Windows 2000 Server Domain giving problem XP OS

[vinayak 0]

We have Windows 2000 Server Domain and all our machines were running Windows 2000 and windows xp professional workstation. I joined them to the domain, no problem.

 

For one, I've found that I sometimes am unable to browse the 2K and xp machines from the XP machines. When I first log in, it's fine. But then after some time when I try to browse to a 2K machine, it hangs for a minute and eventually errors out. I have to reboot the machine before I can get access again or when i removed IP & DNS it's working fine.

 

We also have a VPN to another network that has some XP machines in a workgroup. I can access these machines with no problems from our 2K machines no matter who I log in as. The XP machines won't connect unless I log in with a username/password that also exists on the target machine. Even with the same username/password, I sometimes lose connection and have to reboot before I can access the machine again.

 

I've searched all over the Internet for anything about these issues. but I am not find any solution. I appreciate any help anyone can offer. Thanks!

[Myke 0]

What protocols are you using? We use both Novell and Microsoft authentication, which has left us, at times, unable to browse to other machines unless the IPX/SPX protocols are installed. This is kind of ridiculous, as having additinoal protocols installed can slow down the response times on a network.

 

Also, I'd check the local firewall settings (I assume you have upgraded to XP SP2) to ensure that File and Print Sharing is checked. This has caused some problems if not checked in the past. The XP firewall is the first thing that I look into when dealing with such issues. For instance, when SAV would not function properly, I found that TCP port 2967 had to be opened up on the clients' firewalls to allow proper communication.

 

Hope this is somewhat helpful to you.

[vinayak 0]

We r using only TCP-IP protocol, & All our Machines windows 2000 & Xp are Updated with latest service Pack.

 

I think problem is our DNS setting, Our IP's not resolve domain name sometimes.

[peterh 1]

Does you network have DHCP server? Does DHCP run on the Windows server or from a router?

If running from a router, you may have 2 DHCPs on the same network that may be causing the problem and thus giving the wrong IP/gateway/dns information.