| Title: | POLYCENTER AssetWORKS + Microsoft Systems Management Server |
| Notice: | See note 937.1 for kit access information access |
| Moderator: | RDVAX::LEVY D |
| Created: | Wed Feb 23 1994 |
| Last Modified: | Fri May 30 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 977 |
| Total number of notes: | 3989 |
Does anyone know what SMSRUN16 may be doing in this scenario ?
A user running Win95 is not connected to the network (no cable pluggfed
in), but still goes
through the network logon process (to ensure they are logged on so
exchange will allow them to open their folders in offline mode). After
getting the message that there is no domain controller to validate
login, and ok'ing this, the system 'hangs' for approx 3 minutes.
Looking at the task-list shows SMSRUN16 in a "not responding" state.
Given time whatever was causing smsrun16 to 'hang' clears (or timesout)
and the system come up into windows properly.
We know smsrun16 is the process holding up the system because an
'end-task' on this process frees the system immediately.
I have tried;
-removing all pesistent network drive mappings
-removing all shortcuts from the startup folder
-removing the load= lines from smsrun16.ini
-setting the system to 'windws logon' instead of 'client for microsoft
networks' logon
If the user does not login (presses cancel at the logon screen) the
system comes up without hanging. I assum this means that smsrun16
thinks that the network exists and is trying to do something on the net
- but what I can't find in any docs.
Anyone got an idea of what's going on ?
Cheers,
Steve
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 948.1 | SMSRUN16 connects to the logon server SMS_SHR | SUBSYS::CARLETON | A paradigm shift without a clutch | Wed Feb 12 1997 11:24 | 14 |
I used to know what SMSRUN16 was doing in detail. I don't have access
to the SMS sources anymore so I have to go from memory.
I know that SMSRUN16 attempts to connect to the SMS_SHR share in
on its logon server. It will try each network transport on which
NetBIOS is supported. The node it needs to try to connect to
is saved in the hidden C:\SMS.INI file. You might be able to hack
this file so that, when you are running stand-alone, it will
try to make a connection to a share on the local system. You
would need to duplicate some of the domain and workstation files
that are normally found on the logon server.
| |||||
| 948.2 | Ta | KERNEL::WOODWARD | Smile! | Wed Feb 12 1997 11:30 | 3 |
Thanks for the quick answer and suggestion - I'll have a play,
Steve
| |||||