I should've mentioned at the start the the error I get, while trying to pull up an http page in the browser is "connection reset while page was loading". Here's the result of a tracert to yahoo: Tracing route to yahoo.com [69.147.114.224] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.123.254 2 589 ms 1000 ms 653 ms 10.8.0.1 3 655 ms 662 ms 705 ms 10.102.254.254 4 674 ms 657 ms 667 ms 10.202.0.2 5 677 ms 679 ms 633 ms 10.255.247.1 6 634 ms 676 ms 680 ms m70.sprottshaw.com [207.102.1.70] 7 674 ms 649 ms 677 ms nwmrbc01gr01.bb.telus.com [154.11.4.98] 8 701 ms 657 ms 661 ms 154.11.10.74 9 660 ms 682 ms 665 ms Yahoo.plalca01gr00.bb.telus.com [154.11.3.74] 10 696 ms 642 ms 682 ms as-0.pat2.dnx.yahoo.com [216.115.101.129] 11 709 ms 686 ms 755 ms as-1.pat2.che.yahoo.com [216.115.96.54] 12 790 ms 770 ms 779 ms as-0.pat1.dce.yahoo.com [216.115.101.144] 13 771 ms 672 ms 780 ms ae2-p150.msr2.re1.yahoo.com [216.115.108.61] 14 750 ms 761 ms 782 ms te-9-2.bas-a1.re3.yahoo.com [68.142.238.67] 15 737 ms 681 ms 761 ms b1.www.vip.re3.yahoo.com [69.147.114.224] Trace complete.

0

589 ms 1000 ms 653 ms 10.8.0.1 I am going to assume 10.8.0.1 is your Satellite modem. Can you replace the cable between the router and the modem? That is way too long for a modem reply. Pc direct to the modem has less time?

0

I've already tried replacing the cable a while ago. Initial response w/o router is comparable.

0

See if you can telnet a web page port 80. If all other common services are OK then it is a port 80 issue. As to why I can't say. Guess you could try a live cd like knoppix 5.1 just to be sure it isn't the OS. Playing to the angels Les Paul (1915-2009)

0

Thanks for the suggestions. I've never used telnet, but I'm game to try. Funny you should mention a live CD, as I just ordered a couple of Linux distributions the other day. But as for the OS, I refer you to the top of the thread. I have the same behavior on 4 machines -- any one of which works fine connected directly to the modem -- so it seems unlikely to be the OS. The only thing in this picture that doesn't work is the router, which has been fine for years. While I think it would be awfully weird to have a hardware failure be this specific in its effect, I'm out of guesses. Thanks again

0

Same ms rating to the modem with or without the router points not to the router but to the modem as the problem.

0

wanderer: Forgive me if this is a naive question, but then why is everything fine (or at least functional) when any PC is directly connected to the modem? I've been doing some searching on related topics. There is an example of a trace (mtr, but whatever) from a satellite customer at http://www.tolaris.com/2008/10/09/i... You can see that the first hop from the router in the example shown is ~670ms. Seems like that first IP address is not the modem, but rather, it is the earth station to which the modem is yakking via satellite. I ain't sayin' I know this, I'm just sayin' it looks like this. :-) jefro: Tried telnet and was able to d/l a page off my employer's website while directly connected to the modem. With the router, no dice. Thanks dudes, this is more of a help than you might think.

0

Log on to the router and view web based config. Seems to be the router blocking port 80 Playing to the angels Les Paul (1915-2009)

0

Jefro, I agree, and that's where I went as soon as I narrowed this issue down to the router. But there are no filtering rules of any kind in effect, and early on in this process I did a hardware reset to factory defaults to make dead sure. Exact same symptoms. I've even created various filtering rules and then cleared them again hoping to free a stuck bit somewhere. (Desperate.) About the only thing left to do is try a different power supply on the router. I've seen power supply issues create some pretty exotic problems... although at the risk (nay, guarantee) of repeating myself, this is an oddly specific fault and highly unlikely to be attributable to power, so I don't hold out a lot of hope. Cheers.

1

looking in the router what is the wan ip address? 1 <1 ms <1 ms <1 ms 192.168.123.254 Your router 2 589 ms 1000 ms 653 ms 10.8.0.1 their equipment - modem 3 655 ms 662 ms 705 ms 10.102.254.254 their equipment 4 674 ms 657 ms 667 ms 10.202.0.2 their equipment 5 677 ms 679 ms 633 ms 10.255.247.1 their equipment 6 634 ms 676 ms 680 ms m70.sprottshaw.com [207.102.1.70] now you are on the internet backbone

0

According to a configuration record I saved earlier, the router indicates the WAN address as 96.63.24.93. I'll reconnect yet again and see if this changes. Why this hop doesn't show up explicitly in the trace is beyond me (as though I need to point that out). Cheers...

0

That certainly does not make sense. The modem port and the router wan port have to be in the same subnet. On the router wan port what was listed for gateway and dns?

0

WAN address: 96:63:24.93 Gateway: 96.63.24.1 DNS: 72.45.111.250 (and .251) Again, it seems clear from the characteristic satellite delay of ~ 600+ms that the 10.8.0.1 address is equipment at the ground station at their end, not the modem here, wouldn't you say? Between us, we've put in enough time on this to exceed the cost of a new router - if only for its value as a diagnostic aid. Unless a miracle happens soon, I'm ordering one today. Might as well upgrade to n-class. This router was important here initially because it has a built-in print server with a parallel port - but the printer it once connected to is long dead and the new printers are both network capable. Oh yeah... gotta try a different power supply just to rule that out. Fat chance that'll do anything but I gotta find out. <sigh>

0

Thanks for your help guys. I can't spend any more time on this and I sure as heck can't ask you to. I just placed an order for a new router. Hopefully I'll be back here next week to report that all is well. If not, it means the new router didn't fix the problem and I've strangled myself with a Cat5 cable. Cheers...

0

I had a thought while waiting for my new router to arrive. As crazy as it seems for the router to spontaneously begin filtering port 80 or otherwise screwing up http traffic, it could conceivably come down to one flipped bit in the firmware. It's in EEPROM after all, not etched in granite. If I had a copy of that firmware, it's possible that reloading it might restore the router to normal operation. Wish I could've tried that. Note to self: make back-up copies of the firmware for any field-upgradeable device -- before the manufacturer stops supporting it.

0

New router went in today. No further problems. No surprise. Thanks again for trying to help, but I think we were doomed by a hardware (or firmware) fault. Resetting to factory defaults should certainly have restored web access if the issue was something I'd done, or a random glitch. Ta...

0

Glad it worked out and thanks for posting back.

0