DNS or network problem

Bruce Hyatt bjhyatt at myway.com
Tue Feb 13 01:44:57 UTC 2007


 
Below is the output from the machine that works:ifconfig:eth0      Link encap:Ethernet  HWaddr 00:40:33:AA:94:56            inet addr:192.168.1.199  Bcast:192.168.1.255  Mask:255.255.255.0          inet6 addr: fe80::240:33ff:feaa:9456/64 Scope:Link          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1          RX packets:10263 errors:0 dropped:0 overruns:0 frame:0          TX packets:129 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:1000           RX bytes:3210318 (3.0 Mb)  TX bytes:10568 (10.3 Kb)          Interrupt:10 Base address:0xec00 lo        Link encap:Local Loopback            inet addr:127.0.0.1  Mask:255.0.0.0          inet6 addr: ::1/128 Scope:Host          UP LOOPBACK RUNNING  MTU:16436  Metric:1          RX packets:171 errors:0 dropped:0 overruns:0 frame:0          TX packets:171 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:0           RX bytes:11228 (10.9 Kb)  TX bytes:11228 (10.9 Kb)route:Kernel IP 
routing tableDestination     Gateway         Genmask         Flags Metric Ref    Use Iface192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth00.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0Here's the ouput from the machine that's not working:ifconfig:eth0      Link encap:Ethernet  HWaddr 00:03:47:DE:F2:B5            inet addr:192.168.1.198  Bcast:192.168.1.255  Mask:255.255.255.0          inet6 addr: fe80::203:47ff:fede:f2b5/64 Scope:Link          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1          RX packets:75 errors:0 dropped:0 overruns:0 frame:0          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:1000           RX bytes:24217 (23.6 Kb)  TX bytes:546 (546.0 b)eth1      Link encap:Ethernet  HWaddr 00:03:47:DE:EF:D3            inet addr:192.168.1.198  Bcast:192.168.1.255  
Mask:255.255.255.0          inet6 addr: fe80::203:47ff:fede:efd3/64 Scope:Link          UP BROADCAST MULTICAST  MTU:1500  Metric:1          RX packets:0 errors:0 dropped:0 overruns:0 frame:0          TX packets:9 errors:9 dropped:0 overruns:0 carrier:9          collisions:0 txqueuelen:1000           RX bytes:0 (0.0 b)  TX bytes:546 (546.0 b)lo        Link encap:Local Loopback            inet addr:127.0.0.1  Mask:255.0.0.0          inet6 addr: ::1/128 Scope:Host          UP LOOPBACK RUNNING  MTU:16436  Metric:1          RX packets:10 errors:0 dropped:0 overruns:0 frame:0          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:0           RX bytes:700 (700.0 b)  TX bytes:700 (700.0 b)route:Kernel IP routing tableDestination     Gateway         Genmask         Flags Metric Ref    Use Iface192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 
eth1169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth1 --- On Sun 02/11, Mikkel L. Ellertson  wrote:Bruce Hyatt wrote:> I have a new fedora installation and I can't get it to connect to> my network; not to other computers on my network nor to the internet.> > It is connected through a hub to a router using a static IP> address. I have another linux box connected without any problems> through the same hub, it's not a problem with the NIC and it's not a> problem with the cable.> > Yes, I have enabled ip forwarding in /etc/sysctl.conf> This should not be necessary unless you have more then one interfaceon the computer. For a system connected directly to a hug or router,you are not forwarding IP connections. That is for a system withmore then one connection, and you want to 
forward connections fromone interface to another.> I've compared all the network settings on the two computers andthey're the same except for one thing; the one that is working hasIPTables running. The one that won't work doesn't even have the tables.> > Could it be that not having IPTables configured and running is the problem?!!!> > Thanks in advance,> Bruce> I do not think it is IP tables. It wounds more like your static IPaddress for the new machine is wrong. Are you sure it is in the samenetwork as the other machines, and that is doesn't duplicate theaddress of another machine? Also, are you sure the Interface is upon the new install?If you would post the output of ifconfig and "route -n" from boththe machine that works, and the one that doesn't, we would have abetter idea of what is going on, and may be able to help you.Mikkel--   Do not meddle in the affairs of dragons,for thou art crunchy and taste good with Ketchup! --- On Sun 02/11, 
Guillermo Garron < guillermo.fedora at gmail.com > wrote:From: Guillermo Garron [mailto: guillermo.fedora at gmail.com]To: bjhyatt at myway.com, fedora-list at redhat.comDate: Sun, 11 Feb 2007 01:18:11 -0400Subject: Re: DNS or network problemOn 2/10/07, Bruce Hyatt  wrote:>> I have a new fedora installation and I can't get it to connect to my network; not to other computers on my network nor to the internet.>> It is connected through a hub to a router using a static IP address. I have another linux box connected without any problems through the same hub, it's not a problem with the NIC and it's not a problem with the cable.>> Yes, I have enabled ip forwarding in /etc/sysctl.conf>> I've compared all the network settings on the two computers and they're the same except for one thing; the one that is working has IPTables running. The one that won't work doesn't even have the tables.>> Could it be that not having IPTables configured and running is the 
problem?!!!I think -no way-but help you better could you please describe your network better?what is the IP/mask/def_gateway of the two PCs the working and not working?The IP of the router they are using to get the Internet?Also you can try this.use this command on the working and not working PCtcpdump -i any -s 1500 -w capture.cap--- first turn off the firewall on the working PC --- then analysethese files with Ethereal software, or if you want put the files wherewe I can download them and I will try to help you.If you do not have tcpdump use$yum install tcpdumpregards,-- Guillermo Garron"Linux IS user friendly... It's just selective about who its friends are."(Using FC6, CentOS4.4 and Ubuntu 6.06)http://feeds.feedburner.com/go2linuxhttp://www.go2linux.org

_______________________________________________
No banners. No pop-ups. No kidding.
Make My Way  your home on the Web - http://www.myway.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20070212/ff1edee3/attachment-0001.htm>


More information about the fedora-list mailing list