• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

Problems accessing server shared drives through a hardware vpn due to rights

I've got a customer whom has a hardware VPN (always on) connection to the home office which I had no part in setting up. There is only one pc in this remote office and to my knowledge it has always been in a WorkGroup setting, not attached to domain (user did mentioning have to enter password to connect to Exchange and possibly shares when accessing them). The pc has been working fine for years until recently they took it to a local vendor fix a virus and now it will not connect entirely to the network drives on the server in the home office. They get a access denied message. I have confirmed the pc can ping the home office server (which runs on a entirely different IP scheme) by its ip address but I cannot ping the servername itself which makes me think it is possibly a DNS issue? I've tried to us the NET USE command but cannot get it to stick as I may be typing something wrong. I did this thinking if I recreated share while entering credidentals to problem would if itself but now after removing of of the shares I cannot get it remapped. Here's a example:

NET USE O: \\10.0.0.1\Shared
or
NET USE O: \\10.0.0.1\Shared userspassword /USER:username    and\or NETBIOSname\username

But I get messages like "Cannot find Network" or "Error 67".

Does anyone have any ideas on how to recreate a new drive mapping and allow this remote users to access the drives without having to enter a username and password everytime (except for exchange which I understand)? The users should have everything setup on the server as it should be (rights, group assignments, etc) as nothing has even been touched on it and also they have another remote site with just 1 computer that is still connecting fine.

Thanks in advance.
0
Scotts1976
Asked:
Scotts1976
  • 6
  • 5
  • 5
2 Solutions
 
biscuit3Commented:
Can you bringup the server shares?  GoTo -> Run-> type in:  \\10.0.0.1   press enter..  you should be prompted for the server credentials.  Then if you see the shares, right click and select Map Network Drive.

Also, they might have put the netbios names in the Hosts file (c:\windows\system32\drivers\etc\)
0
 
Scotts1976Author Commented:
Thanks for quick reply biscuit3.

When typing \\10.0.0.1 into run line I get a message stating
"No network provider accepted the given network path"

I will see what I can find about Host file.
0
 
Rob WilliamsCommented:
Try:
net use O:  \\10.0.0.1\Shared  password  /USER:TheirDomain.abc\UserName  /persistent:yes
or:
net use O:  \\10.0.0.1\Shared  password  /USER:UserName@TheirDomain.abc  /persistent:yes
Note: ( USER is not a variable, and abc is their domain suffix which may be the internal suffix .local)

>>"No network provider accepted the given network path"
Are you sure the share exists?
I assume you can still ping the IP?

An alternate to adding the domain suffix above is to add the domain suffix to the network adapter.
http://www.lan-2-wan.com/Added%20Images/Blog/DNS.jpg
The NIC should also only have the remote site's DNS as the DNS server. The ISP should not be added even as an alternate.

0
Industry Leaders: 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!

 
biscuit3Commented:
Is the remote workstation on a different IP Scheme than the main site?

Example

Remote Site                                Main Site
192.168.1.0/24                           192.168.50.0/24
0
 
Scotts1976Author Commented:
Rob: Thanks for your response also

Thanks for confirmation on net use command I will check that out to confirm.

Also yes the Shares definitely exist as another site is accessing them at this time.
Yes I can still ping the server's IP that the share lives on.

They are using the local ISP DNS I believe I will read over that article and see if that helps but I did just recently check the other site that is connected the same exact way and I believe they are using there ISP's DNS.
***********

Biscuit:

Yes the remote site is on a different ip subnet  192.168.5.1-254 and the home office is on 10.0.0.1-254
0
 
Rob WilliamsCommented:
>>"I believe they are using there ISP's DNS"
That is fine if you are using IP's, but not if you want to connect by FQDN. Adding the suffix to the NIC basically automatically adds the domain name and suffix to a user's credentials when authenticating. Remember TheirDomain.abc\UserName is not the same as UserName. The later defaults to LocalPC\UserName if the domain is not specified or the suffix added to the DNS tab of the NIC configuration.
0
 
Scotts1976Author Commented:
Rob:

Will adding the DNS suffix to NIC cause them problems getting on internet or will it just route DNS through server at home office?

Scott
0
 
biscuit3Commented:
I personally would not touch the DNS settings on the NIC if you are only dealing with one workstation because then they will have issues accessing the internet when they are not connected via VPN.

0
 
biscuit3Commented:
the authentication fault is probably what Rob said, domain\username not localPC\username
0
 
Rob WilliamsCommented:
Changing the DNS server's IP to the server, rather than the ISP will cause local internet problems, if the VPN is down. But as mentioned if using the IP to map it is not necessary anyway. Adding the DNS suffix will not harm local internet access. If they also have a local domain, ad both suffixes under search in this order.
0
 
Scotts1976Author Commented:
Rob and Biscuit:

Just wanted to let you know I finally found issue with the VPN drive shares access problem to be that the NETBIOS had somehow become disabled/corrupt and wouldn't enable. I had to boot to safe mode and remove the LAN network adapter and reinstall to fix issue.

Thank you both for your suggestions and troubleshooting steps and I will see if I can split points.
0
 
Rob WilliamsCommented:
NetBIOS was the problem? Very odd as NetBIOS is not very effective with VPN's, which is why they rely on DNS.
0
 
biscuit3Commented:
i have seen the netbios as an issue before.  Depending on the infrastructure netbios might play a bigger role than DNS.
0
 
Rob WilliamsCommented:
If you had configured a host file, it would now work.
However, still means DNS is probably broken, but if it works.....   :-)
0
 
Scotts1976Author Commented:
Thanks to you both again for your assistance. Your steps, though not the exact fix, did help me finally come across the actual problem. Also I learned a few things about DNS suffix and host files which I didnt know. Thanks again.
0
 
Rob WilliamsCommented:
Thanks Scotts1976.
Cheers !
--Rob
0

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

  • 6
  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now