Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cannot reach internal map drives when VPN to my external domain

Status
Not open for further replies.

drummelhart

IS-IT--Management
Feb 25, 2009
173
US
For the longest time, our clients have used WEBDAV to reach their resource folders to retrieve, or upload data to our network.

As of late, we have setup VPN Access to our network, where we also have to VPN to access those folders.

I now have a client who states he cannot open his internal map drives when he VPN's to our network.

In addition, within our VPN documentation, we have the Advanced TCP/IP settings stated to uncheck the box use default gateway of remote network.


What are the reasons why this person cannot access his internal map drives? All I can think of his the group policy within his internal network. Sadly his IT personnel will not email me back.
 
I check all those possible solutions none of which really gave me a course or plan to look into.

We do not use a Proxy Servers like ISA, so most of those ideas are lost.


What I have to do is figure out with what little he has given me, and come up with a solution, hopefully on our end, and if on his, then an idea that he can present to his IT department and have them OK the resolution.

I can VPN to that same external network, and have access to all my internal map drives. This is the part that slays me!!!
 
the speicifc thing i was looking for, is what is the exact error the user gets. we cant help as easily without knowing the exact error messafe (network path not found or what have you) :)

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
that is what I am working on :).

I just emailed the client. Now I have to patiently wait :(
 
I bet you do.....


What is worse, is this guy is like the only one who has this problem right now......eeekk
 
thats actually what makes group policy that much less likely to be the culprit :)

Are the drives mapped by server name? If so, are they mapped using the FQDN or the NetBIOS name of the server?

My thinking right now without knowing the error is that most likely, its not properly resolving server names. Of course, if using IPs, we have a different issue and my thinking will change.

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
well the only part of the mapped drives I believe is a possibility is the fact that three of them are shared with other persons. Now do not get me wrong, I am not a map drive phenom.
 
The problem here most likely isnt at the server level in my thinking right now, so the fact that other people can connect is only a side note which tells us we should be looking for a client side problem..whether that be connectivity issues or configuration issues is all that need be determined :)

- Brandon Wilson
MCSE:Security00/03; MCSA:Security03
MCSA:Messaging00; MCP; A+
IT Pangaea (
 
The client will not discuss this issue any longer.

It wreaks of BS so we can close this thread, and if I have this issue arise once more I will open a new thread again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top