V
Vedran Vrbanc
Hello,
I have the following problem:
When accessing a shared folder with a large number of files/subfolders
(around 2000) from any XP client, opening the folder takes 5-6 seconds.
Performing the same task from any win98 client takes less than a second.
The shared folder is located on a win2003 server (pure file server, static
addressing through lmhosts, no domain).
However, in another environment I haven't noticed any such slowdowns in the
similar scenario: XP client, large shared folders, BUT: the XP client and
the file server are domain members (the server is not the DC itself).
I am guessing that this is an XP authentication issue but I can't think of
anything to alleviate this problem. Currently, the authentication is set up
so that I have the same username/password on both the client and the
server. Is this a bad practice?
I have tried mapping the share through the IP address but it didn't help.
TCP/IP is the only protocol used.
Kind regards,
Vedran
I have the following problem:
When accessing a shared folder with a large number of files/subfolders
(around 2000) from any XP client, opening the folder takes 5-6 seconds.
Performing the same task from any win98 client takes less than a second.
The shared folder is located on a win2003 server (pure file server, static
addressing through lmhosts, no domain).
However, in another environment I haven't noticed any such slowdowns in the
similar scenario: XP client, large shared folders, BUT: the XP client and
the file server are domain members (the server is not the DC itself).
I am guessing that this is an XP authentication issue but I can't think of
anything to alleviate this problem. Currently, the authentication is set up
so that I have the same username/password on both the client and the
server. Is this a bad practice?
I have tried mapping the share through the IP address but it didn't help.
TCP/IP is the only protocol used.
Kind regards,
Vedran