Slow UNC connection

  • Thread starter Thread starter Mickey Sauk
  • Start date Start date
M

Mickey Sauk

Hi all,

we currently have a platform of NT and W2K servers that communicate to each
other using ms-dos scripts.
One of these scripts run on a W2K server contains a test of existence for a
folder on a remote NT server (if \\server1\log\405 exists then xcopy ...).
This test randomly fails because the folder is not found (and it exists !).

If we make a simple test of unc connection via the start/run menu of the
W2k (\\server1\log), it is indeed longer than a connection between two nt
or W2k systems.
We suspect that the script fails because of a timeout for the UNC
connection.

Does anybody have an idea ?
Thank you

/MS
 
Are they all in the same domain?
Do all computers point to the same DNS (internal DNS)?
Do you have a WINS server setup, and do all computers point to that server?


Arild
 
Yes all systems are in the same domain.
There's no DNS, systems are configured to use lmhosts resolution.
No Wins server.
 
If you have W9x, ME or NT4 clients, you need WINS. Also options 044 and 046
(0x8) should be set in DHCP-server, Scope options.
 
Back
Top