CaLoFs79
asked on
Multiple Exchange Server 2003 same domain, not working with other server users!
Hi there.
First, I will describe you my enviroment.
Active Directory, 3 offices connected by VPN, one domain and 2 exchange server 2003.
I just installed the third Echange Server 2003 in the third office with the AD and DNS.
Now, I created an account in the first exchange server and then I move it to the third email server in oder to test it.
I can send emails to foreign domains and to the users at the second Exchange Server, I receive emails from any domain and from the others exchange server in our VPN... but I can't email to the users in the first Exchange Server!
I have checked the routing groups, the recipients policys, etc...
Some time later, I got all those email back by mail delivery error :/
And the last step showed in the Message tracking center is:
"SMTP: Message Routed and Queued for Remote Delivery"
I check the AVG antivirus and disabled the email scanning with not results.
Any idea?
Thanks
First, I will describe you my enviroment.
Active Directory, 3 offices connected by VPN, one domain and 2 exchange server 2003.
I just installed the third Echange Server 2003 in the third office with the AD and DNS.
Now, I created an account in the first exchange server and then I move it to the third email server in oder to test it.
I can send emails to foreign domains and to the users at the second Exchange Server, I receive emails from any domain and from the others exchange server in our VPN... but I can't email to the users in the first Exchange Server!
I have checked the routing groups, the recipients policys, etc...
Some time later, I got all those email back by mail delivery error :/
And the last step showed in the Message tracking center is:
"SMTP: Message Routed and Queued for Remote Delivery"
I check the AVG antivirus and disabled the email scanning with not results.
Any idea?
Thanks
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I changed the setting to use the internal IP, recreated the SMTP connectors and abracadabra!!! It's working!
Thank you!
Thank you!
ASKER
Wierd... now it's not working!
I double checked the settings and everything looks normal!
About the "IP" setting told by Sembee, it must be on all the servers on our VPN? or just our local?
I double checked the settings and everything looks normal!
About the "IP" setting told by Sembee, it must be on all the servers on our VPN? or just our local?
The IP address setting should be on the SMTP virtual server and should be set to the machine's own IP address, not any other IP address that the server may have. If the server has more than one IP address it needs to be its primary address.
You then need to recreate the routing group connectors, not the SMTP connectors.
Simon.
You then need to recreate the routing group connectors, not the SMTP connectors.
Simon.
ASKER
Still not working.
I deleted the routing group connectors after update the IP address setting and then I created the routing group connectors.
Any idea what could be? Maybe something else?
I deleted the routing group connectors after update the IP address setting and then I created the routing group connectors.
Any idea what could be? Maybe something else?
Can the servers talk to each other on port 25?
Have you got smart hosts set on the SMTP virtual server?
Check that your AV software doesn't block port 25.
Simon.
Have you got smart hosts set on the SMTP virtual server?
Check that your AV software doesn't block port 25.
Simon.
ASKER
Yes, they can talk to each other on port 25.
I have no smart hosts set on the SMTP VS.
Done, No 25 port blocked.
How could I set that smarthost?
I have no smart hosts set on the SMTP VS.
Done, No 25 port blocked.
How could I set that smarthost?
You don't want to set a smart host on the SMTP virtual server as that will break the message flow. If you need to use a smart host for outbound traffic then it should be set as an SMTP Connector.
You may want to read my blog post from last week, it is a similar issue.
http://www.sembee.co.uk/archive/2007/02/19/55.aspx
Simon.
You may want to read my blog post from last week, it is a similar issue.
http://www.sembee.co.uk/archive/2007/02/19/55.aspx
Simon.
ASKER
Hey Sembee, thanks a lot.
It's working now, I just update the IP address settings in the Virtual SMTP server in all the others exchange server on the network.
Thank you very much!
It's working now, I just update the IP address settings in the Virtual SMTP server in all the others exchange server on the network.
Thank you very much!
ASKER
Well, I had some administrative stupid issues and then I had to remove that settings, but I found a new solution.
I edit the "host" file in /winnt/system32/drivers/et
Thanks a lot for the idea.
I edit the "host" file in /winnt/system32/drivers/et
Thanks a lot for the idea.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
We had a quite a few issues with that when migrating to Exch2003.
I do recall an issue simliar to that dealing with recipient policies. Something to do with the external domain and the priority?