Exchange Server name resolution associated with DHCP lease renewal
Posted on 2004-09-16
Running Win2k Server (Basic) and active directory in native mode. I have a problem with approximately 4 client computers during IP lease renewal. When a user starts the client and logs onto the network, all shared resources/printers are just fine. What isn't fine is when the user tries to start Outlook 2000. Outlook 2000 cannot seem to locate the exchange server. When I run a tracert to the exchange server, the route comes back to our gateway's external IP address - not the internal IP address. Same with ping, it will ping the external IP of the gateway, but not the internal IP of the exchange server.
What happens is the user is presented with a logon pop-up box that asks for username, password, and domain. Nothing works no matter what is input.
This is only happening with approximately 4 clients (the same 4) out of a network containing 100 computers in the domain. What's frustrating is that the problem seems to self-correct in 5 to 10 minutes. After about 5 to 10 minutes the client will be able to properly tracert the exchange server to the internal IP and pinging the exchange server will ping the proper internal IP.
The problem appears randomly, but seems most prevalent at lease renewal from the DHCP. I've created a batch file to capture the ipconfig information and dns cached information for the client the next time this happens to hopefully further track down the cause.
All other clients on the network do not experience this issue and I can't figure out what is different or needs fixed.