Click to See Complete Forum and Search --> : my problem and solution?


optech
03-26-2001, 07:28 AM
here's my problem:
-two computers, one for firewall with mandrake 7.2, one with winME for main computer.
-computers connected with crossover cable
-dsl and eth0 on linux connected with striaght through cable
-eth0 on linux works with the DSL fine.
-eth1 is set to a class C private IP
-wineth is set to class C private IP (one less than eth1)
-windows is set to use gateway, IP - eth1

so far, i have green lights on both (that weren't there when i didn't have crossover cable in place)...
both computers can ping themselves (with 127.0.0.1 and their own network IPS) but they can't ping, traceroute, or anything to each other...
i have not set up any firewall rules yet either.

i had a dream last night, and it was about a possible solution...

there are some anti-hacker tools installed on the windows machine, and echo is off on the linux box..
is it possible that these two computers are configured to not recieve pings?
so far, that seems to be the only solution to my problem... how can i verify this?

Lorithar
03-26-2001, 07:06 PM
*grins*

If you have your win box running a firewall, then its likely not answering and if the linux box has it's echo turned off it too will be silent.

Sanity check as follows.

shut down the dsl.
shut down firewall on linux (ipchains -F)
shut off firewall/portblockers on win box
retry pings
Doublecheck netmasking. This is frequently the single biggest mistake made by hard coding ips.
Make sure that the ROUTING exists on both boxes
netstat -rn from the commandline on BOTH linux and windows.

1) default route 0.0.0.0 with netmask 0.0.0.0 points to what device.
2) route [class C ip Segment]dot 0 points to which device
3) on the linux box try adding an explicit route to [windows box ipaddress] pointing to eth1

With DSL down the default route will likely still point to the ethernet for the DSL.

If problems persist, post the following in detail.

a) netstat -rn from box boxen
b) ifconfig -a from linux
c) all ipconfig info from windows box
(ipconfig in NT or winipcfg in win95/98)
d) a rough idea of what "anti-hacking" software is in windows
e) a rough idea of the firewall you are using.

Do you have forwarding enabled in the linux box? (check /proc/sys/net/ipv4/ip_forward ... if it contains 1, yes you are set to forward, if it contains 0, no you aren't set to forward)

Good luck ...

optech
03-26-2001, 07:18 PM
i got it... my crossover cable was wrong (i forgot to switch the white wires too)
and there's a hardware conflict as well...
eth1 won't work when eth0 is enabled... trying to fix that now.

aph3x
03-27-2001, 12:33 AM
Originally posted by Lorithar:
if the linux box has it's echo turned off it too will be silent.

umm, i dont think the echo port (7) is used for icmp echo replies, i think it is used for network troubleshooting... my echo daemon is turned off and i receive icmp echo-replies from my slack box. just thought id piont that out :)

optech
03-28-2001, 10:06 AM
well, i'm trying to ping, so echo would have to be there