Link to home
Start Free TrialLog in
Avatar of jmoody
jmoody

asked on

VPN can't browse network

My internal network address is 192.168.0.x and when I connect to my network via the VPN on a network that uses this same address 192.168.0.x then I can't use any network resources. Is there a way that I can use my network resources while connected to a network that uses the same network addresses that I do? I am using the VPN that is built into Windows server 2003. Thanks.
Avatar of YohanShminge
YohanShminge

Greetings jmoody,

Under your VPN connection properties, Network tab, what protocols are installed?  If you don't see TCP/IP or Client for Microsoft Networks, install them.

Yohan
You can't use the same local address -- class C IP domain -- for the network you are on and the network you are "calling" by VPN.  They should be different, for correct functionality, because the VPN becomes locked in a loop-back failure if they resolve to the same.  It is a failing of the TCP/IP design.

Maybe, you can give yourself a static IP and connect to the local network by including that in the router domain, or else, map drives across workgroups, and that will solve the local problem.  More to the point, to solve the VPN connection, if you are out of the class C domain 192.168.0.x, you should be OK.
Avatar of jmoody

ASKER

Thanks. I thought I would need to move out of that class c. Do you know one that is less used that would be pretty safe and does anyone know how to move from a 192.168.0.x to somethig else? I treid it on a test network and I could not get the internal DNS working again, so then my Active Directory would not work. I am using Windows server 2003. It runs DNS, Exchange, and it is the DC.
you can use 10.x.x.x
ASKER CERTIFIED SOLUTION
Avatar of sciwriter
sciwriter

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I just wanted to add that this did indeed help me as well. I was trying to VPN in to an SBS 2000 server with a subnet of 192.168.1 XX and my home box was on that same sub as well. Once I changed my home IP to 192.163.0. XX it worked great. Thanks sciwriter for the awesome tip!!!