XP VPN Client connects to remote LAN but NOTHING ELSE seems to work 2

[duBe68]

Hi, I'm a complete NOOBIE with all things networkable, so please forgive me.
As a result of constant vandalisim at my business, I've recently installed a couple of Axis IP Cameras, which are attached to my Billion ADSL Router.
I've created both a PPTP and a L2TP LAN-to-LAN VPN entries in the work router that I was hoping would allow me to connect to the cameras from home.
When I create NEW NETWORK connection on my laptop at home (using XP Network Connection Wizard), the resultant connection tells me that I can connect to the work router via the VPN's. This is confirmed by the work router indicating that the tunnel is active & connected.
Problem is, I cannot do anything with the connections, I even lose all access to IE browsing until I close the VPN connection.
Sorry for the convoluted question, but I really don't know what is wrong, so I don't know what to include.
I'd be most grateful for your assistance.

 

[cmeagan656]

Is the IP address on the laptop that you're trying to connect to your work LAN in the same scope? I.E. laptop IP is 192.168.0.8 and your the scope at work is 192.168.0.1/254.

You'll have problems seeing anything on the work LAN if your laptop IP is within the same scope.

Cheers.

 

[linney]

Any clues here?

"error 733"+vpn

http://www.google.com/search?q="error+733"+vpn&rls=com.microsoft:

thread1583-1437402: Got Network issues and nForce Chipset...

Have a look at the Winsock Fix mentioned here.
WinXP Connectivity Issues
faq779-4625

 

[duBe68]

Hi again folks, thanks so very much for your continued support, I greatly appreciate it.

cmeagan656:

Yes, my office router private IP range is 192.168.11.1/254 whereas my home router private IP range is 192.168.1.1/254.

I've even tried setting the office router to 192.168.22.1/254 but same result.

linney:

Thank you so very much for the link to the info on the WinSock Fix, it worked a treat for my system. I'm once again able to connect, although I'm still stuck with the original problem of not being able to do anything with the connection.

I haven't had a chance to look at the other threads yet, but I will do & report back if anything there solves the original problem.

Once again, thanks so very much for the ongoing help.

duBe

 

[duBe68]

Oh, I forgot to thank Ken (cckens) for his excellent instruction of how to save config text files from the command prompt.

I had no idea how to do that previously; works a treat.

I used it together with the instructions in the thread that linney gave me about the Winsock issue. That allowed me to save both the original & fixed Winsock catalog's to text file, so I could take a look at the changes made by comparing the two files.

Magic, thanks, I've learned so much of late.

duBe

 

[duBe68]

Hi once more,
I've had a chance to read through the other threads recommended by linney:

1. Error 773 thread
looks like my friend's laptop has an extra comms service called IPX/SPX that I don't have, so I guess that's why I get the error thrown up when I try to connect with his system?

2. nForce chipset
I'm pretty confident that I don't have a nForce chipset. My Device Manager lists "Intel Pro", so I guess that means I don't have nForce chipset, right?

I'll follow the steps recommended by Ken (cckens) on Monday when I'm back at work & post the results.

Again, please accept my sincere appreciation to all who are helping me solve this problem.

duBe