Link to home
Start Free TrialLog in
Avatar of NetToken
NetToken

asked on

Does WINS be used to help domain workstations maintain connection with Windows Active Directory ?

I have a problem with keeping Windows XP workstations attached to our Windows Server 2003 R2 domain controller ever since our ISP changed along with the main office router.  All our WinXP client workstations cannot see the domain even though the computer names appear in the Domain Controllers computers list.   The problem is temporarily resolved by rebooting both the PDC and workstations, but after an hour or so the workstations can't see the domain.   No problem pinging anything, just can't find the domain when looking for locations to add users to groups in WinXP system management.   Also shared resources between the domain workstations start to require user authentication to access.

I read that enabling WINS was a recommended best practice in a mixed mode environment.  I was just wondering if - in cases like mine - enabling WINS protocol would be helpful.
Avatar of Qlemo
Qlemo
Flag of Germany image

No. AD needs DNS, and does not utilize WINS.
Avatar of Member_2_957366
Member_2_957366

Check your DNS Reverse and Forward Lookup settings.  They might be pointing to the wrong DNS names or the DNS from the previous ISP.
ASKER CERTIFIED SOLUTION
Avatar of Qlemo
Qlemo
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of NetToken

ASKER

Thanks hunart: for the info about AD & DNS.   Qlemo:, I'll make sure the domain controller is setup as the DNS server for the XP clients.  We do use an external DNS from our ISP and that address is also what the clients are setup for their DNS.  I'll correct this tomorrow morning (EST) and get back with the results and to assign points for the solution.

Thanks again to you both for getting back to me on this.
Thank you for providing me with the solution Qlemo:.  

I setup the domain controller to also function as a DNS server and then put the server's IP address as the primary DNS on the client workstations and Active Directory was up on them all day!  

The only problem encountered was Internet browsing was very slow until I added the ISP DNS address as the secondary on the network adapter.

I'm assigning to you all the points on this question for your complete and accurate solution.