SMS: Remote Control Using IPX Fails After Exiting Windows
Article ID: 174585
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft Systems Management Server 1.0 Standard Edition
- Microsoft Systems Management Server 1.1 Standard Edition
- Microsoft Systems Management Server 1.2 Standard Edition
- Microsoft Systems Management Server 1.0 Standard Edition
This article was previously published under Q174585
SYMPTOMS
If a Novell client is running Windows 3.1 and has UserIPX in its
Autoexec.bat file, Remote Control works fine before entering Windows and
during the Windows session. However, after the person who is remotely
controlling the client quits Windows, that person can no longer use Remote
Control on the client until UserIPX is unloaded and then reloaded again.
CAUSE
The main problem is the redirector code within the TSR. Systems Management
Server closes the code in Windows, but it still needs to be open if Systems
Management Server opens it within MS-DOS and then starts Windows.
STATUS
Microsoft has confirmed this to be a problem in Systems Management Server
versions 1.0, 1.1, and 1.2. This problem has been corrected in the latest
U.S. Service Pack for Systems Management Server version 1.2. For
information on obtaining the Service Pack, query on the following word in
the Microsoft Knowledge Base (without the spaces):
Additional query words: prodsms helpdesk
Keywords: kbtshoot kbbug kbfix kbnetwork kbremoteprog KB174585