Exchange Name resolution problem

[Bhavin78]

In our network we have AD domain/DNS.

we use third party exchange server for our email. Third party is the company with whom we do business with. We also use many of their AS 400 and intranet system. For all this the have cisco router in our office to make connection.

Issue is with exchange. When I try to configure outlook profile on users PC,name resolution is the problem. Cannot resolve name.
what I need to do to make this work correctly?

 

[ShackDaddy]

You need the right protocols to run over the VPN connection to the other site. If the Cisco router is limiting the types of traffic that traverse the VPN, then it's likely that RPC connections are being blocked. That runs on port 135, but it also uses other ports to make the connection. See the following article:

http://support.microsoft.com/kb/278339/

In particular, pay attention to ports related to the Global Catalog, since the initial connection to the Exchange server to verify the server/username makes a connection to the Global Catalog on the remote server.

ShackDaddy

ShackDaddy

http://www.shackelfordconsulting.com

 

[BenChristian]

I'm assuming that you have a VPN connection or other link to the third-party? If you are using Windows 2003 DNS servers, you can configure conditional forwarding so that you can resolve hostnames of machines that belong to the domain that the Exchange server resides in. For example, if the server resides in a domain called "thirdparty.local" you can configure your DNS server(s) to forward all requests for the thirdparty.local DNS domain to a DNS server at the Thirdparty location.

Ben Christian
MCSE, MCSA:Messaging

http://www.benchristian.com

 

[Bhavin78]

I have done that but it's not able to resolve Name to IP address but it works when I put IP Address.

I think I need to find right DNS Server name from third party.

 

[ShackDaddy]

So you already tried adding the remote internal domain name to the forwarders tab on your DNS server, and then you selected that domain name and added the remote domain's DNS server IP address to the list? That's what would have to be in place to implement Ben Christian's good solution.

ShackDaddy
Shackelford Consulting

 

[Bhavin78]

shackdaddy,
I added remote DNS server name/IP address on the forwaders TAb. This is what I did.
what else I need to do? I was confused with your last post.

 

[ShackDaddy]

To see whether the underlying DNS stuff is working, I would open a commandline and run nslookup.

Your client should be pointed at your local DNS server for name resolution, so when you run nslookup, it will show you the name of your local DNS server.

Then type in the name of the remote exchange server, including the full domain, like 'exchange.domain.local'

Does the name resolve to an IP address? Is it the correct address, ie: the internal IP for the remote mail server?

If it does resolve properly, then it maybe you should use the very same full domain name as the server name when you enter it in the Outlook client. If it still doesn't work, it may be a protocols issue after all, and you should re-read my first post.


ShackDaddy
Shackelford Consulting