Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Two ethernet and swtch. Ping Problem 1

Status
Not open for further replies.

palhello

Programmer
Dec 29, 2002
30
NP
Ok, here is the scenrio. I have got a headless linux box with fedora installed and Windows XP professional. Windows machine has two ethernets (one for internet via pppoe and the other for LAN).
I just want simple networking. But here is the problem. One ethernet is in 172. range with 255.255.255.0 subnet mask and is used for pppoe connection for internet.
The other nic for LAN is configured other ethernet as follows
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

For the linux, I have
IP Address: 192.168.0.100
Subnet: 255.255.255.0
Gateway:192.168.0.1
DNS: 192.168.0.1

Now I don't know what's the problem I can't ping linux from windows or vice-versa. I don't need internet in the linux box so I don't care much about internet sharing..what's the problem ?? Is it some kind of routing issue that I am missing ?

here is the routing information on windows machine

Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 124.41.229.26 124.41.229.26 1
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.1 2
124.41.224.1 255.255.255.255 124.41.229.26 124.41.229.26 1
124.41.229.26 255.255.255.255 127.0.0.1 127.0.0.1 50
124.255.255.255 255.255.255.255 124.41.229.26 124.41.229.26 50
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.16.61.0 255.255.255.0 172.16.61.3 172.16.61.3 20
172.16.61.3 255.255.255.255 127.0.0.1 127.0.0.1 20
172.16.255.255 255.255.255.255 172.16.61.3 172.16.61.3 20
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 20
224.0.0.0 240.0.0.0 172.16.61.3 172.16.61.3 20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 20
224.0.0.0 240.0.0.0 124.41.229.26 124.41.229.26 1
255.255.255.255 255.255.255.255 124.41.229.26 124.41.229.26 1
255.255.255.255 255.255.255.255 172.16.61.3 172.16.61.3 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 124.41.229.26

P.S. All firewalls on both machines are turned off. Even disabled one ethernet and checked the connection without the internet ethernet..doesn't ping...


 
What do you get on the windows box when you do ipconfig /all?


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 

Windows IP Configuration

Host Name . . . . . . . . . . . . : myhost
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82566DC-2 Gigabit Network C
onnection
Physical Address. . . . . . . . . : 4C-00-10-72-0A-2B
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.61.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 PCI Fast Ethernet Ad
apter
Physical Address. . . . . . . . . : 00-A1-BE-C4-21-D3
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

 
Are you directly connecting the linux box to the win box, or are you going through a switch? If direct, are you using a crossover cable?

Are there any other boxes on the 192 subnet? Can they ping either of the boxes in question??

The settings look good (on the win side anyway), at this point I'd start checking cables, connectors, etc.


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
I am using a switch...I double checked the cables.. Should the color coding of wires have anything to do with it . I don't have cross connection.
At each side I have
OrangeWhite,Orange,GreenWhite,Green,BlueWhite,Blue,BrownWhite,Brown
The switch led shows green so I don't know what's the problem.
There is just one box in the 192 subnet. I just have two machine one is XP and the other is linux right now.
 
If the color scheme on both ends is exactly the same, then the cable should be fine. Post ifconfig -a from the Linux box. What kind of switch is it? Is the interface on the XP box enabled? Is Windows Firewall turned off? Windows Firewall blocks ICMP echo-replies by default.

Burt
 
All Firewalls are turned off both on Windows and Linux. Even turned off the SELinux. Could it be a switch problem ? I can ping 192.168.0.1 which is the self computer...and the light is green..
 
ok I changed the windows setting a bit
Windows IP Configuration

Host Name . . . . . . . . . . . . : dualcat
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 PCI Fast Ethernet Ad
apter
Physical Address. . . . . . . . . : 00-E0-4E-A4-21-DE
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.1

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82566DC-2 Gigabit Network C
onnection
Physical Address. . . . . . . . . : 4C-00-10-72-0A-2B
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.61.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

PPP adapter wlink:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 124.41.229.201
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 124.41.229.201
DNS Servers . . . . . . . . . . . : 202.79.32.33
202.79.32.35
NetBIOS over Tcpip. . . . . . . . : Disabled


No gateway there for 192.168.0.1 .
And here is my ifconfig -a from linux


eth0 Link encap:Ethernet HWaddr 4C:00:10:72:0A:2B
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::4e00:10ff:fe72:a2b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:4 dropped:0 overruns:0 frame:0
TX packets:91 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3815 (3.7 KiB) TX bytes:7475 (7.2 KiB)
Interrupt:11 Base address:0xc000

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:1986 errors:0 dropped:0 overruns:0 frame:0
TX packets:1986 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2396138 (2.2 MiB) TX bytes:2396138 (2.2 MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


The problem now is that I can ping windows from linux. But when I turn on windows I cannot ping the Linux box, also no ssh, no httpd nothing. Somehow windows isn't seeing the linux box. Is it because I have two ethernets ? I still think this is somekind of routing problem with windows. Any help would be appreciated.

P.S. Linux is a headless box and I only have one monitor so I have to switch the CPU's to check any settings...it's painfulll :p






 
On the Linux box...

TX packets:91 errors
RX packets:37 errors:4 dropped

this could mean a duplex mismatch.
The 4 dropped I would have guessed meant a firewall, bad cable, or duplex mismatch as well...

Burt
 
One simple question, how do I resolve it ? i turned on the link mode of the NIC from Auto Detect to 100 Mbps Full Duplex mode..still no luck.
 
What kind of switch? Are both interfaces (NICs on the Windows box and Linux box) set to 100/full?

Burt
 
It is a 8 port switch. Both linux and windows are on 100Mb Full mode. I even turned off the auto negotiating part.
I am still not able to ping linux..what's wrong...

One thing that I have noticed in the linux box is that

$ssh user@127.0.0.1
seems to work fast almost instantly
however

$ssh user@192.168.0.100
seems to make me wait at least for sometime for the password prompt.

Is there something wrong with RJ45 wiring or something else ???






 
127.0.0.1 is the internal loopback---of course it will be instant! SSH needs to generate 1024 bit or 2048 bit (depending on if you configure ssh1 or ssh2) before the login pops up.
Your NIC on the Linux box could be messed up---also, make sure you have a gateway set in linux. Since Linux can ping Windows, it has a two way path, so routing is not an issue.
What IP are you pinging from both?

Burt
 
I only have 2 computer so I can't say which IP I am pinging from both.

I can ping 192.168.0.1(windows) from linux.
I cannot ping 192.168.0.100(linux) from windows.

Is my routing on windows all right ? Please analyze the route print that I have given earlier.
 
It must be right---ping utilizes a route to and from, so there is a route from Linux to Windows and from Windows to Linux. Let's see if Windows actually knows about Linux---there is probably a "route add" statement/batch you should run...perhaps a Windows person could help here...I'm a Cisco person myself...
Post a new "route print", since you have changed a few things.

Burt
 
Here is the new route print..not much different
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...4c 00 10 72 0a 2b ...... Intel(R) 82566DC-2 Gigabit Network Connection -
Packet Scheduler Miniport
0x20005 ...00 e0 4e a4 21 de ...... Realtek RTL8139 PCI Fast Ethernet Adapter -
Packet Scheduler Miniport
0x40004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 124.41.231.42 124.41.231.42 1
124.41.224.1 255.255.255.255 124.41.231.42 124.41.231.42 1
124.41.231.42 255.255.255.255 127.0.0.1 127.0.0.1 50
124.255.255.255 255.255.255.255 124.41.231.42 124.41.231.42 50
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.16.61.0 255.255.255.0 172.16.61.3 172.16.61.3 20
172.16.61.3 255.255.255.255 127.0.0.1 127.0.0.1 20
172.16.255.255 255.255.255.255 172.16.61.3 172.16.61.3 20
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 20
224.0.0.0 240.0.0.0 172.16.61.3 172.16.61.3 20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 20
224.0.0.0 240.0.0.0 124.41.231.42 124.41.231.42 1
255.255.255.255 255.255.255.255 124.41.231.42 124.41.231.42 1
255.255.255.255 255.255.255.255 172.16.61.3 172.16.61.3 1
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
Default Gateway: 124.41.231.42
===========================================================================
Persistent Routes:
None



And I already tried adding
route add 0.0.0.0 mask 0.0.0.0 192.168.0.1 metric 1
OR
route add 0.0.0.0 mask 0.0.0.0 192.168.0.1 metric 1 if 0x2

It doesn't work :(
 
Try
route add 192.168.0.100 mask 255.255.255.255 192.168.0.1

Burt
 
Doesn't seem to work :(. Let me rewire all the rj45 plug out one nic, and check if there is a one on one connection.
 
It seems to be rj45 crimping problem. I removed the switch from two computers made a cross-cable connection between the two computers and now it is working like a charm.

And now I think why the heck did I buy the switch for ? May be I will use it when I have more than two computers.
Or is there something interesting that I can do ??
 
<cough>


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top