I finally found, or rather, understood the problem. It is that our password was not valid to Sles8 fixes, just for Sles7 stuff.
Getting the new password, turned out to be a major ordeal. It should have been just going to the Suse website and request a new password. However, we use Netscape 4.6 Trust. Netscape 4.6 doesn't work with some pages on the Suse website. The Suse support people said to use Netscape 7 or better. Well, Netscape 7 doesn't work with our internal Webservers, so it was blocked from being downloaded. This is our problem and scheduled to be worked on. So, I, thinking that I needed Netscape 7 or better for Suse maintenance, decided to finish bringing up Sles8 and then use it's funtion to access the Suse Website. Yep, this works but you can't ask for a password this way. The message that YOU comes back with states that you should try latter or try a different site. Didn't say anything about passwords so I continued to forget I needed a new password. (If I would have remembered, I would have requested one from my home pc running Netscape 7.) So I banged my head against the wall a few times before Suse support said that I needed a password. Douh! Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 05/30 7:59 PM >>> I applied the Yast updates and was able to run the Online Update without a problem. -----Original Message----- I'm trying to use the online update feature of Yast under Suse 8. First time though, ok. It wants me to download the recommended update for YOU (patch 5185). I do that, and Yast does its thing. I get fully out of Yast and back in. When I try to go to Software:Online Update:Package update (manual option): It brings up the Authorization screen (I kept the registration from before), do the login and I get: Initialization failed. Try again. If failure continues, shoose another SuSE FTP/HTTP serve. It seems like the updates for YOU, breaks YOU. If anyone has been down this path before, I would appreciate it if you "show me the way".
