> Are you directly connecting the Windows XP box to the Linux host, or do
> you have a switch or a hub in between them? If direct, are you certain
> that you are cabled correctly? I would think you'd want a crossover
> cable instead of a regular cable.
this is a direct connection, using a crossover cable... i'm not that stupid ;)
>
> What are the results of the following commands on the Linux host:
>
> route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
200.217.50.131 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 200.217.50.131 0.0.0.0 UG 0 0 0 ppp0
> ifconfig eth0
eth0 Link encap:Ethernet HWaddr
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7279 errors:0 dropped:0 overruns:0 frame:0
TX packets:6733 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:493697 (482.1 KiB) TX bytes:612523 (598.1 KiB)
Interrupt:185 Base address:0x6000
> service iptables status
Table: nat
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- 0.0.0.0/0 0.0.0.0/0
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Table: filter
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0
Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 255
ACCEPT esp -- 0.0.0.0/0 0.0.0.0/0
ACCEPT ah -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state
RELATED,ESTABLISHED
REJECT all -- 0.0.0.0/0 0.0.0.0/0
reject-with icmp-host-prohibited
> ping -c 4 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
--- 192.168.1.2 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
> arp -a
? (192.168.1.2) at [ether] on eth0
>
> And what are the results of these commands on the XP box:
>
Partially translated windows xp output:
> route print
===========================================================================
Interface list
0x1 ........................... MS TCP Loopback interface
0x2 ...00 e0 18 a3 b8 87 ...... ASUSTeK/Broadcom 440x 10/100 Integrated Controll
er
===========================================================================
===========================================================================
Active routes:
Net address Mask Gateway Address Interface Cost
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2 20
192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2 20
224.0.0.0 240.0.0.0 192.168.1.2 192.168.1.2 20
255.255.255.255 255.255.255.255 192.168.1.2 192.168.1.2 1
Default gateway: 192.168.1.1
===========================================================================
Persistent routes:
None
> ipconfig
Local ethernet adaptor:
Connection Specific DNS suffix . :
IP Address . . . . . . . . . . . . : 192.168.1.2
Net mask . . . . . . . . : 255.255.255.0
Default gateway. . . . . . . . . . . : 192.168.1.1
> ping -n 4 192.168.1.1
Answer from 192.168.1.1: bytes=32 time<1ms TTL=64
Answer from 192.168.1.1: bytes=32 time<1ms TTL=64
Answer from 192.168.1.1: bytes=32 time<1ms TTL=64
Answer from 192.168.1.1: bytes=32 time<1ms TTL=64
> arp -a
Interface: 192.168.1.2 --- 0x2
IP Address Physical Address Type
192.168.1.1 00-61-e3-10-cf-54 dynamic
PS: hardware addresses removed...
--
Thiago dos Santos Guzella
Electrical Enginnering Student - UFMG (www.ufmg.br), Brazil
Linux User #354160
UIN: 13465286. Jabber: tguzella @ jabber.org
"Faith: not wanting to know what is true."
Friedrich Nietzsche
