CLI host registration over authenticating proxy not working

I am trying to register a new Solaris 10 server in Update Connection. It doesn't have any X libraries installed, so I can't run updatemanager, and it is behind an authenticating proxy.

It just does the following:

# sconadm register -a -r /tmp/registrationprofile.properties

sconadm is running

(waits a few minutes...)

Internet connection failure, please check proxy settings

The correct proxy details are in registrationprofile.properties, and I have also played with the -p/-x sconadm switches with the same result.

A truss shows the following files are not found, which may be the cause of the problem... I have not been able to find any packages that contain these files though.

stat64("/usr/lib/breg/resources/com/sun/cns/basicreg/common/ProxyManager.class" , 0xFFBFD0F8) Err#2 ENOENT

stat64("/usr/lib/breg/resources/com/sun/cns/basicreg/common/ProxyAuthenticator. class", 0xFFBFC5F0) Err#2 ENOENT

Can anyone help? For what it's worth the smpatch command gets through the proxy just fine (only to tell me that the server has not been registered... great).

[1129 byte] By [flint_m] at [2007-11-26 6:04:54]
# 1
If you're using a proxy then perhaps the http_proxy environment variable can help. The only other possibility I can think of is a router / proxy issue.Does "snoop" actually show the data going out to the proxy and can you see the proxy picking it up ?
LionO at 2007-7-6 13:31:25 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2

I don't believe it is a proxy issue... as I mentioned, the smpatch command gets through the proxy fine. I can also successfully use wget with the appropriate proxy variables set.

The sconadm command does talk to the proxy (202.12.142.21):

Using device /dev/ce (promiscuous mode)

138.217.5.181 -> 202.12.142.21 HTTP C port=32857

202.12.142.21 -> 138.217.5.181 HTTP R port=32857

138.217.5.181 -> 202.12.142.21 HTTP C port=32857

138.217.5.181 -> 202.12.142.21 HTTP GET http://www.sun.com HTTP/1.1

202.12.142.21 -> 138.217.5.181 HTTP R port=32857

202.12.142.21 -> 138.217.5.181 HTTP HTTP/1.1 407 Proxy Authentication Required

202.12.142.21 -> 138.217.5.181 HTTP R port=32857

138.217.5.181 -> 202.12.142.21 HTTP C port=32857

138.217.5.181 -> 202.12.142.21 HTTP C port=32857

138.217.5.181 -> 202.12.142.21 HTTP C port=32857

138.217.5.181 -> 202.12.142.21 HTTP C port=32858

202.12.142.21 -> 138.217.5.181 HTTP R port=32857

202.12.142.21 -> 138.217.5.181 HTTP R port=32858

138.217.5.181 -> 202.12.142.21 HTTP C port=32858

138.217.5.181 -> 202.12.142.21 HTTP GET http://www.sun.com HTTP/1.1

202.12.142.21 -> 138.217.5.181 HTTP R port=32858

It also seems to successfully pick up the proxy authentication details; the second "HTTP GET http://www.sun.com" request in the above exchange does include the "proxy-authorization" header, and the hash it uses looks identical to the ones generated by wget/smpatch.

However, this is the end of the transaction; after the above, there is a timeout period and then it gives the "Internet connection failure, please check proxy settings" error.

flint_m at 2007-7-6 13:31:25 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3
Hi!I have the same problem but without proxy definition. The computer is connected directly to my ISP router...Did anyone had any clue on this?Many thanks !GR.
God007 at 2007-7-6 13:31:25 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4

Are you getting the exact same error from sconadm, i.e: "Internet connection failure, please check proxy settings"?

Can you post output of "smpatch get" and the /tmp/registrationprofile.properties file, as well as some snoop output?

If you have a support contract you may wish to submit a support case for Sun support so that your issue can be investigated in depth without having to post any potentially sensitive information on this forum.

ForumModerator at 2007-7-6 13:31:25 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5

Hello!

I'm really sorry to tell you that and I really apologize for this but the system we were trying to update was not set on a correct date: the year was set to one back?That's the source of the error and now the system is updating.

Sorry for disturbing you about this.

Anyway, the sconadm program keep saying there was a problem with the network and not with date synchronization?br>

Many thanks for your help :-)

Godefroy Riegler

God007 at 2007-7-6 13:31:25 > top of Java-index,Administration Tools,Sun Update Connection-System...