Sign in with
Sign up | Sign in
Your question

Issue connecting via UNC over VPN by hostname.

Tags:
  • VPN
  • Business Computing
  • Thor
Last response: in Business Computing
Share
December 24, 2013 7:41:01 AM

Environment: Server 2008r2 domain, accessing over OpenVPN from a Windows 7 x64 laptop, which is joined to the domain.

This is the issue:
UserA is on a Windows 7 pro x64 laptop which is joined to the domain. Their permissions are set properly on all of their network shares. When in the office, they can connect to server 'Thor' (windows server) via unc (\\Thor) without issue. They can also connect to \\Tick (a different windows server) and to \\Cyclops (linux server running Samba) without issue.

When outside the office, they connect in over VPN.
The user can still \\cyclops and \\tick
The user can NOT \\thor
The user can \\thor.company.local
The user can ping thor

UserB (me) can \\thor over VPN without issue.

I've created a new VPN client, but it does not make a difference.
His Virtual Adapter for VPN has the same settings as mine (in that everything is set to automatic)
I created a second dns entry called 'thortest' and he can \\thortest without issue.

The specific issue is that when he tries to UNC, it comes back with 'the network path cannot be found' but it shouldn't be a dns issue because the user can ping 'thor' properly.

Any ideas?

Thanks

More about : issue connecting unc vpn hostname

December 26, 2013 7:43:04 AM

Just a shot in the dark here did you try to flush the DNS on users A laptop?
m
0
l
December 26, 2013 7:49:41 AM

Yes.

I even went so far as to edit their hosts file.
m
0
l
Related resources
December 26, 2013 7:58:58 AM

Thor and Tick what version of windows server are they running, and which one handles your AD and DNS? When he tries to connect to and of the \\ over VNC is he prompted to enter a username or password?
m
0
l
December 26, 2013 8:49:09 AM

Thor is the domain controller, Tick was just a file server.

I was able to resolve the issue by manually adding 'company.local' as a suffix in the advanced settings for dns on the network adapter. No idea why it was only affecting one user on only one server though.
m
0
l
!