Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS resolution..

Status
Not open for further replies.

redman71

IS-IT--Management
Mar 15, 2002
329
US
I'm having some issues with Windows XP machines resolving the hostname of the Exchange server. I cannot ping by hostname, but can by IP. Running Active Directory.
If i connect to the Exchange Server's web access first, then go back in through outlook, it works. Does anyone know what could cause this?
 
are those XP pointing to AD DNS? what about Exchange server?

when they all pointing to AD DNS, you will have everything resolved.

---------------------------------------
Sr. Directory Services/Exchange Consultant
 
Assuming you are talking about a local connection? What benlu is referring to is that XP relies heavily on DNS, and in order for this to work correctly, the Exchange server and the XP clients all need to register with a DNS server, and use a DNS server to service the requests. If you do not have a DNS server, you can create a file called HOSTS (with no extension) in the %windir%\system32\drivers\etc folder and add your machine names and ip addresses to it in the format:

192.168.1.1 Mailserver.domainname.com
192.168.1.2 Client1.domainname.com
192.168.1.3 Client2.domainname.com

and the machines will be able to find each other.
 
If you are running AD, then you have DNS running. AD requires it, or it won't install. Are you getting any kind of error messages on the clients? On the clients, they should be pointing to local dns only, so if they are pointing to an outside dns server, you will find the problem. All clients point to local servers, and local servers point to themselves first, then to forwarders.
If i connect to the Exchange Server's web access first, then go back in through outlook, it works. Does anyone know what could cause this?
Sounds like it's going into cache, so thats why it works then. If you turn off a client that is working because of this, does it work when you turn it back on? My guess is no. Just need a little more info. Good luck.b

Glen A. Johnson
If you're from the Illinois, Wisconsin or Florida area, check out Tek-Tips in Chicago IL
To get the best answers to your questions, check out faq950-5848
 
I've got DNS properly configured. It only happens on XP machines running Outlook 03. I've found that if I enable a LMHOST file with the IP - Hostname listed. Works fine then. What could cause this?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top