| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4254.1 | | CTHU22::M_MORIN | Mario Morin, Hull CSC - Canada | Tue Apr 08 1997 17:52 | 8 |
| Just checked and same problem occurs on patched VAX as well.
When I try from W95 clients, no problems.
Am I overlooking something obvious here or is the patch not
doing what it's supposed to do?
/Mario
|
| 4254.2 | see 4242 | VMSNET::P_NUNEZ | | Wed Apr 09 1997 09:57 | 7 |
| Mario,
You too eh? See 4242. I think it's WNT that's the culprit.
But I'm not sure it's even a problem...guess a trace will
tell the story.
Paul
|
| 4254.3 | | UTRTSC::SWEEP | I want a lolly... | Thu Apr 10 1997 06:59 | 6 |
| This is normal behaviour, don't worry.
I normally take 2 aspirines and go to bed early
when I encounter NT workstations.
Adrie
|
| 4254.4 | | CTHU22::M_MORIN | Mario Morin, Hull CSC - Canada | Thu Apr 10 1997 10:17 | 7 |
| And when you get up in the morning the problem has gone away?
I wish this was the case for me :-(
Confused...
/Mario
|
| 4254.5 | | PTGSYS::SWEEP | I want a lolly... | Thu Apr 10 1997 11:44 | 37 |
| OK lets explain
Windows NT when you log on remembers the username and
password.
When you make a connection to a share, it uses that
username and password, or the ones you supplied when
connecting to the share. This session shows up as a
session with your username.
Now at some moment NT decides to do some administrative
functions. It therefore connects to IPC$. When it connects
to IPC$ it uses a blank username (don't ask me why??).
This IPC$ connection is left open for the duration of
your username's life (login time). Now when you show this
session it either shows a blank username or if guest is
enabled the name guest.
This is where the session comes from.
The session patch you are talking about resolves the
problem where you would get the noaccess errors.
When the IPC$ connection with the blank username
was made, the origional session (with the username)
was by accident marked as a blank session.
LM uses blank usernames to identify a session that
is only allowed to do a limited nr of smb requests.
So for other requests the server returns a noaccess
error.
Adrie
Hope you're no longer confused but if you still are,
I still have some aspirines ;-)
|
| 4254.6 | | CTHU22::M_MORIN | Mario Morin, Hull CSC - Canada | Tue Apr 15 1997 13:34 | 13 |
| Here's a twist to the problem:
Assuming I had selected the "reconnect at logon" box when
I connected to the share on the PATHWORKS server:
If I logoff from the NT 4.0 WKSTN I then see that the session
on the server disappears.
If I log back on and re-click on the network drive, to
re-establish the session, then check on the server, I then
only see my 1 session. The one with GUEST disappears.
/Mario
|