Voyager 2100 - Solved - thanks :)
>> You do not say why you want the test - can't you access them yourself?
Nope not using a 2100.
Although the kitz site is a relatively new one.. the arrse site is a well known issue that goes back a few years. (and is known to PN).
"The arrse issue" is even known by Voyager and was something they werent even able to resolve after a firmware update
(im currently using 2.18.01.17h_a023g1.d15g which was a beta version).
Voyager gave up trying to find the root cause because all their testing only showed it occuring on the Plusnet platform. It also occurs on a couple of other ISP platforms - Supanet and another ISP I cant recall.
My obvious first thought that it was an MTU issue - but no amount of tweaking my MTU settings seems to resolve this and I still cant access these sites. I can though if I use another router.
I was more trying to get to the bottom of the kitz one to see if it was another instance of the "arrse issue" (theres a few other known sites that are included in the list too).
The reason Im trying to get to the bottom of it - is that mail to the other domain "conveniently" seems to have gone astray too.
Nope not using a 2100.
Although the kitz site is a relatively new one.. the arrse site is a well known issue that goes back a few years. (and is known to PN).
"The arrse issue" is even known by Voyager and was something they werent even able to resolve after a firmware update
(im currently using 2.18.01.17h_a023g1.d15g which was a beta version).
Voyager gave up trying to find the root cause because all their testing only showed it occuring on the Plusnet platform. It also occurs on a couple of other ISP platforms - Supanet and another ISP I cant recall.
My obvious first thought that it was an MTU issue - but no amount of tweaking my MTU settings seems to resolve this and I still cant access these sites. I can though if I use another router.
I was more trying to get to the bottom of the kitz one to see if it was another instance of the "arrse issue" (theres a few other known sites that are included in the list too).
The reason Im trying to get to the bottom of it - is that mail to the other domain "conveniently" seems to have gone astray too.
>> - never bothered to update the firmware
>>> Firmware Version 3.03c.
hmmm thanks for that info - may be on to something here!
FYI this is some of the relevent snippets of convo with Voyager that date back to 2006 when I was in contact with them about developing firmware which supported IGMP.
They also asked me to test some sites regarding the "arrse issue" - originally in Feb 06 I could access them, but soon after I couldnt. - The "soon after" was after I upgraded the firmware.
Like you my 2100 is now a couple of years old.. and did at first have the really old firmware version on.
From Voyager February 15, 2006
From Voyager 23-2-2006
------------
Edit
I was just about to update the firmware to try that
alan - where did you get v 3.03c from - do you know please?
Ive just been to the voyager site and the latest version on there is still the 2.18.01.17 variant
>>> Firmware Version 3.03c.
hmmm thanks for that info - may be on to something here!
FYI this is some of the relevent snippets of convo with Voyager that date back to 2006 when I was in contact with them about developing firmware which supported IGMP.
They also asked me to test some sites regarding the "arrse issue" - originally in Feb 06 I could access them, but soon after I couldnt. - The "soon after" was after I upgraded the firmware.
Like you my 2100 is now a couple of years old.. and did at first have the really old firmware version on.
From Voyager February 15, 2006
Quote In regards to PlusNet web page inaccessibility problems, we know that the problem lies with the 2100 / PlusNet combination as we have tested the a number of different PCs with a number of different Voyager routers and the only router that did not work on any PC was the Voyager 2100, all the PCs worked with all the other routers tested. Thus far you are the only PlusNet customer that we have talked to that is able to access the problem pages;
From Voyager 23-2-2006
Quote There is definitely some sort of problem with the 2100/PlusNst combo
when it comes to some web pages but we haven't been able to figure out
what's different with PlusNet server setup and how it only effects the
2100.
------------
Edit
I was just about to update the firmware to try that
alan - where did you get v 3.03c from - do you know please?
Ive just been to the voyager site and the latest version on there is still the 2.18.01.17 variant
Thanks for the info pierre - sorry it locked up your browser
Out of curiousity do you know which firmware version you are using?
Out of curiousity do you know which firmware version you are using?
Don't know if this is useful but I can access both sites perfectly well using a Voyager 2091 router (version 3.03c) and using Firefox. No problems exiting either. 