| Title: | Windows NT |
| Notice: | See note 15.0 for HCL location |
| Moderator: | TARKIN::LIN .com::FOLEY |
| Created: | Thu Oct 31 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6086 |
| Total number of notes: | 31449 |
Hi all,
just wanted to check if someone has seen something like this before.
A customer reported that he all of a sudden couldn't access shares on
his pathworks V5 server from his two Windows NT V3.51 SP5 workstations.
Access from WFW3.11 systems using the same account on the V5 server
worked problemfree.
I checked it out and found that the NT workstations were connected as
GUEST to the share even though they were logged on with a proper username
and password.
Creating a new account on one of the Windows NT workstations, still
with the same username and password solved the problem...so it seems
like the username/password information that the Windows NT workstation
handed over to the pathworks V5 server upon connection had somehow
become "corrupt", this is only an assumption though.
Has anybody seen this behaviour before, is there a way to "clear out"
the "buffers" that holds the username/password information used when
connecting to a LAN Manager server?
In this case the Windows NT workstation was member of a workgroup with
the same name as the Pathworks V5 LAN Manager domain.
Ohhh...one more thing, if the customer desides to create new accounts on
his Windows NT workstations he will lose all information about the
desktop etc etc.
Is there a way to remove an account and then add an account with the
same name and keep the "old user profile"?
Regards
Bjorn Lundberg
CSC Sweden
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5624.1 | anyone? | MAZE::FUSCI | DEC has it (on backorder) NOW! | Wed Mar 05 1997 12:08 | 20 |
I believe I am experiencing the same problem, and offer this additional
information:
My scenario:
At random times, my NT V4.0SP2 users will be unable to access shares on my
Pathworks V5.0E (and V5.0D) server. As .0, when the users get into this
state, checking on the Pathworks system shows that they have somehow become
connected to the share as GUEST.
If the user disconnects and reconnects the share enough times, they will
eventually get connected properly. ("Enough" has ranged from 1 to 15.)
This only happens to my NT users. WFW V3.11 and W95 users have not
reported this problem.
(My Pathworks server only offers TCP/IP, I have DECnet and NETBEUI
disabled.)
Ray
| |||||
| 5624.2 | Bug in Pathworks V5.0E ? | STKAI1::BLUNDBERG | It's the monster!!! | Thu Mar 06 1997 00:49 | 20 |
I believe that we both hit a bug in the pathworks V5 for OpenVMS
server that makes the server authenticate the windows NT client on
a session without a username.
This bug was fixed in V5.0D-ECO3 but seems to have "surfaced" again
in a similar way in V5.0E.
This is MY opinion and it is not official in any way.
The problem my customer was experiencing was definately "solved" when he
downgraded pathworks from V5.0E to V5.0D-ECO3.
More information about this can be found in NOTED::PWV50IFT note 4155 or
in IPMT case CFS.49378
Cheers
Bjorn
CSC Sweden
| |||||