1) Check your subnets and IP addresses. Do ifconfig on Linux and ipconfig /all on Windows. 2) Check routes on both with netstat -r 3) Check that the windows box is receiving the ping by doing a netstat -e to see the interface statistics. One problem I have had was a bad IRQ on the old NE2000 card I had in windows. It could send a packet but never got the interrupt to say it had received one. Another problem I had was a broken wire between the board and the BNC connector (it was a cheap net lan card, how many people remember these?). Hope this gives you some ideas. Rick Meyerhoff said: > > > Johnny Fulcrum wrote: >> On Fri, 22 Aug 2003 13:05:43 -0500, Rick Meyerhoff <rick at eworld3.net> >> wrote: >> >>> I still have not been able to get my network (just a crossover cable) >>> to work right. At this >>> point I can ping from w2k to Linux but not from Linux to w2k. Here is >>> what happens when I try: >>> >>> [rick at myLinux rick]$ ping myW2k >>> PING myW2k (192.168.1.2) 56(84) bytes of data. >>> >> >> >> Humm... can you ping the IP address of your windows box instead of >> it's > > same problem > >> name? PING is saying that the IP address of myw2k is 192.168.1.2 - is >> that true? >> Do you have a Name Server that is resolving names on you LAN? Just >> wondering how ping is knowing the IP address of the windows box... > > I just use hosts files on both machines and they look right. > >> >> I'm kinda new to this too, these are just some thoughts I had :) > > > -- > Eric (Rick) Meyerhoff > rick at eworld3.net > 952-929-1659 > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org tclug-list at mn-linux.org > https://mailman.real-time.com/mailman/listinfo/tclug-list _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list