OS/2 Client Logon Script Fails if Server Name Contains Blanks (122446)
The information in this article applies to:
- Microsoft LAN Manager 2.2
This article was previously published under Q122446 SYMPTOMS
If a Lan Manager version 2.2 server has a computer name that contains blank
spaces ("TEST SERVER", for example), the following error messages may
appear on an OS/2 2.x client when you try to execute a logon script:
- NET2122: An error occurred while loading or running the logon script.
- SYS1041: The name specified is not recognized as an internal or
external command, operable program or batch file.
After these errors appear, the connection to the server is successful.
WORKAROUND
To work around this problem, change the name of the server to a name that
does not contain any blank spaces.
STATUS
Microsoft has confirmed this to be a problem in LAN Manager version 2.2. We
are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
These error messages only appear when you run a logon script that includes
the NET USE command from a computer running OS/2. If you run the same logon
script from a LAN Manager client running MS-DOS, no errors will appear.
Modification Type: | Major | Last Reviewed: | 9/30/2003 |
---|
Keywords: | KB122446 |
---|
|