Disconnecting Null Session Disconnects Normal Sessions Too
Article ID: 101721
Article Last Modified on 10/31/2006
APPLIES TO
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
This article was previously published under Q101721
SUMMARY
If Server Manager is run on a server, a particular client has both
normal and null sessions connected to that server, and the client has
files opened over the normal session, telling Server Manager to
disconnect the null session disconnects both sessions with no warning
about the open files.
RESOLUTION
Be very careful when disconnecting null sessions. If you really need
to disconnect \\CLIENT from \\SERVER, disconnect all normal (non-null)
sessions first. This will give you the appropriate warnings about open
files.
Additional query words: prodnt
Keywords: kbnetwork KB101721