Unable to browse network shares using UNC \\IP address\C$ while connected to Always on VPN
While I am connected to my organization's internal network using the Always on VPN connection (while outside of the office) I am able to successfully browse network shares on the Hyper-V base server and virtual servers using the \\hostname\C$ convention but can't browse these same network shares using the \\internal IP address\C$ convention.
The internal IP address scheme used by my organization is uniqute and isn't widely used amoung other networks, 10.88.188.x (or by the networks I am connected to while establishing the Always On VPN connection).
I am also able to successfully browse these same C$ network shares while within my organization's internal network and connected using Wi-Fi or an Ethernet cable.
What can I do to fix this issue so I will be able to connect to and browse my organization's server's C$ shares using their IP addresses while outside of the office and connected to my organization's internal network using the Always On VPN connection?
The internal IP address scheme used by my organization is uniqute and isn't widely used amoung other networks, 10.88.188.x (or by the networks I am connected to while establishing the Always On VPN connection).
I am also able to successfully browse these same C$ network shares while within my organization's internal network and connected using Wi-Fi or an Ethernet cable.
What can I do to fix this issue so I will be able to connect to and browse my organization's server's C$ shares using their IP addresses while outside of the office and connected to my organization's internal network using the Always On VPN connection?
Just curious - what's the logic behind wanting to connect to a computer via IP as opposed to DNS? (Not questioning or implying you are doing anything wrong. I am just curious).
If your remote computer is connected to the VPN wouldn't your VPN ip be on a different subnet than your internal (10.88.188.x) network?
If your remote computer is connected to the VPN wouldn't your VPN ip be on a different subnet than your internal (10.88.188.x) network?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am able to successfully ping (and get responses) when I ping the server names by either their hostnames or IP addresses (while connected to the Always On VPN).
However, I get the following errors when I run the nslookup commands. The "Address" is listed as the public DNS IP address of my ISP, Comcast. What can I do to fix this?
C:\Users\dsmith.BAYITNC>ns
Server: UnKnown
Address: 75.75.75.75
*** UnKnown can't find bitcaad01: Query refused
C:\Users\dsmith.BAYITNC>ns
Server: UnKnown
Address: 75.75.75.75
*** UnKnown can't find bitcaad02: Query refused
C:\Users\dsmith.BAYITNC>
However, I get the following errors when I run the nslookup commands. The "Address" is listed as the public DNS IP address of my ISP, Comcast. What can I do to fix this?
C:\Users\dsmith.BAYITNC>ns
Server: UnKnown
Address: 75.75.75.75
*** UnKnown can't find bitcaad01: Query refused
C:\Users\dsmith.BAYITNC>ns
Server: UnKnown
Address: 75.75.75.75
*** UnKnown can't find bitcaad02: Query refused
C:\Users\dsmith.BAYITNC>
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
How can this be fixed by changing the DNS IP addresses that are assigned via DHCP when the Always On VPN connection is established?
Also, the DHCP IP address range assigned by the Always On VPN connection is on the same subnet as the internal network and the servers I am having this issue connecting to using their IP addresses while connected to the Always On VPN.
Also, the DHCP IP address range assigned by the Always On VPN connection is on the same subnet as the internal network and the servers I am having this issue connecting to using their IP addresses while connected to the Always On VPN.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What results do you get if you run (from a CMD prompt) ping <internal IP address> and also ping <hostname>?