Guest_imported
New member
- Jan 1, 1970
- 0
I have a win2k network with windows 98 / NT4 and win2k pro client computers.
when running login script batch file (script.bat - writen below) from any 98 client it work OK.
when running this batch file (script.bat) from the server (netlogon share)
the following message appears:
"
cmd.exe was started with '\\servername\netlogon' as the current directory path.
UNC paths are not supported. defaulting to windows directory.
"
and then it runs the login script very very slowly (about 5 min.)
doring this time the whole network is halts and no one can work until the login script is done.
but if I copy the batch file to the win2k pro client computer and run it from the local win2k pro station
it works fine.
another thing is that when I try to copy any regular file (10MB) from the server to the win2k pro computers it copies it in seconds
when I try to copy any script.bat (500 bytes) file from the NETLOGON to the win2k pro client it takes 2 min.
ANY IDEA WILL BE APRRECIATED !!!
this is the login script:
REM Login script for Server 2000
REM Please do not change before consulting with Administrators
@SET HomeDrive=N:
net use I: /delete 2> NUL
net use K: /delete 2> NUL
net use L: /delete 2> NUL
net use M: /delete 2> NUL
net use N: /delete 2> NUL
net use O: /delete 2> NUL
net use K: \\netfinity\operations
net use L: \\netfinity\rta_data
net use M: \\netfinity\temporary
net use N: \\netfinity\workreports
net use O: \\netfinity\manufacturing
net use P: /delete 2> NUL
net use P: \\netfinity\Admin
net use y: /delete 2> NUL
net use y: \\netfinity\priority
when running login script batch file (script.bat - writen below) from any 98 client it work OK.
when running this batch file (script.bat) from the server (netlogon share)
the following message appears:
"
cmd.exe was started with '\\servername\netlogon' as the current directory path.
UNC paths are not supported. defaulting to windows directory.
"
and then it runs the login script very very slowly (about 5 min.)
doring this time the whole network is halts and no one can work until the login script is done.
but if I copy the batch file to the win2k pro client computer and run it from the local win2k pro station
it works fine.
another thing is that when I try to copy any regular file (10MB) from the server to the win2k pro computers it copies it in seconds
when I try to copy any script.bat (500 bytes) file from the NETLOGON to the win2k pro client it takes 2 min.
ANY IDEA WILL BE APRRECIATED !!!
this is the login script:
REM Login script for Server 2000
REM Please do not change before consulting with Administrators
@SET HomeDrive=N:
net use I: /delete 2> NUL
net use K: /delete 2> NUL
net use L: /delete 2> NUL
net use M: /delete 2> NUL
net use N: /delete 2> NUL
net use O: /delete 2> NUL
net use K: \\netfinity\operations
net use L: \\netfinity\rta_data
net use M: \\netfinity\temporary
net use N: \\netfinity\workreports
net use O: \\netfinity\manufacturing
net use P: /delete 2> NUL
net use P: \\netfinity\Admin
net use y: /delete 2> NUL
net use y: \\netfinity\priority