Lost Internet Connection - Dual Boot Fedora Core 5 & Windows
Hello again,
Well I'm back, I have lost my connection to the web once more.
I have on my dual boot machine I have Win XP and Fedora Core 5, I was up and running on XP, then rebooted and booted up Fedora, only to find that i couldn't get on line? I have been running online in Fedora for about 6 days without a hitch. My Network say's I'm activated,But I can't get on line, My firefox is running, yet it can't find the servers? I tried to resart with the /etc/init.d/network restart command and all commans I know, Maybe someone else that had this problem can help? Thanks. fvs
Well I'm back, I have lost my connection to the web once more.
I have on my dual boot machine I have Win XP and Fedora Core 5, I was up and running on XP, then rebooted and booted up Fedora, only to find that i couldn't get on line? I have been running online in Fedora for about 6 days without a hitch. My Network say's I'm activated,But I can't get on line, My firefox is running, yet it can't find the servers? I tried to resart with the /etc/init.d/network restart command and all commans I know, Maybe someone else that had this problem can help? Thanks. fvs
0
Comments
-drasnor
[root@localhost frank]# /etc/init.d/network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[root@localhost frank]# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.051 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.049 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.045 ms
64 bytes from 192.168.0.3: icmp_seq=4 ttl=64 time=0.043 ms
64 bytes from 192.168.0.3: icmp_seq=5 ttl=64 time=0.043 ms
64 bytes from 192.168.0.3: icmp_seq=6 ttl=64 time=0.046 ms
64 bytes from 192.168.0.3: icmp_seq=7 ttl=64 time=0.045 ms
64 bytes from 192.168.0.3: icmp_seq=8 ttl=64 time=0.051 ms
64 bytes from 192.168.0.3: icmp_seq=9 ttl=64 time=0.045 ms
64 bytes from 192.168.0.3: icmp_seq=10 ttl=64 time=0.044 ms
64 bytes from 192.168.0.3: icmp_seq=11 ttl=64 time=0.048 ms
64 bytes from 192.168.0.3: icmp_seq=12 ttl=64 time=0.044 ms
64 bytes from 192.168.0.3: icmp_seq=13 ttl=64 time=0.045 ms
64 bytes from 192.168.0.3: icmp_seq=14 ttl=64 time=0.048 ms
64 bytes from 192.168.0.3: icmp_seq=15 ttl=64 time=0.044 ms
64 bytes from 192.168.0.3: icmp_seq=16 ttl=64 time=0.043 ms
64 bytes from 192.168.0.3: icmp_seq=17 ttl=64 time=0.047 ms
64 bytes from 192.168.0.3: icmp_seq=18 ttl=64 time=0.049 ms
--- 192.168.0.3 ping statistics ---
18 packets transmitted, 18 received, 0% packet loss, time 16998ms
rtt min/avg/max/mdev = 0.043/0.046/0.051/0.004 ms
[root@localhost frank]#
route add default gw 0.0.0.0
(replace 0.0.0.0 with the IP address of your router/nat machine).
As Drasnor said, you also need valid nameserver entries in your resolv.conf file.
search Cable.rcn.com
nameserver 207.172.3.8
nameserver 207.172.3.9
root@localhost ~]# vi /etc/resolv.conf
[root@localhost ~]# /sbin/route add default gw 192.168.0.1
SIOCADDRT: File exists
[root@localhost ~]# /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
default sorannos 0.0.0.0 UG 0 0 0 eth0
[root@localhost ~]#
last night before shuting down I said to myself maybe take a chance and put the network-conf back to dhcp
and see what happens, Well no dice it didn't work.
After going through this for about 5 days this morning i got up and went to buy a new ethernet card, On returning I decided to boot up one more time and see what would happen? Guess what about 15 minutes ago it opened and now I'm back up, This thing is bazzar. I didn't need an new ethenet card, It's so puzzling/
I now am affaid to reboot to XP thinking I'm going to loose my connections once more. WOW! are all linux so finky as Fedora 5?
Final question, now that I'm up and running what is the first thing I could do to keep my operating system stable? Which upgrades do you recomend?
As far as updates go, just go through you package manager and hit update all if it has such a feature. Do this once or twice a week.
-drasnor
2.6.15-1.2045
Thanks, If you have some tips, I would apprciate it, How best to keep it stable.
fvs