I've had something similar and after 6 months, off and on, between my network people and Suse, what I found was:
First, sorry about the explanation. I'm not at that site and don't have access to my notes...
The firewall was requiring a "certificate" every 5 minutes. We would connect in using Yast, that got us the certificate. It took about 3.5 minutes for me to navigate the menu items and start the download. We would start downloading, but after 1.5 to 2 minutes, the download stream, slowed to nothing. Eventually we would time out.
Now I could download via a web access from home. So the temp solution was to download the service pack and burn a CD.
Eventually, I found that I could download via a web access from work.
Eventually, I found that I could bring up the GUI interface up on my PC, then bring up Mozilla and then download directly via the web interface. (It took about 20% CPU utilization just to support the GUI interface.)
Apparently, a web browser will obtain a new certificate when necessary.
Of course, you could also have the network people open up a path in the firewall to the IP address to Suse. Then YOU works just fine.
Tom Duerbusch THD Consulting
Nick Laflamme wrote:
I'm trying to use YAST on an SLES8 to get on-line updates for the first time. (Well, not the first time I've tried, but when it works, it'll be the first time I've gotten it to work!) Alas, the "Online Update" option in the curses variant of YAST is a bit too terse, just eventually saying, "Cannot connect to www.suse.de. Check your connection." My network folks assure me that the first layer of firewalls is seeing and permitting the HTTP transaction from the Linux guest to the IP address that corresponds to www.suse.de. In fact, they see about six HTTP transactions, about ever minute and a half (or slightly longer). We haven't yet sniffed the traffic, so we don't know if those are six failures with a retry 90 seconds later, or what.
I'm sure I'm missing something simple here, but this YAST front end is protecting me from myself to an excessive degree. Is there a curses-based browser I should be using to verifying the basic connectivity before going further? Should I throw away the YAST training wheels and use a command from an SSH session to do these "online updates" in some verbose mode? If so, which command, please? :-)
Working on writing Chapter 4 of "SLES8 for Stubborn VMers", Nick
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
