Solaris Registration Wizard authentication
I went to
http://www.sun.com/service/sunupdate/gettingstarted.html?cid=78607
as directed by the automated email from Sun, and downloaded
the Sun Update Connection installer. I ran the installer:
--
$ cd updateConnection
$ ls -al
total 72
drwxr-xr-x3 l41nstaff512 Apr 18 12:11 .
drwxr-xr-x3 l41nstaff512 Aug 1 20:44 ..
-rw-r--r--1 l41nstaff29042 Jul 20 2005 THIRDPARTYLICENSEREADME
-rwxr-xr-x1 l41nstaff3538 Apr 18 12:11 installUpdateConnection
drwxr-xr-x 10 l41nstaff512 Apr 18 12:11 patches
$ whoami
l41n
$ su
Password:
# pwd
/home/l41n/udc/updateConnection
# ls
THIRDPARTYLICENSEREADME installUpdateConnection patches
# ./installUpdateConnection
121454-02 is already installed on the system
121119-06 is already installed on the system
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
The following requested patches will not be installed because
the packages they patch are not installed on this system.
0 All packages from patch 121082-04 are patched by higher revision pa tches.
No patches to install.
#
I then proceed to click on the taskbar's green globe so that I can
begin downloading the standard set of basic security fixes/patches.
The Solaris Registration Wizard opens and takes my input.
After considerable delay, the Registration Wizard finally
outputs "Your login information does not match a valid Sun
account. Please try again."
My Sun online account username/password worked fine when
I went to the download, but for some reason the same
username/password combination is then subsequently rejected by
the server(s) at Sun to which the Solaris Registration Wizard
connects.
The username/password combination also works fine for logging
in to mysun.sun.com and to the discussion forums. Why would it
not work from within the Solaris Registration Wizard or its
commandline equivalent, sconadm?
The authentication process completed successfully during previous
registrations on the same machines.
# 1
Can you post the output of the following commands - # showrev -p | egrep -e '121454|121119|120336|121082|121564|122232|119789'# cat /etc/release
# 2
> Can you post the output of the following commands -
>
> # showrev -p | egrep -e
> '121454|121119|120336|121082|121564|122232|119789'
> # cat /etc/release
$ showrev -p | egrep -e '121454|121119|120336|121082|121564|122232|119789'
Patch: 121454-02 Obsoletes: 120777-03, 121087-02, 119108-07 Requires: 119575-02, 119255-06 Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWccccrr, SUNWccccr, SUNWccfw, SUNWccsign, SUNWcsmauth, SUNWswupcl, SUNWppror, SUNWpprou, SUNWcctpx, SUNWccinv, SUNWupdatemgru, SUNWupdatemgrr, SUNWccccfg, SUNWccfwctrl, SUNWppro-plugin-sunos-base
Patch: 121082-05 Obsoletes: Requires: 121454-02 Incompatibles: Packages: SUNWccccrr, SUNWccccr, SUNWccfw, SUNWccsign, SUNWcctpx, SUNWccinv, SUNWccccfg, SUNWccfwctrl
Patch: 121119-06 Obsoletes: Requires: 121454-02 Incompatibles: Packages: SUNWppror, SUNWpprou, SUNWupdatemgru, SUNWupdatemgrr, SUNWppro-plugin-sunos-base
Patch: 120336-04 Obsoletes: Requires: 121454-01 Incompatibles: Packages: SUNWpprou
Patch: 122232-01 Obsoletes: Requires: 121454-02 Incompatibles: Packages: SUNWcctpx
$ cat /etc/release
Solaris 10 6/06 s10x_u2wos_09a X86
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 09 June 2006
$
# 3
Update 2 of Solaris 10 comes with the Sun Update Connection toolset pre-installed. As such you already have the software installed and just need to proceed through the registration process.You do not need to download and install the software.
# 4
I am considering reinstalling with the "reduced networking" option to see if that will help
narrow down the problem. Does the minimal set of packages include all the functionality
needed for running sconadm, and if not, which additional package dependencies must be
satisfied in order for the registration process to work? Also, do the strings in the file
entitled "registrationprofile.properties" which is passed as an argument to the -r option
of sconadm need to be enclosed in quotes?
# 5
As per our previous post yuou should not need to install any software as the Update Connection software should be installed automatically with the Sol 10u2 build.
Can you clarify what the current issue is? You should be able to simply run the sconadm command now without installing or re-installing anything
# 6
When I click on the taskbar's green globe icon with the question mark (the one which starts
the Registration Wizard and Update Manager) and proceed through the process of entering
my username/password (the same username/password that I use to log in to this forum and
to log in to mysun.sun.com), I receive a dialog box which says "Your login information does
not match a valid Sun account. Please try again." If I try to register the OS using
"sconadm register -a -r <path-to-registrationprofile.properties>" or simply
"sconadm register -a", registration doesn't work either.
The only possible clues I have received so far which might help pinpoint the problem are a
"0.0.0.<host#>" symptom in the netstat output whose associated connection is stuck on
SYN_SENT, a "0.0.0.<host#>" message in the cacao log, and the fact that a nslookup of
its own hostname (both with and without the default domain appended) fails despite all
other DNS-related functionality being normal (/etc/inet/hosts, /etc/inet/nodename, resolv.conf,
/etc/hostname.rtls0, /etc/hosts, /etc/defaultrouter and ifconfig all have the correct ip address). Also, Solaris Management Console tries to find 0.0.0.<host#>:898 instead of <what appears in ifconfig>:898 whenever SMC is started.If I manually reset the ip address from <actual ip address> to 0.0.0.<host#> using ifconfig, SMC promptly connects to 0.0.0.<host#> and works normally, but if the correct ip address is used, it displays stopsigns in the toolbox.
There is probably some maddeningly obvious configuration detail somewhere which is missing or
incorrect, but I do not understand why the same process and setup worked perfectly during
registration of the 1/06 version.
# 7
Once you are sure your basic networking is not an issue, ie you can ping hosts on the Internet by name, please follow the instructions here: http://sunsolve.sun.com/search/document.do?assetkey=1-9-82688-1
If you still have problems, post the file /tmp/registrationprofile.properties and the command that you are you are using.
Also, check /tmp/basicreg<timestamp>.log for errors.
# 8
I think I may have figured out a possible solution: The Solaris workstation which thinks its ip address is "0.0.0.64" has a hostname of "0x0040". My Linux workstation, whose hostname is
"0x6350", will give a message "Trying 0.0.99.80..." if I do 'telnet localhost' with the telnet line
in /etc/inetd.conf commented out. My second Solaris workstation, which thinks its ip address is
"0.0.100.80", has a hostname of "0x6450" on rtls0 and "0x6451" on rtls1. On rtls1, it thinks its
ip is "0.0.100.81". Could it be that giving the node a name whose alphabetic characters happen to correspond to a hexadecimal number is somehow confusing and/or fooling the local hostname lookup mechanism, which doesn't realize that the hexadecimal "number" is intended as an alphabetic string? In other words, instead of doing 'telnet 0x0040" in a situation where the host is named
"0x0040", I end up with "telnet 64", which is an abbreviation for "telnet <this network>.64", and get 0.0.0.64 as a result. That might explain the "0.0.0.64 SYN_SENT" in my netstat -a output.
Maybe the Solaris Registration Wizard (and/or the Solaris Management Console) cannot handle hostnames which begin with the characters "0x." I am going to try changing the hostname to
something which cannot be misconstrued as a hexadecimal numeric constant by the system,
and see if that corrects the problem.
# 9
Changing the first character of the hostname from a zero to a capital 'O' seems tohave corrected the problem. sconadm outputs "finish registration!" and Sun UpdateManager is now working. Apparently, hostnames cannot begin with the string "0x".
