How do I map a network drive on VPN when the remote IP address conflicts with local IP address.

I am trying to connect to map a drive on the server on a client's network through a VPN from my home office.  When I am in their office on my laptop connected directly to their network, I was able to map the drive.  However, when I am at home and connected through the VPN, it says "Windows cannot access \\192.168.0.2\data"  The ip address on the client's network is 192.168.0.2.  My home network uses an address scheme of 192.168.1.x.
MGothelfAsked:
Who is Participating?
 
MGothelfConnect With a Mentor Author Commented:
Never mind. I found the problem.  I recently upgraded my anti-virus software and the firewall settings were set to the defaults.  I needed to identify the remote network as a trusted network.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
What VPN are you using?  Windows?  Cisco?  Netgear?  OpenVPN? something else?

Can you ping the IP of the remote system?  Are you sure you're connected to the VPN?  Can you post your IPCONFIG /ALL results
0
 
MGothelfAuthor Commented:
I am using Windows VPN.  I Can ping the remote address - it is 192.168.0.2, for location NPS

IPCONFIG /ALL below:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\MGothelf>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Mark_PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

PPP adapter NPS:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NPS
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.88(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : 0.0.0.0
   DNS Servers . . . . . . . . . . . : 192.168.0.3
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connec
tion
   Physical Address. . . . . . . . . : 00-25-64-C8-61-5A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::ecec:8825:80bb:f71b%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.9(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, January 28, 2015 8:53:03 AM
   Lease Expires . . . . . . . . . . : Thursday, January 29, 2015 8:53:03 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 234890596
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-44-03-0D-00-25-64-C8-61-5A

   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{A7622AF1-F383-4F1C-81DC-33A495243837}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\MGothelf>ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time=25ms TTL=128
Reply from 192.168.0.2: bytes=32 time=23ms TTL=128
Reply from 192.168.0.2: bytes=32 time=24ms TTL=128
Reply from 192.168.0.2: bytes=32 time=23ms TTL=128

Ping statistics for 192.168.0.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 25ms, Average = 23ms

C:\Users\MGothelf>
0
 
MGothelfAuthor Commented:
I found the problem myself.  I recently upgraded my anti-virus software and the firewall settings were set to the defaults.  I needed to identify the remote network as a trusted network.
0
All Courses

From novice to tech pro — start learning today.