A weird occurrence of an SBS-2008 environment where locally connected users are unable to resolve DNS even though network services are working well on the server.
This user encountered a similar issue as mine:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26804178.html#a39516961
To those of you who has no Expert Exchange account, I have printed and saved this article here:
http://www.scribd.com/doc/170510614/DNS-issue-faced-with-Windows-SBS-2008-in-the-Local-Area-Network
I am using SBS-2008, updated with the latest patches.
One fine day my clients in their office are unable to resolve DNS addresses. However, all incoming connections including VPN-PPTP were working well.
My usual solution was to restart the server, and that should fix it. Initially we thought it was due to the Antivirus software installed on the server.
We manage to figure another way out, disable network adapter, and re-enabling it will resolve the issue.However, we couldn't do that all the time, as it will disconnect our remote support session. Restarting the server was a better choice for us.
Observations:
We ran nslookup on the server, it showed an ip v6 NS. It can resolve names properly.
We ran nslookup on the workstations, it showed ip v4 NS, which is the correct and default NS, and we couldn't resolve the DNS. We could still maintain a connection via teamviewer, but simply not resolve any DNS when browsing sites.
Work-around solution:
After disabling IPv6 on the network adapter on the server, we were able to resolve DNS entries fine on the server and the clients.
In addition, we were also able to connect to the internet on both server and clients. I do realize that Exchange might encounter problems, so I turned IPv6 back on again in the server network adapter and problem was resolved.
I believe this will come back again.. and I don't think the above is a real-solution yet, but it's a good enough solution for now to resolve this issue quickly.
No comments:
Post a Comment