Exchange 2003 SBS not receiving Mail!

[Hotchkin]

Hi this is my first post to the forum.

I have 2 old W2K servers in a domain - DC1 is the current Exchange 2000 server and SQL Server and works fine, DC2 just serves files.

Bought a new W2K3 SBS server with loads of capacity with a view to replacing both W2K Servers. Connected new server up to the domain, replicates Active Directory fine. Installed SQL server which works fine. Installed Exchange 2003 and can move mailboxes from Exchange 2000 to Exchange 2003 no problem. Users connected to mailboxes on Exchange 2003 can send e-mails to users either on new server, old server or externally, but can only receive e-mails from users on the new server. Any e-mails sent to users on the new server originating from outside the new server sit in the message queue on the old Exchange server (the queue name that they sit in is the FQDN of the new server).

Why aren't the messages going from the queue on the old server to the new server? Furthermore, why do they go to the old server at all?

Thanks in advance,
Richard.

 

[58sniper]

How did you connect the server to your domain? SBS must be the forest root, and hold all FSMO roles. Additionally, having multiple Exchange servers isn't part of the design. You're certainly not giving us enough info to determine the problem.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[Hotchkin]

Thanks for getting back to me Pat. Sorry if I'm not giving you all the info you need. Trouble is I don't really know what info you might need.

We only have a single domain...so I guess that means that it's the Forest Root(?)

You were right, my new server hadn't been assigned "Master" roles. I've rectified this and it is now the Schema Master, Domain Naming Master, RID Master, PDC Emulator Master and Infrastructure Master. Unfortunately, having done this, it's still not working and inbound messages to users on the new server are still being added to the queue on the old server.

It is not my intention to run multiple Exchange Servers, but at the moment, I don't really have any option. The users have got to keep their mail running via the old server until the new one's working properly. As soon as it is, I can shut down the old server.

Thanks again...I really appreciate your help.
Richard.

 

[58sniper]

You were right, my new server hadn't been assigned "Master" roles. I've rectified this and it is now the Schema Master, Domain Naming Master, RID Master, PDC Emulator Master and Infrastructure Master. Unfortunately, having done this, it's still not working...

Well, I didn't mean to mislead you into thinking that would fix the problem you're having. Just trying to head off any other potential problems.

Can you telnet into the new box over port 25 and manually send test messages to mailboxes on that server? Do both servers show up in ESM? Are they in the same routing and administrative groups?

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[Hotchkin]

Hi Pat,

I think we might be getting somewhere. For some reason I can't telnet on to the new server on Port 25 it keeps coming up "press any key to continue..." then, when I press any key, "connection to host lost". I've successfully telnetted on to the old server and sent myself an e-mail.

To answer your other questioins, yes, both servers are in Exchange System Manager. Under "Administrative Groups" the tree goes down to "first administrative group" beneath which there's "Servers" and "Routing Groups". In servers I've got both my new Exchange server and the old one. Beneath "Routing Groups" I have "first routing group" and beneath that I have "Connectors" an "Members" in which both my Exchange Servers are listed. As shown below...


Administrative Groups
|_
first administrative group
|_
| Servers
| |_
| Server1
| Server2
|_
Routing Groups
|_
first routing group
|_Connectors
|_Members (Containing Server1 and Server 2)

Thank you once again for your continued support.
Richard.

 

[58sniper]

I'll bet you've got anonymous not enabled on the SMTP virtual server. Check and make sure that box is checked.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[Hotchkin]

In the "Server" section under my new Exchange Server, there's a "Protocols" tree. in the "SMTP" section there's "Default SMTP Virtual Server" in the properties for this, on the "Access" tab I clicked the "Authentification..." button. "Anonymous access" is already checked.

Is this what you meant?

Thanks again,
Richard.

 

[Hotchkin]

Aha! Not quite there yet Pat, but I've found that I can telnet onto the new server if I open a connection on the IP address rather than the server name on port 25. Does this shed any more light on the situation?

Thanks,
Richard.

 

[paulha]

Is your firewall natting the external IP to the old server still ?

 

[Hotchkin]

Hi Paul,

Good question. ISA is set up on the W2K server. Can't see anything in ISA Manager thats directing incoming mail from our outside IP address to an inside IP address (although I guess there must be something somewhere - any thoughts on that one?) In any case, would that prevent mail sent from a client connected to our old server (on the inside network) from reaching a client mailbox on the new server(also on the inside network)? Surely that would be handled internally without any NAT translation wouldn't it?

Thanks again,
Richard.