Questions

VPN (Browse to shares on server)

Tags:
+
0 Votes
Locked

VPN (Browse to shares on server)

bc42bike
I have a customer one workstation can connect through VPN and browse to network shares with no problems.

The other workstation can establish the VPN connection but can not browse the network or connect to shares. This workstation was able to do this but stopped working about a week ago.

The settings are the same for both workstations, firewalls not an issue.

I can ping the fqn and get a reply however I can not ping \\server and get a response.

The ip address of the server responds to pings. I am thinking there must be an issue with DNS.

Anybody got any ideas?
  • +
    0 Votes
    bc42bike

    file & Print sharing turned on

    +
    0 Votes
    JPElectron

    You haven't said what VPN client your using, but check that after the VPN connects, the virtual adapter should have a DNS server defined (usually the IP of your Active Directory domain controller or internal DNS server) You can prove this is the problem by adding the IP and name of the file server to the local hosts file, or by trying to map a drive using the IP instead of the server name, for example \\192.168.34.8\share

    Check that the client computer is in a different IP range than the VPN tunnel, and also different than the office network - if any are the same, the system doesn't know to pass traffic over the tunnel. For example...
    Office LAN 192.168.34.x
    VPN tunnel 192.168.35.x
    Home/client LAN 192.168.0.x
    ...each must be a different IP range for it to work.

    +
    0 Votes
    PurpleSkys Moderator

    don't suppose you noticed the date on the orginal post...it's four years old...I'm hoping they figured it out by now.

  • +
    0 Votes
    bc42bike

    file & Print sharing turned on

    +
    0 Votes
    JPElectron

    You haven't said what VPN client your using, but check that after the VPN connects, the virtual adapter should have a DNS server defined (usually the IP of your Active Directory domain controller or internal DNS server) You can prove this is the problem by adding the IP and name of the file server to the local hosts file, or by trying to map a drive using the IP instead of the server name, for example \\192.168.34.8\share

    Check that the client computer is in a different IP range than the VPN tunnel, and also different than the office network - if any are the same, the system doesn't know to pass traffic over the tunnel. For example...
    Office LAN 192.168.34.x
    VPN tunnel 192.168.35.x
    Home/client LAN 192.168.0.x
    ...each must be a different IP range for it to work.

    +
    0 Votes
    PurpleSkys Moderator

    don't suppose you noticed the date on the orginal post...it's four years old...I'm hoping they figured it out by now.