Exchange 2010 DNS problems
Hello guys,
Im having the following problem with the exchange server on my company:
On some of the users pc's randomly through the day their outlook client won't connect to exchange and the only way to fix it is to reset the DNS Client windows service.
After that it inmediately connects without a problem.
I have zero experience dealing with DNS servers and Im wondering Why does this not happen in every pc and, what could be causing this?
Thanks in advance for your time!
Im having the following problem with the exchange server on my company:
On some of the users pc's randomly through the day their outlook client won't connect to exchange and the only way to fix it is to reset the DNS Client windows service.
After that it inmediately connects without a problem.
I have zero experience dealing with DNS servers and Im wondering Why does this not happen in every pc and, what could be causing this?
Thanks in advance for your time!
I recommend you to check DNS configured in DHCP server. And DNS forward and reverse Zones..
ASKER
Yes all pc's have static address but I checked and they're all different.
I checked one of the problematic pc ipconfig /all and compared to a non-problematic one and the only differences i found where the Ip addresses
I checked one of the problematic pc ipconfig /all and compared to a non-problematic one and the only differences i found where the Ip addresses
If only Outlook is having an issue that is resolved simply by restarting the DNS Client service, an IP conflict is not likely the issue.
Side note: It is unusual to use static IP addressing for all workstations. After you fix this issue, I would setup DHCP and convert the workstations to DHCP clients.
Questions for the current issue:
- Do you have more than one DNS server?
- What balloon and pop-up errors do you get when Outlook is not connecting?
- What errors are otherwise available from Outlook?
- What Event Log errors can you find on the affected client operating systems?
- Have you tried pinging the Exchange server during an event BOTH before and after an event and what are the results?
- Tom
Side note: It is unusual to use static IP addressing for all workstations. After you fix this issue, I would setup DHCP and convert the workstations to DHCP clients.
Questions for the current issue:
- Do you have more than one DNS server?
- What balloon and pop-up errors do you get when Outlook is not connecting?
- What errors are otherwise available from Outlook?
- What Event Log errors can you find on the affected client operating systems?
- Have you tried pinging the Exchange server during an event BOTH before and after an event and what are the results?
ASKER
There is only one DNS server on the domain.
It get stuck on contacting server and then the pop up says "Server not avaible" with retry and work offline buttons.
I didn't find errors or warnings on the windows event logs while this event arises.
I tried and both times the exchange server responds witouth an issue.
It get stuck on contacting server and then the pop up says "Server not avaible" with retry and work offline buttons.
I didn't find errors or warnings on the windows event logs while this event arises.
I tried and both times the exchange server responds witouth an issue.
"I tried and both times the exchange server responds witouth an issue."
To recap:
Also during the event, it would be good to see if you can ping a couple other local servers:
- Tom
Are you referring to pinging the Exchange server during an event?
Also, I should have been clear, I meant to ping the Exchange server by name during the event. If pinging by name does not work, then try by IP address.To recap:
During the event (while the Outlook client is unable to contact the Exchange server), try to ping the server by name. If that works, stop. If ping-by-name fails, try to ping by IP address.
The point is to validate if the client OS is having the same DNS issue with respect to the Exchange server as indicated by the DNS Client service restart fixing the problem.Also during the event, it would be good to see if you can ping a couple other local servers:
- Any member server or a DC by name.
- The DNS server by address.
However, it would be good to clarify if the Outlook clients are configured to access the Exchange server by name (the most common and recommended method) or by IP address.- The DNS server by address.
- Tom
ASKER
Yeah sorry, I meant pinging the servers.
I pinged the exchange server by name and it worked, also I tried pinging other servers and the DC and it worked too.
And the outlook clients are configured to connect by server name.
I pinged the exchange server by name and it worked, also I tried pinging other servers and the DC and it worked too.
And the outlook clients are configured to connect by server name.
Hmm, curious. On one hand restarting the DNS Client service on the workstation indicates a probable issue at the OS level. However, the ping by name during an incident indicates otherwise.
Just to be absolutely sure, during an incident...:
If it does, then another look at Outlook is in order...
- Tom
Just to be absolutely sure, during an incident...:
1 - Without exiting Outlook, ping the Exchange server by name.
2 - Given a successful ping, confirm that Outlook STILL cannot access the Exchange server.
3 - Restart Outlook (just Outlook) and confirm that it STILL cannot access the Exchange server.
4 - Restart the DNS Client service and confirm Outlook CAN access the Exchange server.
I know you more or less, performed all these tests, but want to see/confirm if the exact sequence produces the same results.2 - Given a successful ping, confirm that Outlook STILL cannot access the Exchange server.
3 - Restart Outlook (just Outlook) and confirm that it STILL cannot access the Exchange server.
4 - Restart the DNS Client service and confirm Outlook CAN access the Exchange server.
If it does, then another look at Outlook is in order...
- Tom
Are these Computers New with Win7?
If they are, try to set/change the Power Saving Profile to high performance.
Also, check/verify that your NICs are not powered down to save electricity.
One last thing, run ipconfig /flushdns and then ipconfig /registerdns.
Note: if your other PCs on the LAN are not loosing communication with the servers you don't have a DNS problem. It could be just these computers and one last thing your networking device port not working properly.
Good Luck!
If they are, try to set/change the Power Saving Profile to high performance.
Also, check/verify that your NICs are not powered down to save electricity.
One last thing, run ipconfig /flushdns and then ipconfig /registerdns.
Note: if your other PCs on the LAN are not loosing communication with the servers you don't have a DNS problem. It could be just these computers and one last thing your networking device port not working properly.
Good Luck!
ASKER
Sorry for not answering.
I did it in that sequence and I got the same results, although most of time I can't even get Outlook to open, it gets stuck on Connecting to server on the splash screen.
I did this on one of the pc's with this problem, I deactivated the sleep function and made sure the NIC does not get powered down and the problem seems to be fixed on that pc. Is it normal that after waking from sleep flushing the DNS made it work?
But in another one (that always has had the sleep timer deactivated and the NIC always on) it still sometimes loses connection to the server until I reset the DNS client service (or flushdns)
Hmm, curious. On one hand restarting the DNS Client service on the workstation indicates a probable issue at the OS level. However, the ping by name during an incident indicates otherwise.
Just to be absolutely sure, during an incident...:
1 - Without exiting Outlook, ping the Exchange server by name.
2 - Given a successful ping, confirm that Outlook STILL cannot access the Exchange server.
3 - Restart Outlook (just Outlook) and confirm that it STILL cannot access the Exchange server.
4 - Restart the DNS Client service and confirm Outlook CAN access the Exchange server.
I know you more or less, performed all these tests, but want to see/confirm if the exact sequence produces the same results.
If it does, then another look at Outlook is in order...
- Tom
I did it in that sequence and I got the same results, although most of time I can't even get Outlook to open, it gets stuck on Connecting to server on the splash screen.
Are these Computers New with Win7?
If they are, try to set/change the Power Saving Profile to high performance.
Also, check/verify that your NICs are not powered down to save electricity.
One last thing, run ipconfig /flushdns and then ipconfig /registerdns.
Note: if your other PCs on the LAN are not losing communication with the servers you don't have a DNS problem. It could be just these computers and one last thing your networking device port not working properly.
Good Luck!
I did this on one of the pc's with this problem, I deactivated the sleep function and made sure the NIC does not get powered down and the problem seems to be fixed on that pc. Is it normal that after waking from sleep flushing the DNS made it work?
But in another one (that always has had the sleep timer deactivated and the NIC always on) it still sometimes loses connection to the server until I reset the DNS client service (or flushdns)
If you are 100% sure this PC and NIC doesn't have any power saving mode turned on try moving the network connection to another port of your switch, reset the switch or both.
If this fails, replace your NIC.
If this fails, replace your NIC.
ASKER
New developtment: it seems the problem is not only on Exchange, some users also reported sudden lost of connection to network drives.
Restarting the dns client service fixed the issue.
Restarting the dns client service fixed the issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If static chances are someone else gets the same IP, i am sure i dont need to explain what happens.
Second i would like you to check with other 'non-complaining' machines if and how the output for ipconfig /all differ.