James, Do you have another machine with a packet-sniffer in it?? I think what you're going to find is that your machine that can't talk to the 66.x.x.x network machine never ARP's for it, it just forwards packets destined for that machine to its default router because it's outide of it's network range, as defined by its IP address and it's network mask. You should see an ARP "whohas" 66.13.172.18 on the hub as the very first thing that machine does to try to find the other machine. Since you're plugged into a hub, the 66.x.x.x machine should see this ARP broadcast and reply, thus bypassing the router. But if that handshake isn't occurring, then the internal 192.168.x.x machine is having to forward all packets for other hosts to the router's internal address, and then the router is having a hard time figuring out that the 66.x.x.x address is actually on its internal interfce. I missed it in the reply chain, but I'm assuming this is a NAT setup to get to that machine? Anyway, Ethereal or another packet sniffer will quickly tell the story.... On Thu, Oct 16, 2003 at 08:23:45PM -0700, James Newton, webhost wrote: > source= http://www.piclist.com/piclist/2003/10/16/192550a.txt? > > > Could you draw a simple picture with your networks > > and those router interfaces ? > > 192.168.0.1 to 192.168.0.15 are all plugged into a hub that is connected to > the router. The WAN side of the router goes to a DSL modem and out to the > internet as 66.13.172.18 > > Can't get any simpler. > > I didn't enter those in the routing table... the router came up that way... > Also the old router, which did work, had the same entries. > > --- > James Newton: PICList.com webmaster, former Admin #3 > mailto:jamesnewton@piclist.com 1-619-652-0593 phone > http://www.piclist.com/member/JMN-EFP-786 > PIC/PICList FAQ: http://www.piclist.com > > -- > http://www.piclist.com hint: The PICList is archived three different > ways. See http://www.piclist.com/#archives for details. -- Nate Duehr -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body