On Tue, Apr 28, 2009 at 2:05 PM, Joe Heaton <[email protected]> wrote:
> I opened a DOS prompt, tried pinging the server, and get a Host cannot be
> found error.
Things to try:
* Try PING by all of {short DNS name, FQDN, NetBIOS name, IP address}
and compare results
* Use NSLOOKUP to see what DNS thinks is going on
* Use NBTSTAT to see what NetBIOS thinks is going on
* Look at "IPCONFIG /ALL"; compare to the working computer
If none of those help you, describe how you've got name resolution
configured. That would include:
* What is your AD domain name?
* What DNS nameserver(s) do you have the clients configured to use?
** What are those DNS servers (e.g., your DCs, ISP nameservers, etc.)?
* Is NetBIOS-over-TCP/IP enabled?
** If so, are you using WINS?
*** If so, are the WINS servers all replicating to each other?
*** If not, are all computers on the same IP subnet (broadcast domain)?
In particular: Don't ever (*EVER!*) configure clients to use
nameservers at Internet providers if you're using a private
(undelegated) DNS zone for your AD domain name. Not even as
"Secondary DNS". That can cause the
works-mostly-but-occasionally-stops-working-for-a-little-while problem
you describe.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
