When the problem happens, do "ipconfig /displaydns > d:\foo\dns.txt" on the affected workstations. Compare to a workstation that isn't broken.
When the problem happens, use nslookup to query all configured nameservers for all the names in question. This checks to see if all nameservers are giving consistent answers. When the problem happens, do "nbtstat -c" to check the cache of NetBIOS names. Make sure your clients have a consistent DNS configuration. For most people, this means the clients are configured to use your Active Directory Domain Controllers, and *only* your AD DCs, as nameservers. In particular, do *NOT* put your ISP nameservers in. You say you're not using WINS, but you also say you're using NetBIOS names. NetBIOS without WINS uses broadcasts to resolve names. This generally sucks rocks. My preference is to either disable NetBIOS entirely, or deploy WINS. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
