Bug 152061 - YOU fails with "Cannot fetch remote server list"
Summary: YOU fails with "Cannot fetch remote server list"
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-18 22:26 UTC by Shaun Qualheim
Modified: 2006-02-22 20:06 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Yast Logs for bug 152061 (369.37 KB, application/x-gzip)
2006-02-18 22:29 UTC, Shaun Qualheim 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shaun Qualheim 2006-02-18 22:26:34 UTC 
Hey everyone:

I just installed beta 3 a few days ago on my box and went to try to do a "software update" launched from yast2 and I get the following after a few minutes:

"Cannot fetch remote server list. Only user-defined patch sources will be available."

It tells me to check the network connection and says the following under details:
"
URL: http://www.suse.de/cgi-bin/suseservers.cgi
couldn't connect to host
"

But.. I can ping/ssh/browse the web fine.  I can even open up that list of servers directly using that URL in konqueror.  

Any ideas?

Thanks!
Shaun
Comment 1 Shaun Qualheim 2006-02-18 22:29:15 UTC 
Created attachment 69191 [details]
Yast Logs for bug 152061
Comment 2 Michael Gross 2006-02-20 12:19:38 UTC 
Might be a network-problem nontheless. Please try it one more time, if it still fails, I will reassign it.
Comment 3 Shaun Qualheim 2006-02-22 20:06:10 UTC 
Ok, so appearently, it had to do with the fact that I had set the machine to look at the gateway (DSL Modem box) for name services... which it's supposed to be capable of, but which appearently isn't working correctly.  When I set the nameservers in resolv.conf to the ISP's IPs for such, it worked fine.