vicrod3315
asked on
Second Exchange 2003 Server in different Site
Hi,
I have the following topology
LAN A - Domain Controller1 and Exchange Server 1
LAN B - (Second Site) Domain Controller 2 and Exchange Server 2
Both domain controllers can share ADS fine. Both Exchange Servers can be seen in System Manager.
Here's my problem...
LAN B - Exchange Server can send to external clients (all internet clients). It can send to LAN A Exchange Clients, like exchange server B can delivery to exchange server A.
LAN A- Exchange server CANNOT SEND TO LAN B ECHANGE SERVER.
They are both on the same domain which is our intent. We want to share the same domain name space accross all servers. My only problem is that one exchange server cannot send to another exchange server in the different site. How can I fix this?
I have the following topology
LAN A - Domain Controller1 and Exchange Server 1
LAN B - (Second Site) Domain Controller 2 and Exchange Server 2
Both domain controllers can share ADS fine. Both Exchange Servers can be seen in System Manager.
Here's my problem...
LAN B - Exchange Server can send to external clients (all internet clients). It can send to LAN A Exchange Clients, like exchange server B can delivery to exchange server A.
LAN A- Exchange server CANNOT SEND TO LAN B ECHANGE SERVER.
They are both on the same domain which is our intent. We want to share the same domain name space accross all servers. My only problem is that one exchange server cannot send to another exchange server in the different site. How can I fix this?
ASKER
what i mean by site is they are in different subnets. They are also in the same routing routing group but both servers are in two different networks.
We are trying to simulate two exchange server in the same doman but in different networks.
We are trying to simulate two exchange server in the same doman but in different networks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok to answer your questions about the GAL, I can see all users in GAL on Server B. that's no problem. I can even ping from server A to B and vice versa. At least this eliminates any routing issues pertaining to the network.
When I send a mail from server A to serber B, the mail just stays on the queue. Now If I was to send mail from server B to server A, the mail gets delivered properly. I have even tried putting both servers in the same subnet and still it's the same problem. I tried creating an SMTP connector from server A to server B and this does not work. It seems all mail delivery from server A to server B stay on the queue no matter what. I'm pretty sure i'm doing something wrong here.
I checked the client recipient policy and there's only one there right now. On the email address policy I have @mydomain as authoritive for the organization checked. I read somethere where you need to remove the check mark on that and make it non authoritive. If I do that then I can't receive emails from the Internet. I even tried fooling the policy by creating a bogus email domain like @internal and made that authoritive while the @mydomain was not. Still no luck with that. I got fustrated and created a second recipient policy, this time with @mydomain as authoritive for the second policy, while in the first policy is was unchecked. So hoping that the policy would check the next one in order, this still does not work.
When I check the queue from server A to B and click on the server queue, at the bottom it displays " the server remote server has rejected the connection". So I'm thinking this may be a dns issue I check the DNS server and correct name and IP is correct. The only problem is I don't have an MX record for server B. So to eliminate that possibility I created an MX record for server B and still no luck sending email from server A to server B. I'm telling you i'm going crazy here. I know this is supposed to work when both server are in the same routing group and same administrative group. I finally decided to uninstall server B from the organizationa and reformat the server and install from scratch again with a diferrent host name and new DNS entry. After all that hard work and joining the server back to the same administrative and routing group, it still does not work. I really don't know what to do from this point on. Is this a normal issue? Am I doing something wrong here?
When I send a mail from server A to serber B, the mail just stays on the queue. Now If I was to send mail from server B to server A, the mail gets delivered properly. I have even tried putting both servers in the same subnet and still it's the same problem. I tried creating an SMTP connector from server A to server B and this does not work. It seems all mail delivery from server A to server B stay on the queue no matter what. I'm pretty sure i'm doing something wrong here.
I checked the client recipient policy and there's only one there right now. On the email address policy I have @mydomain as authoritive for the organization checked. I read somethere where you need to remove the check mark on that and make it non authoritive. If I do that then I can't receive emails from the Internet. I even tried fooling the policy by creating a bogus email domain like @internal and made that authoritive while the @mydomain was not. Still no luck with that. I got fustrated and created a second recipient policy, this time with @mydomain as authoritive for the second policy, while in the first policy is was unchecked. So hoping that the policy would check the next one in order, this still does not work.
When I check the queue from server A to B and click on the server queue, at the bottom it displays " the server remote server has rejected the connection". So I'm thinking this may be a dns issue I check the DNS server and correct name and IP is correct. The only problem is I don't have an MX record for server B. So to eliminate that possibility I created an MX record for server B and still no luck sending email from server A to server B. I'm telling you i'm going crazy here. I know this is supposed to work when both server are in the same routing group and same administrative group. I finally decided to uninstall server B from the organizationa and reformat the server and install from scratch again with a diferrent host name and new DNS entry. After all that hard work and joining the server back to the same administrative and routing group, it still does not work. I really don't know what to do from this point on. Is this a normal issue? Am I doing something wrong here?
sorry vicrod this is suppose to be as easy as drinking water and u have
done everything right.Now do one more thing make sure to check both
smtp server for authentication(inbound and out bound)and make sure
annonymous is enabled(only annonymous)
what about firewalls?depending which u have they may be the problem too.
if everything failed u and right before u call MS reinstall smtp on ur server A.(it is on ur exchange CD).
Also enable diagnostics logging to get a more detailed description of ur
problem.
done everything right.Now do one more thing make sure to check both
smtp server for authentication(inbound and out bound)and make sure
annonymous is enabled(only annonymous)
what about firewalls?depending which u have they may be the problem too.
if everything failed u and right before u call MS reinstall smtp on ur server A.(it is on ur exchange CD).
Also enable diagnostics logging to get a more detailed description of ur
problem.
ASKER
Ok I found the problem.
I forgot to mention i have two domain controllers in our LAN. For some wierd reason they're both having replicating issues with each other as this can also affect exchange directory access. When I right clicked on each server under the ESM and looked on the Directory Access tab, I noticed that they were opposite to each server and this was causing the secondary server not to be seen by the primary one. So I set both servers to have the config server settings as the same in order. Then I want back to Directory Site and services and forced replication among the DC's. Then stop and restarted the virtual smtp server and this made it work. Server A was able to send to Server B and vice versa. So anyone else out there reading this, make sure you have both DC's replicating properly with each if you're installing exchange in a Two Domain Controller or more enviroment. I know realize how important DNS and domain controllers have a huge impact on all services.
I forgot to mention i have two domain controllers in our LAN. For some wierd reason they're both having replicating issues with each other as this can also affect exchange directory access. When I right clicked on each server under the ESM and looked on the Directory Access tab, I noticed that they were opposite to each server and this was causing the secondary server not to be seen by the primary one. So I set both servers to have the config server settings as the same in order. Then I want back to Directory Site and services and forced replication among the DC's. Then stop and restarted the virtual smtp server and this made it work. Server A was able to send to Server B and vice versa. So anyone else out there reading this, make sure you have both DC's replicating properly with each if you're installing exchange in a Two Domain Controller or more enviroment. I know realize how important DNS and domain controllers have a huge impact on all services.
two exchange servers are within the same exchange organization?same routing group?
both handle the same email domain?