WinXP Pro --> Win2000

  • Thread starter Thread starter William Anderson, Jr.
  • Start date Start date
W

William Anderson, Jr.

I'm having problems connecting our one and only XP Pro client to our Windows
2000 server. The user is able to login, is authenticated, is able to login
to the Exchange server, browse the Internet, and print over the network, but
when it comes to browsing our network files, there is a long pause, then a
dialog box asking him to login with the proper rights.

I've checked the user's account, as well as the computer's rights, and
they're the same as others who are able to browse without a problem. Any
thoughts are helpful. Thanks!


Wil
 
This has to do with you hosts file. I'm not at work but
you need to set the ip address of your server in there.
Man I sound stupid but if I was at work I could find it.
Hope this helps.
-----Original Message-----
I'm having problems connecting our one and only XP Pro client to our Windows
2000 server. The user is able to login, is
Click to expand...
authenticated, is able to login
 
-----Original Message-----
I'm having problems connecting our one and only XP Pro client to our Windows
2000 server. The user is able to login, is authenticated, is able to login
to the Exchange server, browse the Internet, and print over the network, but
when it comes to browsing our network files, there is a long pause, then a
dialog box asking him to login with the proper rights.

I've checked the user's account, as well as the computer's rights, and
they're the same as others who are able to browse without a problem. Any
thoughts are helpful. Thanks!


Wil

I am having the same problem so will watch this and hope you (we) get an answer.
.
Click to expand...
 
I tried modifying the hosts file as noted by one helpful post, but it didn't
seem to do the trick. I took a look at another board, and a suggestion was
posted to point the DNS of the problematic computer directly to the DC.
Apparently, this has solved many XP-related networking issues.

I gave that a try this morning and it seemed to take hold. I'll give it a
day and a reboot, then report back.


Wil
 
Well in a round about way you got to the change I was
trying to remember to tell you.

That fix will fix it.
 
Back
Top