Results 1 to 5 of 5
I downloaded 10.3 after messing with 10.0 for a short while. With 10.0, I was able to connect to the internet using a wireless adapter after "disabling" the network card.
...
- 10-10-2007 #1Just Joined!
- Join Date
- Oct 2007
- Posts
- 3
Can't connect to router in SuSE 10.3
I downloaded 10.3 after messing with 10.0 for a short while. With 10.0, I was able to connect to the internet using a wireless adapter after "disabling" the network card.
I installed 10.3 over 10.0 and had issues connecting to the network with the wireless. I had time today, so I decided to wipe the drives in the computer and with a fresh install of 10.3.
Prior to the install, I moved the computer closer to my router and then hooked up the computer to the router using an ethernet cable. However, it still will not connect to the router. I doubt the problem is the cable itself because while toying around with some of the settings, I opened up my router's config page using my XP machine and could see the linux machine was connected to the router but I still was unable to connect to the network. As it stands right now, when I ping the router (192.168.1.1), I get the following:
After browsing this forum and another linux forum. I gathered all the information I could find. I appreciate your help in advance and please let me know you require any other information.connect: Network is unreachable
Here are the options I have in YaST:
Global Options
Hostname/DNSNetwork Setup Method: Traditional Method with ifup
IPV6 is not enabled
DHCP Client Options: Identifier is empty, Hostname to Send is "HERMES"
RoutingHostname: HERMES
Domain name: home
change hostname via DHCP is not selected
write hostname to /etc/hosts is selected
update DNS data via DHCP is selected
Network Card Setupgateway is empty
expert configuration is not selected and the table is blank
enable IP forwarding is not selected
This is what I get if I use ifconfigactivates on cable connection
firewall is disabled
IP address is dynamic via DHCP
and if I use cat /etc/resolv.confHERMES:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:FC:53:BB:E7
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11 errors:30 dropped:10615388 overruns:11 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2651 (2.5 Kb) TX bytes:25960 (25.3 Kb)
Interrupt:20
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700 (700.0 B) TX bytes:700 (700.0 B)
HERMES:/etc # cat /etc/resolv.conf
#
search comcast.net
- 10-10-2007 #2Just Joined!
- Join Date
- Sep 2004
- Location
- Luxembourg
- Posts
- 8
Same thing happened to me with a 10.2 to 10.3 clean install.
First thing was the network card was identified but not configured in YAST, that fixed, it still didn't work. On a whim, I rebooted both the PC and the router simultaneously. That did it, but please don't ask me why, I have no idea.
At least it's easy to try.
- 10-10-2007 #3Just Joined!
- Join Date
- Oct 2007
- Posts
- 3
Sorry, I should have added that right now, it doesn't show up as an attached device (when the linux machine is turned on -- it's off right now).
I'll try rebooting them, though, a little later today when I have the time. If it works, I'll let you know.
- 10-10-2007 #4Just Joined!
- Join Date
- Oct 2007
- Posts
- 3
Rebooting both didn't help.
- 10-11-2007 #5Just Joined!
- Join Date
- Aug 2007
- Posts
- 17


Reply With Quote
