Results 1 to 3 of 3
My first expirence with Linux was with a box version of Suse 10.2. The 90 day installation techs were confused but we got it to go on line. After getting ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 01-31-2009 #1
- Join Date
- Jan 2009
Can't get online !
My first expirence with Linux was with a box version of Suse 10.2. The 90 day installation techs were confused but we got it to go on line. After getting familiar with the distro, I found that reinstalling it was the answer and never had another problem. Board, I downloaded the 10.3 open Suse and could not get it to go on line no mater what configuration that I tried. I read other peoples threads and got encouraged to try other distros like Fedora, , Mandrivia...All with no luck. Then I tried Ubuntu 8.4 and Wow! it's a breeze. I stuck with it for a while until 8.10 was released and installed it with no problem except the graphics needs work in the installation partitioning section and upon installing k3b the graphics are non existent while burning iso images but works well if you guess at it. Now I have a new, large, hard drive and want to compare. So I triple booted Windows XP, [back] to Ubuntu 8.4 ('cause it works Great!) and I downloaded, via Bit torrent, SUSE 11.1, Twice, and burnt, 2 DVDs ....Both of them, wont go on line no mater what I do. I went back to Ubuntu and wrote down some numbers that might help and for a brief time, I got some updates and then it wouldn't go on line any more. I have a Dell Dimension 8200 workhorse, with 512 meg RAM, a Davicon 21 x 4 x DEC - Tulip compatible 10 / 100 Ethernet plugged straight into the phone companies DSL modum/Routor via Ethernet cable. The phone company says that they don't use IPV6 that their still on IPV 4. I've just been pushing buttons for days now and then reinstalling, afterwards downloading a new copy and burning iso as slow as I can...I'm out of answers ??? HELP !
I just did a clean reinstall and didn't touch a thing untill I hear from a Wizard. or some kind soul.
- 01-31-2009 #2
- Join Date
- Sep 2008
Have you checked your network settings? Do you manually set up a network address or have you got a dhcp server in the router?
I presume you are using either ubuntu or windows to go online, so check the settings there.
You are wanting to find out the following:
ipaddress (or dhcp set on)
To get these details:
In linux open a terminal and type /sbin/ifconfig
In windows: run ipconfig /all at a command prompt
Once you have these go back to suse and fo to yast>net devices>net settings.
Make sure the hostname/dns and routing information is correct.
Once set, you should be able to ping the router and check the nameserver works by doing an nslookup for a known site.
Your system would probably respond a bit better if you had more ram.
- 01-31-2009 #3
- Join Date
- Jan 2009
can't get on line in Suse
Your right about having UBUNTU. I did look at its settings, but in hast. I'll go back with your list and check more carefully.
In the mean time...Dig this:
If I clicked on the FireFox browser after turning the power off and then back on to the router, it would work. I immediately started downloading the updates (for a new install) and it would stop in the middle of a download. I would then recycle the power and time the 're-try' button to when it started back up and got all the downloads. When I went to restart the computer the grub was missing and I just now got the Ubuntu back on line.
What this tells me is that the speed setting is wrong in the Yast DSL configuration. I know that I get 130 Bytes download and 63 Bytes up. The online clock test is measured in bits and it reads 1024 down and I can't remember what it was up but less than half of that.
In Yast I thought that I tried both these settings, but it wouldn't go on line unless I cycled the power to the router.
I thought the Updates would fix this but I have to reinstall Suse again to try it.
I'll check the UBUNTU settings first. I remember this happening a year ago when I was trying to install Suse 10.3 ...In 10. 2 the configuration menu was different and this never happened.