[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1040
  • Last Modified:

Unable to access shares using VPN (L2TP over IPSec )

Hi Could someone tell me how to get a fix for the following issue

I am doing VPN into my network using L2TP over IPSec into the SBS server. I have a Cisco VPN server

It uses different account to connect to the cisco VPN does not use domain accounts
When i try open shares
\\<hostname> i get access denied , user does not have permissions
I researched and added Authenticated Users into the Builtin-->Windows Authenticated Access group (something like that ) ..then it gave me the user account was not found.

As per the netmon trace , its giving me KerberosV5 error and it is passing the VPN account credentials when it tries to access the shares. Thats why it is getting access denied. Is there a way to pass domain credentials instead of passing the VPN account credentials. It takes in this settings automatically. Please share some of your thoughts.

Thanks You.

PS: Able to access shares via FQDN and IP address also was able to map a drive using the net use command
net use z: \\<hostname> /user:domain\username password
Command executed successfully so definitely it is a problem with those vpn account credentials being passed on
0
Tech Savy
Asked:
Tech Savy
  • 3
  • 2
1 Solution
 
Rob WilliamsCommented:
If the FQDN works then it sounds like the domain suffix is not being added to the host name.  When using a Windows VPN you can do so under the advanced TCP/IP properties of the DNS tab of the NIC configuration for the VPN/PPP virtual adapter, by adding the domain suffix (e.g. mydomain.local) in the "use this domain suffix for this connection".  I don't know that you have this option with the Cisco VPN client, but the Cisco admin should be able to push that out with the deployment package, or VPN DHCP scope options.
0
 
Tech SavyAuthor Commented:
I tried putting the DNS suffix for the VPN connectroid but that din't work I will see the options on the VPN server though
0
 
Tech SavyAuthor Commented:
It was caching the cisco vpn credentials we removed the cached credentials from Credential manager from Control panel issue resolved.
0
 
Rob WilliamsCommented:
Thanks for posting your findings rauldeshmukh.
Cheers!
--Rob
0
 
Tech SavyAuthor Commented:
Self resolved.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now