| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
What kind of things is IPC$ used for? And what kind of client
operation would cause a session to IPC$ be established and remain
established?
I've got a customer who has an NT v4.0 workstation that is in a
separate domain from his v5.0E PATHWORKS server. Yet just after
logging into his workstation's domain, we see his client has a share
connection to IPC$ as user GUEST. We also saw all a separate session
as user ADMIN. So we disconnected all shares and restarted his client
(so his auto-reconnects didn't occur). We still see the IPC$
GUEST connection from his client.
The v5.0E system has the patched pwrk$lmsrv.exe for the duplicate
session issue (where the username on one session is blank or guest).
Prior to the patch he would see dual sessions from all his v4 nt
clients. Now it's just his NT client.
The only thing in his startup folder was some fast-find utility;
we removed it but the IPC$ session still gets established.
Is there anyway to track what the NT client may be doing (short of a
network trace)?
Paul
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4242.1 | Problem or not? | VMSNET::P_NUNEZ | Wed Apr 02 1997 17:48 | 10 | |
Also, is this scenario of a GUEST IPC$ session and a "normal" session
(owned by the real username) ok? Is it normal to see such things on
occassion or is this a problem similar to that discussed elsewhere in
this conference about 2 sessions from nt clients and problems accessing
resources because the session got switch to GUEST?
Maybe I'm chasing a red herring?
Paul
| |||||
| 4242.2 | NT 4.0 redirector is attempting RPCs. | DUNKLE::MCDERMOTT | Chris McDermott - Software Janitorial Services | Fri Apr 04 1997 15:00 | 7 |
The NT 4.0 redirector is establising the session for doing RPCs. It attempts an RPC, which fails because its not supported by V5, an reverts to using LM2.2 SMBs instead. How's that sound? I don't know any of this as an absolute fact, but I guess that is what is going on based on the way that NT does things: try the latest and greatest, if that fails use the down-level metdod. | |||||