Problems accessing shares with XP Pro! ! ! HELP!

[JackBurton]

OK, here is the set up...This is a network of four PCs, Windows 2000 AS (acting as the domain controller), Windows 2000
Pro, Windows 98SE and WIndows XP Pro. All PCs are set up to run at 100Mbps and are connected to the server by a hub. Now here is the problem, XP Pro is running on the machie listed in my signature and everything works great except accessing shares on the server (the server is the only place that has shared folders). I can access the internet and even browse my internal network, but when I try and browse a shared folder in can take up to 5-10mins to view the content! :| All the other machines have no problem accessing the shares and when I had WIndows 2000 Pro on this particular machine, browsing the network functioned normally. All the machines are set up using TCP/IP with IPs ranging from 192.168.0.1 (server) - 192.168.0.4 with a subnet mask of 255.255.255.0. The server ONLY uses TCP/IP and so does the machine running XP Pro. I'm going to swap out NICs to see if that takes care of it. It might be just a driver issue with the NIC. Has anyone else run into this problem?

 

[AKA]

Had this same problem and it was because of the DNS entries.. whenever I disabled that.. it fixed it.

 

[MaximusH825]

I think I have a similar problem. I have Win XP Pro on my machine and when I try to access any other computer or even workgroup I get an error says that the Netbios name is no longer available. So I tried enabling netbios over TCP/IP and I get the same error. Any thoughts or ideas?

 

[JackBurton]

<< Had this same problem and it was because of the DNS entries.. whenever I disabled that.. it fixed it. >>


What do you mean you disabled DNS? Are you talking about taking the entries out of your TCP/IP settings? If so, I don't have any DNS entries entered. I tried it with a DNS IP and without and still get the same results. :| I'm about to kick the crap out of this machine if I don't get this resolved soon. It just doesn't make any sense! If it was a DNS issue I would think I couldn't even ping my server by using its computer name.