General discussion

Locked

Exchange prob - with relay not allowed

By chipw ·
I installed MS Exchange 2000, have DNS working and AD set up, ran netdiag and dcdiag and both passed on everything they check. When I try to send a test email I get the following error -
550 5.7.1 Unable to relay. I read MS article 289553 and don'tquite understand instruction 4 -

"In the SMTP Address Properties dialog box, in the Address field, enter @expecteddomain.com where @expecteddomain.com is the domain that then sender is attempting to send to. Click Apply, and then click OK."

AsI understand this statement, I would have to add every domain that email will ever be sent to, this is not right at all. How many thousands of domains would I have to list here, too many. I obviosly don't understand something here correctly.

Could someone please shed some light on this for me?

This conversation is currently closed to new comments.

34 total posts (Page 3 of 4)   Prev   01 | 02 | 03 | 04   Next
Thread display: Collapse - | Expand +

All Comments

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

Chapter 4 describes how to install E2K in a subdomain, front end and back end servers and on page 148 Windows NT Primary Domain Controllers installation steps. this should help you in understand how to install your W2K server with E2K on it into an NT PDc with a Active Directory Connector with E2K operating in Mixed Mode as well as W2K AD in mixed mode.

Tim Walsh, Joseph Moore, Anna, Lordinfidel[and I've left off some other who deserve credit, sorry ]are all the gurus on NT W2K Nets, and I would love to see them get involved in this discussion. Up the point value to about 5K [they like points].

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

Setting up a W2K AD DC with E2K within an existing net is done when you first install Active Directory. The wizard will ask what role this DC is supposed to have and whether you want it to run in native or mixed [in your case mixed]. Again, Tim Walsh or Joe Moore know the intricies of this much better than I do as I've just gone from NT to W2K and not tried to include into the exising NT net the W2K AD with Exchange.

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

Poster rated this answer

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

I bought the book. Now I'm going through it from the beginning, even reinstalling w2k and exchange. I haven't found the section you mention about the NT/W2K testbed. I only see info on W2K testbed.
This machine may be connected physically to the corporate network but I am giving it a differant domain name. This is the only way I have of giving it internet access.
To make sure I understand this part correctly - E2K has to be on a W2K server (not necessarily a PDC). It has to run AD. Can I make this a member server in my NT network? Seems that would make this all work becuase it would have direct access to the NT DNS server. No trusts, or other fussing around. Or maybe I'm just way off base here.
(So here I have added a comment to my initial question, not to your answer. If I try to comment on your answer I have to give it a unacceptable rating or it will not post)

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

I did a complete reinstall, taking default settings, of w2k and e2k and added lookout, er, outlook.
Telnet will not connect to any port, from the server itself or from a workstation.
nslookup resolves names just fine.
Trust relationships going both ways are working and verified.
I ran vbportscan.exe and it shows that port 25 is open, it's the first on the list.
When I run Outlook on the server I get an error - unable to open your default mail folders - you do not have permission to logon.
When I set up Outlook I used a test account that I set up.
I will try another test account, start a new one and see how that goes.

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

Thanks for the references in the book. They all refer to an existing Exchange installation on NT. We don't have that. We have an NT pdc, for email we have a Notes Domino server administered remotely from Norway (we are in the Seattle area). Upgrading the existing NT server is not an option. The section on p148 talks about upgrading from NT to W2K. I understand mixed mode installs, but it appears that AD has to be the PDC, so E2K can access the AD. Is this correct? I read on p181 "You must deploy AD in your environment if you are planning to install E2K" It goes on to talk about upgrading to W2K. It doesn't actually cover having an NT PDC with an E2K server as a member server or even a BDC.

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

Appears I may be making some progress - I can telnet and connect to port 25 now. Turns out the telnet service was set to start manually by default. I changed that. Connecting to 25 works. NSLookup works for most domains I tried, a few timed out. When I send a message from the telnet window to my company Notes email account it never shows up. I see in the queue in ESM a message that says to enumerate, this book doesn't cover enumerating. Another message I tried to send showed in the queue properly, and shows status queued. How long before it actually gets sent?

Collapse -

Exchange prob - with relay not allowed

by chipw In reply to Exchange prob - with rela ...

I opened the IIS MMC and see a big red X on the smtp properties icon. This is obviously a problem. But, smtp should work, by default, without any fussing around with anything. All I need is for one machine to be able to send out auto-response emails, no users, no incoming messages. A FreeBSD box running a default install does this with no configuration of any kind. Why can't the much more expensive Exchange? I'm frustrated and have had enough of this...

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

if you can telnet to open port 25 and see the exchange message and version # That's good. Next step would be to setup Outlook to use your exchange server to send mail, But to do that! you have to create a AD accout. If you log on to your your servervia the Admin accout, then just install Outlook and set it up to use the exchange server to send email. [Don't try to send Email via telnet]. if you W2K AD server with Exchange has the correct configuration [re a the W2K AD with Exchange is a seperate domain with a two way trust to your NT domain, then via Outlook, you should be able to send email to each other. If you have a hotmail account, you can try to send email from yourself via Outlook to the hotmail account to verify outbound and then reply back to check inbound.[this is a test I do myself. I can send email to my hotmail account and watch on another computer that is signed in to that account for the mail to arrive].

If you have a firewall setup between the internet or external resources and your network, the firewall HAS to allow inbound/outbound port 25 traffic from the W2K AD w/Exchange setup.Since you already have an existing mail server, you might possibly be having a conflict between them. you have to remember thatW2K AD w/Exchange is really setup to be a PDC for the domain as AD creates all the user accounts and intergrates with Exchange to automatically create a email account when the user account is created in AD.

Collapse -

Exchange prob - with relay not allowed

by CG IT In reply to Exchange prob - with rela ...

Since your trying to intergrate exchange into your existing NT network that already HAS a mail server, your going to run into a ton of headaches. If you run a test bed of W2K AD w/Exchange NOT intergrated into an existing NT domain, your'll find that everything setups up very nicely and works without much trouble. Microsoft may say you can use W2K AD w/Exchange in an exisitng NT network BUT it's really meant to replace NT so they can retire and no longer support it and get everyone W2K. Now thebig push will be to W2003 server.

Back to Software Forum
34 total posts (Page 3 of 4)   Prev   01 | 02 | 03 | 04   Next

Related Discussions

Related Forums