I've seen this error 99% of the time due to using the wrong DNS server
addresses in IP properties. This is also true with DCs and clients, not just
clients. They're probably trying to query DNS for the domain and they are
asking your ISP's if the ISP's DNS is in IP properties.
So...
Generally for any AD environment:
1. Point all your machines only to your internal DNS server ONLY. THis means
all your clients and DCs.
2. Do not use your ISP's addresses or your router as a DNS or I guarantee
you WILL have problems.
3. Configure a forwarder on your DNS server for efficient Inernet
resolution. If the option is grayed out, delete your root zone. This article
shows how to do both:
http://support.microsoft.com/?id=300202
More info on AD and it's absolute DNS requirements:
http://support.microsoft.com/?id=291382
Hope that helps
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory