Network user loses permissions to mapped folder

[Schoolies]

I have a windows 2000 domain setup. I moved my server and 2 XP Pro computers to my new house. One computer works fine. The other one does not. I can log into the domain fine and browse the network shares for a couple of hours but then all of a sudden when I leave for an hour or so and come back, I can't connect to my network shares. (the network shares are located on the server)

When I try to get to any network resource it takes forever and spits out an error (i forgot what it was) but now when I try to go to My Computer to double click the networked drives, My Computer just freezes and sits there.

On my workstation, my DNS is pointed to the server. I'm not sure what is wrong here.

Thanks

 

[scauffiel]

Can you ping anything once you've come back after an hour and nothing works? You may want to check the power settings for your NIC and turn off the setting that allows windows to shut the NIC down to save power. Sometimes this setting works, and sometimes it doesn't.

Steve

 

[Schoolies]

Looks like that might have done the trick... thanks!

 

[scauffiel]

Glad I could help,

S.

 

[Schoolies]

I think I spoke too soon. I just got back home and it did it again... My Computer just sits frozen when I double click the icon.

If I stop the NETLOGON service when it is frozen, it will unfreeze.

When it is frozen, I can't ping the other, working, client computer but I can ping the server. I try to view my server by typeing \\server and it asks me for a username and password. If I enter my domain username and password, its says:

"The username you typed is the same as the username you logged in with. That username has already been tried. A domain controller can not be found to verify that username."

but when I specify the server in the username "server\username" it will log in.


STRANGE

 

[LuckyTaxi]

I ran into this issue once and I think I solved it by rejoining the computer to the domain.

 

[casper114]

Originally posted by: lilcam
I ran into this issue once and I think I solved it by rejoining the computer to the domain.

I fixed a problem very similar by doing the same thing. Hopfully you doin't have to delete the user and create a new one.