T
Thany
I'm sorry to post this here, but I couldn't find a win2003 newsgroup.
Besides, this problem occured with my previous server (win2000) as well.
I have got the simplest setup with a Windows 2003 server and Active
Directory. One forest, one domain, one server. All other services on the
same machine. A small business setup if you will.
There are about 5 clients (once again proving my network is quite small) and
at least one of them keeps disconnecting network drives. Not only does it
disconnect mapped drives, also when its working on a UNC path, suddenly the
connection to it is severed. Not only is the connection lost, also no
connection (with *any* of the shares on the server) can be made for approx
20 seconds. Other network traffic to the server, such as FTP, flows normally.
On both the server and the client, I've executed "net config server
/autodisconnect:-1", verified that the setting came through, rebooted and
verified again. But no juice.
In a probably highly related problem, the client has a very hard time
logging onto the domain when it's given a cold boot. It's as if the same
problem occurs: the OK button is pressed, the login screen get grayed out
and then waits for like 20 seconds. After that, it seems to have succeeded
in checking the password and continues. But even then it's slower than it
can, and it still seems to wait for the network for a while during "applying
computer settings".
Besides, this problem occured with my previous server (win2000) as well.
I have got the simplest setup with a Windows 2003 server and Active
Directory. One forest, one domain, one server. All other services on the
same machine. A small business setup if you will.
There are about 5 clients (once again proving my network is quite small) and
at least one of them keeps disconnecting network drives. Not only does it
disconnect mapped drives, also when its working on a UNC path, suddenly the
connection to it is severed. Not only is the connection lost, also no
connection (with *any* of the shares on the server) can be made for approx
20 seconds. Other network traffic to the server, such as FTP, flows normally.
On both the server and the client, I've executed "net config server
/autodisconnect:-1", verified that the setting came through, rebooted and
verified again. But no juice.
In a probably highly related problem, the client has a very hard time
logging onto the domain when it's given a cold boot. It's as if the same
problem occurs: the OK button is pressed, the login screen get grayed out
and then waits for like 20 seconds. After that, it seems to have succeeded
in checking the password and continues. But even then it's slower than it
can, and it still seems to wait for the network for a while during "applying
computer settings".