Conference noted::pwv50ift

4204.0. "username changes to guest when connecting to alias" by NETRIX::"[email protected]" (Robert Milberger) Thu Mar 13 1997 09:33

Hi there,

I have a customer who has just upgraded from 5.0c-eco03 to 5.0e
and now has some strange problems.

It seems, that this problems are the same as described in Note 3713 and 3616.
(but never answered)

2 Node Cluster 
One node is an Alpha one a VAX.
On both machines they have TCPIpware running.
Licensing is Server based.
Lanmanager protcols are Netbeui and TCPIP.

Now, when the customer connects from a NTWS4.0 SP2 to the Cluster
alias it looks like this:

net sess

\\MATSCH               SCHMIDR              DOS LM 2.1       0     01:01:00
\\MILANO               GUEST                OS/2 LM 2.1      0     00:24:00
\\MILANO               DIRNWEBE             OS/2 LM 2.1      0     00:33:00
\\NAGANO               STOCKER              DOS LM 2.1       0     00:00:00
\\OXFORD               MIDI_EBERM           DOS LM 2.1       0     00:48:00
 
you see that node milano is connected two times, one times
with the right user and one times with guest.

net sess \\milano

Username        GUEST
Computer        MILANO
Guest logon     No
Client type     OS/2 LM 2.1
Sess time       00:36:00
Idle time       00:26:00
Sharename      Type     # Opens
------------------------------------------------------------------------------

RZ             Disk     0
The command completed successfully.

The problem is, that the customer can sometimes (if he is lucky)
see his files in share RZ sometimes (most times) not.
He gets a windows on his NT WS witch queries for a username and password.

are there any explanations that I can give to the customers?
As I can see, this is a behaviour that exsists since 5.0d?

Customer swears, that had not this problem with 5.0c-eco03.

any help is very appreciated,

robert  
[Posted by WWW Notes gateway]

Also discussed in 4198 and probably a few others.

Some of these issues are resolved in V50E-ECO1, can't say for sure if yours is.

There has been a QAR entered which may get fixed for the next release, which
will likely be called V50F.

IPMT it if you want it fixed and get a patch sooner.  Make sure you reference 
these notes in the IPMT.

Hi,

thanks for the quick response,
I have spoken to the customer, he will wait for
PWVMS 5.0e-eco01. (hopefully it will be out within 2 weeks??).
If it is not fixed there we will escalate it.

...robert
[Posted by WWW Notes gateway]

    Been on customer site, saw the problem,
    found probable cause (both a problem in Windows NT - is
    reported to MicroSoft) and a problem that was introduced 
    in a bugfix in v50e.
    
    Customer will fieldtest fix this week. 
    
    So the problem is NOT fixed in e eco 1, and for a fix you
    need to escalate a ipmt.
    
    Adrie