VPN update ..Oh yes! we did it..we did it..we did it!!

Re my previous posts I've just cracked my VPN prob all on my
lonesome....well I spotted a thread about VPN and applied it to my
circumstances :-)

I knew my Laptop was okay and definately the work server side was fine, it
was definately my PT3812 router or Virgin.net causing the problem. Anyhow I
was about to buy a cheap BT voyager off ebay for testing purposes and
minutes away an did a few searches regarding BT Voyager & VPN. I noticed a
post about some bloke who had a Voyager 205 with VPN trouble which truned
out to be an IP clash with work addesses. .
so I just renamed my 10.x.x.x addresses to 99.x.x.x. ones and Ta Dah!! it
worked.

I just need to reset my P2P port forward stuff and I'm up and running.


So now VPN woes are history, its full speed ahead on getting a better comms
package.

On Thu, 11 Jan 2007 20:20:40 GMT, ToxOgrady wrote:

>so I just renamed my 10.x.x.x addresses to 99.x.x.x. ones and Ta Dah!! it
>worked.
>
>I just need to reset my P2P port forward stuff and I'm up and running.

Except 99.x.x.x is a "real" IP address range and someone out there has it. You
had two other private ones to choose from: 172.16.x.x & 192.168.x.x

--

Regards

Dave Saville

NB Remove -nospam for good email address

"Dave Saville" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed). uk...
> On Thu, 11 Jan 2007 20:20:40 GMT, ToxOgrady wrote:
>
>>so I just renamed my 10.x.x.x addresses to 99.x.x.x. ones and Ta Dah!!
>>it
>>worked.
>>
>>I just need to reset my P2P port forward stuff and I'm up and running.
>
> Except 99.x.x.x is a "real" IP address range and someone out there has it.
> You
> had two other private ones to choose from: 172.16.x.x & 192.168.x.x

And if you had responded to earlier posts with full and complete answers to
the questions asked, we would have spotted the problem for you.

-- Graham J