problem solved...I replaced the NIC...working fine now... what actually led me to replace this NIC was:
while monitoring the packets on my RH with tcpdump, I pinged from RH; I watched requests go to the windows box, and watched replies come back to RH, but ping never reported that any got received; while pinging from windows box, I watched requests come into RH, but no replies were ever sent back, and thus, the windows ping also reported 100% packet loss... I don't quite understand how tcpdump was recording the acceptance of packets while ping wasn't?! If anyone can explain this phenomena, please do! so, ignore what I described below (tcpdump session)...what was described below happened before I switched my IPs back to what they should have been...oops. Kevin Kevin Weslowski wrote: > Hi all, > > last night I lost power to my RH7.1 box and my windows box... > > RH7.1 acts as gateway/router/firewall... > windows box is part of my private network... > > when I brought them up again, I had somehow lost my network connection > between win box & RH box... > > the first weird thing that I found was that my RH internal NIC had the > same IP as my external IP! Weird! After I changed it back to > 192.168.1.1, I was still unable to ping my win box, 192.168.1.2, or vice > versa; > > I also tried a tcpdump trace on my internal device, eth0, during the > pinging; nothing to report when pinging from the win box, but the > following when pinging from RH: > > arp who-has <windows_box_name> tell <RH_box_name> > > any suggestions on how to diagnose further? does it sound like possible > NIC/cable problems? > > thanks in advance, > > Kevin > > _______________________________________________ > Seawolf-list mailing list > [EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/seawolf-list _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/seawolf-list
