Can't connect to network resources without reboot

[adamlee]

It's not only my daughter giving me gray hair.

We recently migrated from Novell to 2k3. I'm running a dual Xeon 3.something 100 m network, mixed win XP and 98 clients.

I am having connectivity issues. if a machine is idle for an extended period of time, several hours, I lose connectivity with the network. Terminal services still works normal. But when I access network drives, it sometimes takes minutes to connect or it can't connect at all giving me an error "can't connect to //server/shared/...
I have looked through this forum and tried a couple of things, one was in the hardware profile of the nic card, allowing 2k3 to shut off device to save power. Didn't work.

Thanks
Mark

 

[adamlee]

More Info

I search for the server, and try to login. I get the message that my username has already been tried. I can't login as administrator because I can't have two users logged in from one machine.

Thanks
Mark

 

[pborkstrom]

adamlee,

Have you found a resolution for this? I am having a similar problem, but it only seems to affect 95/98 clients. I tied to reinstall the NIC drivers, Client for Microsoft Networks, the AD Client, and no dice. Any luck so far in finding a solution?

Regards,

pborkstrom

http://www.theverseband.com/

 

[adamlee]

Maybe,
I found this last afternoon applied the command and this morning everyone (4 clients) could reconnect normally.

http://support.microsoft.com/default.aspx?scid=kb;en-us;297684&Product=winsvr2003

The actual "DOS" command was
net config server /autodisconnect:-1

I didn't mess with the registry yet. So far today it is working.

Good Luck

 

[pborkstrom]

adamlee,

According to that article, was that command (net config server /autodisconnect:-1) ran on the server (as opposed to the 9x clients)?

-phil

 

[adamlee]

All of my clients were disconnecting overnite. I made this change on my server, and all 3 of my 98 machines and 1 of my 2 XP machines no longer disconnect.

Mark