Can not contact DC

Discussion in 'Hardware' started by TroyK, Jan 29, 2006.

  1. TroyK

    TroyK Private E-2

    Hello. I am having a new problem where I can not contact my domain controller, but only with one system. I am running an NT 4.0 server for authentication purposes only. I have 4 client system running Win2K and one running XP Pro. All Win2K systems log on / ping / etc. just fine. The XP system, however, will only log in using a cached account and I can not reach network resources. I can ping using IP's but not names and I can get out to the internet. I have been running this environment for about 2 years and this just started today. I am stumped. Does anybody have any ideas of what I can try to resolve this issue?

    Many thanks for your time.

    Troy
     
  2. TroyK

    TroyK Private E-2

    Never mind. Problem solved. I noticed after hours of troubleshooting that ipconfig was displaying the node type as peer-peer. As this should be broadcast (normally), I looked into this as the potential problem. I found the solution via a Microsoft support doc that listed the registry path of the NBT Node values. For some reason, the default value of 1 (broadcast) had been changed to 2 (peer-peer). Changing it back and rebooting solved the problem.

    Thanks again for the forum. It's great to have this to turn to.

    Troy
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds