I'm trying to setup a simple network between two machines. One is running windows XP and the other is red hat 7.2. Both have ethernets, both ethernets are identified. Connection is through a cross-over cat5 (no hub).

I setup IP's manually:

Linux: 192.168.0.1
Windows: 192.168.0.2

The network icon in windows xp shows an active network.

When trying to ping the linux machine from windows, it doesn't work:


C:\Documents and Settings\Ahmad>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


The network connection activity shows some sent packets, but 0 (zero) recieved.

Configurations on windows:


C:\Documents and Settings\Ahmad>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ahmadh.com
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.1

PPP adapter D-Link DSL-100D ADSL Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 62.150.86.92
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 62.150.86.92


When using the 'route' command on linux it shows this entry (along with others):


Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.0.0 U 0 0 0 eth0


This is what i get from ifconfig on linux:


inter addr: 192.168.0.1
Bcast: 192.168.255.255
Mask: 255.255.0.0
UP BROADCAST RUNNING MULTICAST
RX packets: 0
TX packets: 19

Have you check to see that your firewall is not blocking the packets?

Peter

try adding the windows IP to your linux /etc/hosts file. restart the network and see if you can ping then.

On a side not, change your subnetmask to 255.255.255.0 192 is c not b :()

Try removing the default gateway...

Since your not a router, that could give ya problems :D

I thought u were setting up your linux box as the router, check out http://master-beta.linuxrouter.org:8080/

Originally posted by davidb
I thought u were setting up your linux box as the router, check out http://master-beta.linuxrouter.org:8080/


His XP box has a modem in it....

Therefore he needs to remove the default gateway from his XP config for the eth...

Settings should be as follows:

Windows:

IP: 192.168.0.2
Subnet Mask: 255.255.255.0
No default gateway
Make sure that TCP/IP is bound to the ethernet card

Linux:

IP: 192.168.0.1
Subnet Mask: 255.255.255.0
No default gateway

Like David said, the subnet mask for a class C IP should be 255.255.255.0. You also need to make sure that both systems have unique computer names.

Once you've changed the settings you'll need to reboot both computers. After that you should be able to ping with no problems.

Thank you all folks, done all that still not working :(

Originally posted by ckpeter
Have you check to see that your firewall is not blocking the packets?

Peter

I did


iptables --list


policy for all chains is accept, is that suffecient? or should i check somewhere else.

Originally posted by jahsh
try adding the windows IP to your linux /etc/hosts file. restart the network and see if you can ping then.

It was already there:


192.168.0.1 linux.ahmadh.com linux
192.168.0.2 windows.ahmadh.com windows

I removed the default gateway from XP, changed the subnet mask in both linux and windows.

still, no connection between the two machines.

BTW, yes, there is a PPP DSL modem on the windows xp, but i don't intend to use it as a gateway, as i don't need a route from the linux box to the Internet. I just want to develope on windows and test on linux.

Just noticed something.

pinging:

windows -> linux = time out
linux -> windows = unreachable

linux -> linux (using localhost) = fast responces
linux -> linux (using eth ip) = fast responces

windows -> windows (using eth ip) = time out
windows -> windows (using localhost) = time out

You got rid of all the gateway stuff right????

Did you check the Windows side of firewall? There is a Internet connection firewall that comes with XP. Make sure you didn't accidentally enabled it. (I knew I did....)

Peter

Originally posted by Ahmad
Just noticed something.

pinging:

windows -> linux = time out
linux -> windows = unreachable

linux -> linux (using localhost) = fast responces
linux -> linux (using eth ip) = fast responces

windows -> windows (using eth ip) = time out
windows -> windows (using localhost) = time out

You're saying you can't ping 127.0.0.1 on the Windows machine?

This might seem very simple, or even stupid.

But did you make sure this was REALLY a crossover cable?

For this one end of the cable should be Starting at wire 1 going to 8, with the "hook" of the connector down:
1 Orange/white 2 Orange 3 Green/white 4 Blue 5 Blue/White 6 Green 7 Brown/White 8 Brown

then the other end should be:
1 Green/White 2 Green 3 Orange/White 4 Blue 5 Blue/White 6 Orange 7 Brown/White 8 Brown

You might just want to check on that.

(there are some other ways to wire it, but this is among the most common)

{edit: this is required for the Tx/Rx on the NIC when not using a hub/switch}

Originally posted by The Prohacker
You got rid of all the gateway stuff right????

Yep.

Originally posted by ckpeter
Did you check the Windows side of firewall? There is a Internet connection firewall that comes with XP. Make sure you didn't accidentally enabled it. (I knew I did....)

Peter

Yes, the firewall checkbox is clear.

Originally posted by AQHost


You're saying you can't ping 127.0.0.1 on the Windows machine?

Hmm, strange isn't it?

I've just discovered that norton antivirus comes with a firewall!

I disabled it and can ping my machine now, still however ..

windows -> linux = time out
linux -> windows = unreachable

windows -> windows = ok
linux -> linux = ok

Originally posted by amd_duron
This might seem very simple, or even stupid.

But did you make sure this was REALLY a crossover cable?

For this one end of the cable should be Starting at wire 1 going to 8, with the "hook" of the connector down:


then the other end should be:


You might just want to check on that.

(there are some other ways to wire it, but this is among the most common)

{edit: this is required for the Tx/Rx on the NIC when not using a hub/switch}

Yep, that was the first thing I checked. It is supposed to be:

1 <-> 3
2 <-> 6

right?

update ..

Linux is now showing a number for recieved (RX) packets.
Windows, however, still shows zero for recieved packets.

They both show sent packets.

Yes, the crossover is correct.

Moving on, on the windows side the tcp/ip is not corrupt is it?

Other than that I don't know what else to offer on forums, except that netowrking with XP is a big pain in the butt and MS should be shot for such pathetic networking support.

{edit: That's not a threat is it? if so remove it}

Originally posted by amd_duron
Yes, the crossover is correct.

Moving on, on the windows side the tcp/ip is not corrupt is it?

Other than that I don't know what else to offer on forums,


Everything is fine on Windows side, thank you for your remark. You are true, btw, it was partly a cable problem. When I keep the linux end of the cable firmly in the port, I start haveing success in some ping requests.


except that netowrking with XP is a big pain in the butt and MS should be shot for such pathetic networking support.

{edit: That's not a threat is it? if so remove it}

well that is a whole different story :)

Thank you all folks for helping me sort out all my misconfigurations. :)

The last problem now is a cable problem. Everything will, hopefully, be working after I replace it.