DOn't knopw if this will catch you before you leave, but here are a couple of thoughts.
At 04:57 PM 10/3/02 -0400, Quan Si Kwon wrote: [...] > >1. You seem to say that the Win2K client has 2 interfaces, one to the > >Bering LAN, the other to "LAN2". What does its routing table look like? > >Does it know the right route to the Bering router? > >In the Win2K box, I use 192.168.1.10/225,225,225,0 as IP and under Gateway >I had put in 192.168.1.254 on both cards. This is wrong, but it may just be a typo in your e-mail. The Win2K box needs network 192.168.1.0/24, which means the IP address (192.168.1.10) is fine but the netmask you show (225,225,225,0) is wrong ... should be 255.255.255.0 . And anyway, I asked about the routing table, not the inetrface address. Does "route print" show a route to 291.168.1.0/24 on eth1? > >2. You say the two devices are connected "|<-xLink RJ45->|". Are you using > >a known-good crossover cable to make this connection? (Or am I > >misinterpreting "xLink"? I read it to mean a direct connection between the > >two hosts, not one through a hub or switch.) > >That's correct! I use an uplink or crossover cable without using a hub and >I have tried with two crossover cables. > > >3. When you try to ping, do the activity lights on BOTH NICs flash? > >(Assuming the NICs have activity lights; not all do.) > >Yes indeed! The activity lights seems to work. They come on and then off >when I ping. So we need to figure out which end is having the problem. On the Linux side, run "ip -s link" before and after an unsuccessful ping to see which of the TX and RX packaet counts change. Do the equivalent on the WIn2K side (I don't know the relevant Windows command for this). Do the same with a failed ping from the Win2K side. > >4. Can the Win2K host ping the Bering router? (Probably not, but does it > >fail with a different error?) > >No! If I use the command: ping -n 2 192.168.1.254, I get the following >results: >================================== >Pinging 192.168.1.254 with 32 bytes of data: >Request timed out. >Request timed out. >Ping statistics for 192.168.1.254: > Packets: Sent = 2, Received = 0, Lost = 2 (100% loss), >Approximate round trip times in milli-seconds: > Minimum = 0ms, Maximum = 0ms, Average = 0ms >================================== > > >I don't see any problems with the Bering config info you sent. But you're > >reporting the firewall rulesets in incomplete form -- you want to use > >"ipchains -nvL" to get a full listing of the rules in effect. > >I don't have "ipchains" as I am using Bering because when I type in the >command "ipchains -nvL", it reports that Not Found! Is this normal? Sorry; I got you mixed up with another inquiry. I meant "iptables -nvL". -- -------------------------------------------"Never tell me the odds!"-------- Ray Olszewski -- Han Solo Palo Alto, California, USA [EMAIL PROTECTED] ------------------------------------------------------------------------------- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
