No access to the local network (Suse 9.2)

Brian Knoblauch · 03-07-2005, 10:40 AM

It all seems very strange to me. I've been using SuSE for *many* years on a wide variety of hardware. I can't even begin to count all the SuSE machines I've had and I've never seen anything like this! :-) Did you change any settings during install? What "non default" options have you setup in Yast, etc?

ultra99 · 03-07-2005, 10:53 AM

Quote:

Originally posted by camorri
ultra_99

The ping command is run from the command line. Type "ping (the ip address you want to get to)"

example: ping 192.168.1.1

If it works ti will look like :

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=250 time=0.629 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=250 time=0.623 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=250 time=0.623 ms

--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms

If you get 100% packet loss, then it failed.

I did that and it went on beyond 4000! ....icmp_seq=4034 ttl.... so i quit and booted to windows and i writing this now. Is that normal?

ultra99 · 03-07-2005, 10:55 AM

Quote:

Originally posted by sharkzf6
I can tell you from my own experience that SuSE seems to have a major issue with local networking. I never got it working and quit using it because of that. My situation was almost identical to yours. It works fine with Debian, Ubuntu and (Slackware - except printing - see my post on that). Go figure.

What about Mandrake, do you know if there are problems with this distro? I want something that user friendly, almost like windows.

Brian Knoblauch · 03-07-2005, 11:15 AM

Quote:

Originally posted by ultra99
I did that and it went on beyond 4000! ....icmp_seq=4034 ttl.... so i quit and booted to windows and i writing this now. Is that normal?

That's normal. You can either set a number to stop at, or you can ctrl-c out after a couple. Were they successful?

ultra99 · 03-07-2005, 11:35 AM

Quote:

Originally posted by Brian Knoblauch
That's normal. You can either set a number to stop at, or you can ctrl-c out after a couple. Were they successful?

I dont know if they were successful or not. I exited it before completion.

Brian Knoblauch · 03-07-2005, 11:45 AM

Quote:

Originally posted by ultra99
I dont know if they were successful or not. I exited it before completion.

It doesn't "complete", it's a continuous test... Can you show us what you got out of it? First 5 lines is plenty (assuming there were no major differences).

ultra99 · 03-07-2005, 11:54 AM

I started the ping again and use ctrl-c to stop the process. And i got the following:

16 packets transmitted, 16 recieved, 0% packet loss, time 14997ms
rtt min/avg/max/mdev=0.064/0.072/0.08/0.010 ms

susefan · 03-07-2005, 11:55 AM

I have been running suse distributions since 6.1 (currently running 9.2)
and I have never had a local network issue.

Try this:
Open up YAST (on both machines on your lan) and disable the firewall.
If that solves your problem, and you still want the firewalls running
on each machine, find out what ports are used by the game, and
open them individually.

Brian Knoblauch · 03-07-2005, 12:17 PM

Quote:

Originally posted by ultra99
I started the ping again and use ctrl-c to stop the process. And i got the following:

16 packets transmitted, 16 recieved, 0% packet loss, time 14997ms
rtt min/avg/max/mdev=0.064/0.072/0.08/0.010 ms

OK, your computer is talking to the local network just fine. What *exactly* are you having problems with?

camorri · 03-07-2005, 12:21 PM

ultra99,

Quote:

16 packets transmitted, 16 recieved, 0% packet loss, time 14997ms
rtt min/avg/max/mdev=0.064/0.072/0.08/0.010 ms

16 sent and 16 received and 0% loss is perfect, can't get better.

I posted a sample earlier, to show what you should see. Yes Ctrl-c will cancel on Linux.

ultra99 · 03-07-2005, 12:32 PM

Quote:

Originally posted by Brian Knoblauch
OK, your computer is talking to the local network just fine. What *exactly* are you having problems with?

The problem is that i cannot connect to the internet. Cannot surf the internet, and cannot use Yast for updates either.

In windows, I had to manually write in the DNS and Alternate DNS, along with the IP and Submask. I can't find a way to add the DNS in suse. Where do i go exactly?

Brian Knoblauch · 03-07-2005, 12:34 PM

Quote:

Originally posted by ultra99
The problem is that i cannot connect to the internet. Cannot surf the internet, and cannot use Yast for updates either.

In windows, I had to manually write in the DNS and Alternate DNS, along with the IP and Submask. I can't find a way to add the DNS in suse. Where do i go exactly?

Oh, insert your nameservers into /etc/resolv.conf

nameserver x.x.x.x
nameserver y.y.y.y

That's all there is to it.

ultra99 · 03-07-2005, 12:41 PM

Quote:

Originally posted by Brian Knoblauch
Oh, insert your nameservers into /etc/resolv.conf

nameserver x.x.x.x
nameserver y.y.y.y

That's all there is to it.

I assume:
x.x.x.x is for the DNS
y.y.y.y is for the Alternate DNS

What do i write under namserver?

Brian Knoblauch · 03-07-2005, 12:47 PM

Quote:

Originally posted by ultra99
I assume:
x.x.x.x is for the DNS
y.y.y.y is for the Alternate DNS

What do i write under namserver?

That's correct. I don't know what you mean by "write under nameserver". Those 2 lines are a complete config file. You can also add a "domain blahblah.net" if you want to have domain search turned on.