Unexpected Net Use behavior
Seahawk60B
desktop, some do various published applications.
Presentation Server 4.0 on Windows Server 2003 SP2
We have the following section in our usrlogon.cmd file to map local
client drives for users that are in the Citrix-MapDrives AD group:
"C:\Program Files\Windows Resource Kits\Tools\ifmember.exe" "Citrix-
MapDrives"
If ERRORLEVEL 0 If not ERRORLEVEL 1 goto cont
Net use I: \\client\A$
Net use J: \\client\C$
Net use K: \\client\D$
Net use L: \\client\E$
:cont
This script has run fine for over two years, but suddenly this morning
it started behaving differently. Prior to this morning, if a user did
not have either an A,C,D, or E local drive, the usrlogon.cmd would
throw a system error 55 and continue on. Now however, if it finds a
non-existent client drive, it throws a prompt for a user name and
password, then returns the system error 55 (regardless what user name
and password is provided - i.e. it's not actually checking
credentials, but requests them anyway.) See below:
This is an issue because usrlogon.cmd sits minimized on the task bar,
waiting for a user name input, but the user doesn't see it unless they
open up the usrlogon.cmd. All they see is the Windows login screen
sitting at "Running logon scripts"
If user has no client drives to map, then the desired behavior/output
of the above batch file is:
System error 55 has occurred.
The specified network resource or device is no longer available.
System error 55 has occurred.
The specified network resource or device is no longer available.
System error 55 has occurred.
The specified network resource or device is no longer available.
System error 55 has occurred.
The specified network resource or device is no longer available.
However, the current behavior, that just started happening is:
The password or user name is invalid for \\client\A$.
Enter the user name for 'client': aaa
Enter the password for client:
System error 55 has occurred.
The specified network resource or device is no longer available.
The password or user name is invalid for \\client\C$.
Enter the user name for 'client': aaa
Enter the password for client:
System error 55 has occurred.
The specified network resource or device is no longer available.
The password or user name is invalid for \\client\D$.
Enter the user name for 'client': aaa
Enter the password for client:
System error 55 has occurred.
The specified network resource or device is no longer available.
The password or user name is invalid for \\client\E$.
Enter the user name for 'client': aaa
Enter the password for client:
System error 55 has occurred.
The specified network resource or device is no longer available.
In a nutshell, I need to know why the net use command is no longer
throwing an immediate system error 55, but is instead stopping the
usrlogon.cmd script waiting for a user name input.
Seahawk60B
to their previous behavior. We have some MPS reports and dumps of the
Citrix redirector that MS and Citrix are looking at, however, if
anyone has any insights into what may have caused the behavior to
change in the first place it would be appreciated.
infecticide
How often to you reboot your machines? Anything past a week in my
experience start to cause weird issues, they are Windows machines
after all.