Hi Sheelagh!

Did this problem with the communications error only occur after changing the
computer name? I've installed 3.1.0.5 on top of 3.1.0.3 and did not see this
problem otherwise.

I believe that the computer name is used as part of the encryption scheme when
the ADSM password is encrypted into the Registry. I was able to recreate a
similar (but not exact) problem using 3.1.0.3 just now (I don't have 3.1.0.5 on
my laptop yet). If I change the computer name, the first time I try to connect
with the GUI, I get a communications error. The second time, it prompts me for
the password, which is encrypted and thereafter I don't see the problem.

Best regards,

Andy

P.S. Check out the BACLIENT.TXT file for information on the change to UNC names.

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 08/19/98 04:26:44 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Win32 client V3 PTF 5 : changing the computer name



Trying out the W95 V3 PTF5 client gives an interesting problem which may be
related to the new Universal Naming Convention ...

On my PC instead of the filespace name being SHEELAGH it is now "\\oucs\c$".

Looking at my network setup I changed that the computer name to "blue" (I
hadn't taken any notice of this config before).  On trying the ADSM backup
GUI, it just gave a communication error.  On the server you see :

19-08-1998 11:14:11  ANR0406I Session 101 started for node BLUE.OUCS
                      (Win95) (Tcp/Ip 163.1.32.197(1026)).
19-08-1998 11:14:11  ANR0424W Session 101 for node BLUE.OUCS (Win95)
                      refused - invalid password submitted.
19-08-1998 11:14:11  ANR0403I Session 101 ended for node BLUE.OUCS (Win95).
19-08-1998 11:14:11  ANR9999D smexec.c(1041): Session 102 with client
                      BLUE.OUCS (Win95) rejected - server does not support
                      the UNICODE mode that the client was requesting.

If you then use the command line interface, you get asked again for the
password and then the session works.  Retrying the GUI after this also
works.

There looks to be some interaction with saving the encrypted password and
the computer name in the network config.

I can see that when we roll out the client others will notice that their
configuration isn't what they expect (because instead of seeing SHEELAGH as
the filespace name they see NOTCONFIGUREDRIGHT) and change it.

I must admit I hadn't come across this Universal Naming Convention before :
I quite liked it that the name of the drive was used.

Regards, Sheelagh
--
Regards, Sheelagh
Regards, Sheelagh