The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: [OT] Strange Router problem - Netgear DG834G



Hi Keith,

I've only got the one router - BT Voager 2000 - and that's what I'm having
problems with.
(I, too, am on option 3).

I wonder if when you swapped routers, you got allocated a different WAN IP,
which got routed through a different cache/proxy - - and when you switched
back to the netgear, the same MAC got the same (old) IP - and thus
experienced the same problem?

This would explain why something that looks like a hardware problem to you
could be the same upstream issue that I see hear.

What do you think - plausible?

Rob



On 6/16/07, Keith Doxey <ukha@xxxxxxx> wrote:
>
>   Hi Rob,
>
> Yep, BT TotalBroadband Option3
>
> But..... If it is a problem with a server upstream how come it only
> affects
> my Netgear router.
>
> Dialup to BTInternet was fine, and my Broadband was fine as soon as I
> stuck
> the BT Voyager 200 back on there.
>
> I also now have a BT Homehub so plenty of routers to ensure I can get
> online
> :)
>
> Keith
>
>
> -----Original Message-----
> From: ukha_d@xxxxxxx <ukha_d%40yahoogroups.com> [mailto:
> ukha_d@xxxxxxx <ukha_d%40yahoogroups.com>] On Behalf Of
> Rob Iles
> Sent: 16 June 2007 03:59
> To: ukha_d@xxxxxxx <ukha_d%40yahoogroups.com>
> Subject: Re: [ukha_d] [OT] Strange Router problem - Netgear DG834G
>
> Keith,
>
> Are you by any chance using BT (Openworld) as your ISP?
>
> If so, I share your problems! I've spent about 12 hours on the
telephone
> so
> far trying to explain to them that one of their transparent proxy
servers
> "has issues"!!!
>
> First time I've ever seen a "Length Required" message (stopp
giggling at
> the
> back!).
>
> Basically, it looks (to me) like their squid cache was broken. It was
> breaking session state/"chunking" - so any website that
requred state to
> be
> maintained (such as some forums, gmail etc), were effectively broken.
>
> Most annoying.
>
> temp fix: route your outbound requests through a proxy (google: public
> proxy
> servers), and add one or more into your browsers config.
>
> If you're not a BT customer, then this is just a spooky coincidence!
> (maybe?!)
>
> Cheers,
>
> Rob
>
> On 6/14/07, Keith Doxey <ukha@xxxxxxx
<ukha%40diyha.co.uk>> wrote:
> >
> > Hi All,
> >
> > Wonder if anyone has experience the same or similar problem to
the one
> > I have just had.
> >
> > We were happily accessing internet sites with no problems when
Sharon
> > got thrown out of the web forum she was on and was unable to log
in
> again.
> >
> > Tried on three different computers and any site that required a
login
> > failed. Some of the forums just threw you back to the login page
or
> > the home page asking guests to login.
> >
> > AutomatedHome Forums gave an error message "Length
Required" as did an
> > ASP base site that I wrote and run for a local voluntary group.
> >
> > The problem was definitely with connecting to the outside world
as I
> > could access a local copy of my website hosted on my intranet.
> >
> > Rebooted the router (Netgear DG834G) remotely a couple of times
but
> > that didn't help an I even powered it down to no avail.
> >
> > Fired up an Old School DIAL UP connection on the laptop and was
able
> > to access all the sites correctly but god was it
> > slooooooooooooooooooooow :(
> >
> > I think the problem was somehow related to session variables as I
> > could search on Google but couldn't log into it.
> >
> > Dug my old BT Voyager 200 out and plugged that in instead and all
is
> > working fine.
> >
> > Anyone got any theories as to what the problem might be ??????
> >
>
>
>


[Non-text portions of this message have been removed]




UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.