• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2000 Server Help Needed.

J

Jay

Golden Member
I have recently upgraded my Server at home from NT to 2K. Everything seemed to be running fine, I setup accounts on the Win2K machines and I could logon to the domain via WinME boxes. Howerver, I have upgraded to WinXP Pro on those machines and cannot get access to the domain.

My understanding is that Win2K was mimicking WINS for the Win9X machines, but for the WinXP Pro machines, they actually have to use DNS to get to the domain controller. Does this mean I have to enable my own DNS server on the box? The warning I get right now is that the domain I use is unavailable, but I can still get to the hidden shares on the box, it just takes forever to get the window to pop up and occasionally my comp will freeze trying to browse the server's hidden shares.

Thanks for any help you guys can provide.

Jay
 
I am not sure how to connect an XP machine to a 2K machine. But do know for a fact is that w2k's Active Directory REQUIRES DNS to function and WINS is optional for downlevel clients like your 9x machines. So DNS is definately installed if you are running a w2k domain because it will install a DNS server along with your DC if you haevn't already got a DNS server.
 
It might be that you have DNS running on your server but the client machines don't know it. Try adding them to your hosts file and see if that helps.

 
tried that, no luck. The actual message I get from the clients is that the domain controller is not found. 🙁
 
Check in the advanced TCP/IP settings under the WINS tab and make sure that you have NetBIOS over TCP/IP enabled unless you are using Win2K DNS/AD and all the clients are pointing to your internal DNS.
 


<< tried that, no luck. The actual message I get from the clients is that the domain controller is not found. 🙁 >>



Double check the DNS services... make sure the service is running. Right click on your dns and run the simple and recursive dns tests. If those pass, make sure your clients &quot;Preferred DNS&quot; entry (in network properties of your LAN connection) is set to the ip of your Win2k DNS Server. On your Win2k DNS machine, do an NSLOOKUP and see what results are you getting.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top