NoNeedToKnow wrote in
(E-Mail Removed):
> On 21 Mar 2006 10:35, "Martin Underwood" <(E-Mail Removed)> wrote:
>
>> There's a limit to what tests can be performed at a distance.
>
> Especially as he's on AOL with different MTU setting, and when I
> helped a neighbour, the PPP "chatter" provided him with a single
> DNS, rather than primary and secondary which most ISPs do. Whole
> load of things which could cause problems, compared with 99 % of
> ISPs with similar settings, and using "standard" BT service.
I never noticed that AOL only gives one DNS server entry, but then I was
looking more for the fact that when the router had connected, it had been
allocated a sensible AOL-specific IP address.
I know all about the MTU setting which needs to be changed from the default
of 1458 to 1400. I'm still not sure how essential that is: when I was
setting up one router on AOL for another customer, I initially forgot about
changing the MTU, and it connected fine. Whether it would have remained
connected once I started transferring large amounts of data is another
matter - I didn't try it because I corrected the MTU as soon as I realised.
However for another AOL/Netgear router customer it refused to connect (I
think it failed to even attempt CHAP authentication) when MTU was 1458. So
it looks as if the same equipment (DG834) to the same ISP (AOL) can give
different results - maybe depending on line condition and precise equipment
at the exchange.
In the case of my present customer, it looks as if the router is esablishing
a connection to the internet, in that I can ping a remote site
(news.bbc.co.uk) by its IP address. If only I could see the router's config
page I could confirm that it's being given sensible IP and DNS addresses.
Inability for a PC to access the router's config page over Ethernet is weird
when it can ping the router's IP - sounds like a firewall port 80 problem.
If the customer had been using Outlook Express rather than AOL to read his
email, it would have been intereting to see if POP and SMTP traffic was also
failing to get through. Hence the need to test with my PC, whose Norton
firewall definitely allows 192.168.0.x:80 traffic through.
All will no doubt become clear(er) on Thursday when I go to see the
customer.
I suspect I'll be doing battle with McAfee's firewall - oh, goody ;-)