On Mon, Dec 8, 2008 at 10:32 AM, Harry Putnam <[EMAIL PROTECTED]> wrote: > "Mark Knecht" <[EMAIL PROTECTED]> writes: > >> I agree with Neil. It sounds like a router issue. Possibly a DMZ >> setting in the router is the same as the IP of the machine that >> doesn't work correctly so the ping gets to the DMZ and the response is >> sent out to the Internet instead of back inside? > > I agree too. > > I once had a DMZ setting set up on the router long ago. The address > was 192.168.0.19. It was an old home machine running openbsd with a pf > firewall. > > Currently no machine on the lan has that address and the DMZ > capability is disabled at the router anyway. (I just checked again > for about the 10th time.) > >> I don't think you stated how the problem box got its address. Is it >> fixed IP or something provided by the router? > > They are assigned by hand (by me) so static IPs. > >> If the 5 internal machines have consecutive addresses, have you tried >> changing the IP address of the machine that doesn't work to something >> above #5? Maybe disconnect one of the other machines and give the >> problem box that IP address? > > No I haven't but I'll try it now... just ifconfigging up a new > address. > > ifconfig eth0 down > ifconfig eth0 192.168.0.27 <=was 192.168.0.4 > route add default gw 192.168.0.20 > > ping ftp.ucsb.edu > PING ftp.ucsb.edu (128.111.24.43) 56(84) bytes of data. > 64 bytes from ftp.ucsb.edu (128.111.24.43): icmp_seq=1 ttl=44 time=129 ms > 64 bytes from ftp.ucsb.edu (128.111.24.43): icmp_seq=2 ttl=44 time=117 ms > [...] > > Oh boy, we in the chips now. > > Yippeee > > I new there would be some simple common sense test I would have > overlooked. Thanks. > > So that proves something is blocking that particular address > 182.168.0.4 and that seems almost certainly to be something on the > router. > > It must be a setting I cannot find and it must be for icmp only since > I've been able to traceroute or any other kind of connect, right > along. > > I could just change that machines address but it would mean changing > all other machines hosts files and such.... not too big a deal I > guess. > > Might be easier to reset the router to default factory condition and > and then set it up for my needs which wouldn't be much work either. > It has a little hole where you press a pin and reset it. > > Is there any chance the blockage is coming from something on that > machine and not the router?
I don't think there's much chance the problem is on the machine. I don't know much about these things though. As for the router I would consider looking for a router firmware update. I've had a couple of funny problems over the years with my LinkSys routers. Usually installing more up-to-date firmware has fixed them. Glad you are making headway. Cheers, Mark
