Registration went smoothly and I can see my system under my subscription so credentials should be okay. Proxies are ok so now I don’t have any idea what might be wrong. I can get to that url fine from same network with my own desktop.
This looks like another content delivery system problem at first glance
and has been reported to Novell earlier today. I’ll post an update when I
see one.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
Silly question: have you tried changing your repository to point to the
new SCC instead of the NCC? I have no idea if this is the right thing for
this case, but the HTTP 410 is odd and maybe this is to help customers
transition to the new site in a more-visible way than using a 404.
For what it is worth, I ran a ‘zypper ref’ and pulled down a new
‘subversion’ package update this morning on my SLES 11 SP3 x86_64 system,
so maybe it’s specific repositories. If you ping nu.novell.com what do
you get back? From one part of the world I get 93.184.215.212 so if that
is not yours, perhaps hack your /etc/hosts file to force it and see if
that makes a difference.
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
It seems to be working now fine without any changes. So most likely a
problem at Novell end.[/color]
Yes it was a problem at Novell’s end which has now been resolved.
For anyone following this thread in future, unless officially advised to
do so by Novell don’t add a static entry for nu.novell.com to your
/etc/hosts file.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
It seems to be working now fine without any changes. So most likely a
problem at Novell end.[/color]
Yes it was a problem at Novell’s end which has now been resolved.
For anyone following this thread in future, unless officially advised to
do so by Novell don’t add a static entry for nu.novell.com to your
/etc/hosts file.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]
Hello, I’m troubleshooting same issue, my server can’t connect to nu…
in yast smt-server nu configuration,
I receiving mirroring credential invalid when I’m doing a test.
Cold you let me know what I should write as registration server url and as download server url ?
nu or scc or ncc ?
I’m lost.
Our firewall don’t let us ping so I can’t try, but I’m able to resolve nu.novell.com.
thank you
Hello, I’m troubleshooting same issue, my server can’t connect to nu…
in yast smt-server nu configuration,
I receiving mirroring credential invalid when I’m doing a test.
Cold you let me know what I should write as registration server url and
as download server url ?
nu or scc or ncc ?
I’m lost.
Our firewall don’t let us ping so I can’t try, but I’m able to resolve nu.novell.com.
thank you[/color]
Are you asking about registering “regular” SLES or mirroring via SMT
(Subscription Management Tool)?
With “regular” versions of SLES earlier than SLES12 you register servers
against Novell Customer Center (NCC) which then show up in SUSE Customer
Center (SCC). With SLES12 you register directly against SCC.
If you have SMT then you need latest SMT11 SP3 code (on SLES11 SP3) and
manually switch it over from NCC to SCC - please see TID 7015836[1].
Make sure you test your mirroring credentials within the yast SMT
module.[/color]
The above only applies to latest SMT11 SP3 code (on SLES11 SP3) and
doesn’t apply to individual SLES servers running versions of SLES
earlier than SLES12.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
