G
Guest
Hi,
We are using DFS on a Windows 2000 Server for homedirs.
The server is a memberserver in a Windows NT4 resource domain.
CLients are Windows 2000 machines.
The first time a client tries to browse the DFS share it is very slow, about 10-30 seconds just to open a share with 3 subfolders.
Seems even slower when saving a document and trying to browse to the right location in the save dialog.
If the client close the explorer window and try the same thing immeidately, it works as expeted, e.g. immidiate response!
Seems like it is ok for a while after this and then the slow response time reappears.
Tried to put the dfs server in lmhosts #pre to see if WINS was causing this, but it didn´t make any difference.
Removed all other server mappings, no difference.
Installed SP4 to a client and added the key HKLM\System\CurrentControlset\Services\Dfs\Parameters:
DfsDisableSiteAwareness =1 as described in KB:810418, no difference.
Does anyone know why the clients are behaving like this with the DFS share?
/Anders
We are using DFS on a Windows 2000 Server for homedirs.
The server is a memberserver in a Windows NT4 resource domain.
CLients are Windows 2000 machines.
The first time a client tries to browse the DFS share it is very slow, about 10-30 seconds just to open a share with 3 subfolders.
Seems even slower when saving a document and trying to browse to the right location in the save dialog.
If the client close the explorer window and try the same thing immeidately, it works as expeted, e.g. immidiate response!
Seems like it is ok for a while after this and then the slow response time reappears.
Tried to put the dfs server in lmhosts #pre to see if WINS was causing this, but it didn´t make any difference.
Removed all other server mappings, no difference.
Installed SP4 to a client and added the key HKLM\System\CurrentControlset\Services\Dfs\Parameters:
DfsDisableSiteAwareness =1 as described in KB:810418, no difference.
Does anyone know why the clients are behaving like this with the DFS share?
/Anders