ADSM-L

NT client 3.1.0.5, problems!!

1998-08-19 07:30:05
Subject: NT client 3.1.0.5, problems!!
From: "Lambelet,Rene,VEVEY,FC-SIL/INF." <Rene.Lambelet AT NESTLE DOT COM>
Date: Wed, 19 Aug 1998 13:30:05 +0200
Hello,

as you can see, the 3.1.0.5 seems to have to be improved before any roolout.

Therefore, we decided to install only 3.1.0.5 on HP-UX and Netware.

For NT clients, we canceled any installation and will wait for 3.1.0.6!!

Regards,

René Lambelet - *3543 - *A581 
Nestec SA - 55, Av. Nestlé - CH-1800 Vevey
Tel: ++41/21/924'35'43 / Fax: ++41/21/924'45'89
E-Mail: rene.lambelet AT nestle DOT com



> -----Original Message-----
> From: Sheelagh Treweek
> [SMTP:sheelagh.treweek AT COMPUTING-SERVICES.OXFORD.AC DOT UK]
> Sent: Wednesday, August 19, 1998 1:21 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> 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
<Prev in Thread] Current Thread [Next in Thread>
  • NT client 3.1.0.5, problems!!, Lambelet,Rene,VEVEY,FC-SIL/INF. <=