I've got SuSE 8.2 on a separate drive on my box. Everything was working great until my Windows partition died and I had to reload it from scratch. Of course, this overwrote my MBR, thus destroying my GRUB setup. Once I got Windows running again, I booted to SuSE using the install CDs and ran YAST2 to reinstall the bootloader stuff just as it was before. That worked great and now my SuSE is running just like before except I cannot connect to the network. I have a Realtek 8139 NIC card and my PC is connected to a Linksys 4-port Cable/DSL Router. The router is using DHCP on the WAN side and static IPs on the LAN side. On the LAN, it is configured to use 192.168.1.1. The PC (the Realtek card as eth0) is configured to use 192.168.1.10. The DNS is set to 192.168.1.1 and local. I have the gateway set to 192.168.1.1 also. As I mentioned, using this exact setup I used to be able to connect just fine, but cannot now. I cannot even ping the router (192.168.1.1). Does anybody have any suggestions on things I should look at? I'm sure it's not a hardware problem, as it worked before and works fine in Windows. The networking setup looks good in YAST2 too. Yippee38 __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
On Tuesday 07 October 2003 21:15 pm, Yippee Three-eight wrote:
I've got SuSE 8.2 on a separate drive on my box. Everything was working great until my Windows partition died and I had to reload it from scratch. Of course, this overwrote my MBR, thus destroying my GRUB setup. Once I got Windows running again, I booted to SuSE using the install CDs and ran YAST2 to reinstall the bootloader stuff just as it was before. That worked great and now my SuSE is running just like before except I cannot connect to the network.
I have a Realtek 8139 NIC card and my PC is connected to a Linksys 4-port Cable/DSL Router. The router is using DHCP on the WAN side and static IPs on the LAN side. On the LAN, it is configured to use 192.168.1.1. The PC (the Realtek card as eth0) is configured to use 192.168.1.10. The DNS is set to 192.168.1.1 and local. I have the gateway set to 192.168.1.1 also.
As I mentioned, using this exact setup I used to be able to connect just fine, but cannot now. I cannot even ping the router (192.168.1.1).
Does anybody have any suggestions on things I should look at?
Does Windoze see the network OK? What does ifconfig say? -- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg
Yippee Three-eight wrote: <snip>
I have a Realtek 8139 NIC card and my PC is connected to a Linksys 4-port Cable/DSL Router. The router is using DHCP on the WAN side and static IPs on the LAN side. On the LAN, it is configured to use 192.168.1.1. The PC (the Realtek card as eth0) is configured to use 192.168.1.10. The DNS is set to 192.168.1.1 and local. I have the gateway set to 192.168.1.1 also. <snip>
Yippee38
Did you use ifconfig to check if the interfaces look correct from the prompt? Are the ip addresses and subnet masks correct? Are you running SuSEfirewall2? Are you sure it's running as well? Check in yast runlevel manager and see if all 3 modules are running. Also, check the firewall settings to make sure they are still correct. Lastly, check for errors in /var/log/messages and /var/log/firewall. Perhaps they will give you a clue what's going wrong. John S.
--- js
Did you use ifconfig to check if the interfaces look correct from the prompt? Are the ip addresses and subnet masks correct? Are you running SuSEfirewall2? Are you sure it's running as well? Check in yast runlevel manager and see if all 3 modules are running. Also, check the firewall settings to make sure they are still correct. Lastly, check for errors in /var/log/messages and /var/log/firewall. Perhaps they will give you a clue what's going wrong.
John S.
Everything looks correct in ifconfig - ip addresses and subnet masks. I've only got two: eth0 and localhost. I am not running SuSEfirewall2. Just to be sure, I disabled protection on Wan and Local network connections, and I made sure it was not running. Using the runlevel editor, I turned off the firewall components (all three). However, it seems like even though I removed them from all three runlevels that they are set to initially (2, 3, & 5), the firewall-init and the other one (not firewall-setup) were still started the next time I booted. I manually turned them off, but still no connect. I also tried enabling all three, but that didn't help either. I tried setting the firewall to protect WAN and Local connects, but allowed all services listed, but that didn't help either. /var/log/messages had no errors. /var/log/firewall does not exist Any other suggestions? This is goofy. Yippee38 __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
Yippee Three-eight wrote:
Everything looks correct in ifconfig - ip addresses and subnet masks. I've only got two: eth0 and localhost. I am not running SuSEfirewall2. Just to be sure, I disabled protection on Wan and Local network connections, and I made sure it was not running. Using the runlevel editor, I turned off the firewall components (all three). However, it seems like even though I removed them from all three runlevels that they are set to initially (2, 3, & 5), the firewall-init and the other one (not firewall-setup) were still started the next time I booted. I manually turned them off, but still no connect. I also tried enabling all three, but that didn't help either. I tried setting the firewall to protect WAN and Local connects, but allowed all services listed, but that didn't help either.
/var/log/messages had no errors. /var/log/firewall does not exist
Any other suggestions? This is goofy.
Yippee38
At this point, it's time to start looking at cables. Try reseating the cables in the router, hub, and PC. Are there other computers on the network you can use to troubleshoot? If so, try pinging the router from another PC. Then, if you have a crossover cable, try connecting the crossover cable between the PC in question and a second PC, and see if they can ping each other. If there is no other PC you can connect the crossover cable between the router and your PC directly, thus bypassing the hub. Do this and try to ping the router. Of course if this works and there is no other PC you can just toss the hub because it's bad. I assume you already tried moving the cable to another jack on the hub right..? Ultimately, if other PC's can ping the router through the hub, including using the same jack that PC #1 is using, then you need to try a new ethernet card in the PC. Also, consider you will want to verify that each cable is good by successfully connecting two devices through it. Don't rely on ohm readings because this doesn't account for twisted pair impedance. John S.
participants (3)
-
Dylan -
js -
Yippee Three-eight