Problem opening shares through VPN

  • Thread starter Thread starter Rolf Barbakken
  • Start date Start date
R

Rolf Barbakken

I have a Windows Server 2003 with RRAS set up to receive VPN connections.
The connections opens fine. I can open shares from XP-computers and
up/download files. Its slow, but thats another issue.

On Vista, though, I cannot open shares. I can ping the server, but "net view
\\xxx.xxx.xxx.xxx" only returns error 53. WINS is installed on the server,
and the VPN-connection have WINS added on tcp/ip property page.

I have turned off the Vista firewall, in case this was the problem, but it
didn't help.

What can be the issue here?
 
I have this EXACT same problem with Vista. I cannot figure out what is
causing the problem either. The problem occurs with the firewall turned on
or off.

This also occurs when I try to map a network drive from Vista to a Windows
2003 Server share using an IP address so name resolution does not appear to
be the problem.

Mike
 
I have tried opening shares with just \\[ip-address]\sharename as well. No
luck. I just get an error saying the resource cannot be found and a nice
little button to "Diagnose". Diagnose doesn't find any problems, of course.

Mike Howells said:
I have this EXACT same problem with Vista. I cannot figure out what is
causing the problem either. The problem occurs with the firewall turned on
or off.

This also occurs when I try to map a network drive from Vista to a Windows
2003 Server share using an IP address so name resolution does not appear
to be the problem.

Mike
Click to expand...
 
I'm really looking forward to the solution to this problem because this is
actually preventing work from getting done.

Mike

Rolf Barbakken said:
I have tried opening shares with just \\[ip-address]\sharename as well. No
luck. I just get an error saying the resource cannot be found and a nice
little button to "Diagnose". Diagnose doesn't find any problems, of course.
Click to expand...
 
Hello,

Yep, I too have exactly the same problem.

I'm using Vista Enterprise and ISA Server 2006 to connect to my work
network. I have the ISA Client for Vista installed, but cannot connect to
any Network shares.

What I want to do is to be able to sync once connected so that I can work
online and update files that I change from home, like I use to do with
Windows XP! I'm the IT Director, and at present cannot connect when away
from my desk, so this is causing me considerable problems.

My observations to date:

I have noticed that when I first connect I can resolve host names, so from a
command prompt I type "ping hostname", for about 30-60 seconds I can continue
to try and ping resources with success. After 60 seconds name resolution
become unavailable and I have to type the IP address in to ping the host.
NetBIOS is disabled throughout our organisation, by design, via DHCP. I
have noticed that at the time when name resolution disappears, my home
connections starts "identifying" and then goes into "public" mode for a while
before returning to the "private" home mode. Once everything has settled
down the VPN connection seems to identify that it is connected to my managed
corporate network. One would think at this stage that Vista was smart enough
to know that it was connected to my work network and go online, allowing me
to access the resources that should be available. This is not the case.

Strangely, I cannot connect my home PC, running Vista Ultimate, to work via
VPN at all, it hangs at the authenticating username and password stage.
However, I can connect that same PC to another VPN host running ISA Server
2000. I find this very confusing, as some TechNet articles I have read
suggest this should be the other way round.

This is just one of the problems my department has discovered with Windows
Vista.
We are also trying to identify the supposed benefits of the new Windows
Deployment Services. This seems to be more work than RIS ever was, as you
have to visit the client, then go back to the WDS MMC and approved and name
the PC, then return to the client to press F12, by which time it’s probably
timed out. At least with RIS I could name the PC whilst at the physical
machine and then leave it to do an unattended installation.
Also, don't get me started on the deployment of a customised installation of
Office 2007 via Group Policy, because you can't! TechNet says so...

However, I'm "Confident" that everything will become "Clear" once I get
"Connected".
 
Mike said:
I have this EXACT same problem with Vista. I cannot figure out what is
causing the problem either. The problem occurs with the firewall turned
on or off.

This also occurs when I try to map a network drive from Vista to a
Windows 2003 Server share using an IP address so name resolution does
not appear to be the problem.
Click to expand...


same here. very annoying, spent 2 days trying to access shares through
vpn from home to office. this is a huge showstopper for our vista
deployment :(

there is KB930163 [http://support.microsoft.com/kb/930163] that adresses
a part of the problem with vpn - unfortunately i'm still not able to map
shares from our office windows 2003 network.

- thomas
 
It could be the routing issue. Can you ping the remote server by IP?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Thomas H. said:
I have this EXACT same problem with Vista. I cannot figure out what is
causing the problem either. The problem occurs with the firewall turned
on or off.

This also occurs when I try to map a network drive from Vista to a
Windows 2003 Server share using an IP address so name resolution does
not appear to be the problem.
Click to expand...


same here. very annoying, spent 2 days trying to access shares through
vpn from home to office. this is a huge showstopper for our vista
deployment :(

there is KB930163 [http://support.microsoft.com/kb/930163] that adresses
a part of the problem with vpn - unfortunately i'm still not able to map
shares from our office windows 2003 network.

- thomas
 
Robert said:
It could be the routing issue. Can you ping the remote server by IP?
Click to expand...

of course. and tracert shows the right routes, and so does route PRINT.

everything else works: remote desktop, pinging, tracing, webs, ftp etc.

- thomas
 
Try this: net use \\serverip? If it asks the username and password, type the server administrator and password. If not, post back with the system error.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Thomas H. said:
It could be the routing issue. Can you ping the remote server by IP?
Click to expand...

of course. and tracert shows the right routes, and so does route PRINT.

everything else works: remote desktop, pinging, tracing, webs, ftp etc.

- thomas
 
Robert said:
Try this: net use \\serverip <file://\\serverip>? If it asks the
username and password, type the server administrator and password. If
not, post back with the system error.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

message

of course. and tracert shows the right routes, and so does route PRINT.

everything else works: remote desktop, pinging, tracing, webs, ftp etc.

- thomas
Click to expand...

as mentioned in the other posts by me and several others, shares over
vpn do not work properly in vista, no matter whether FQDN or IP. using
FQDN produces "the network path was not found." (error 53), and so does
using IP.

really, this is not a "i'm too stupid to use shares"-problem. thanks for
trying to help, tho.

- thomas
 
Same problem here. Everything works fine, except shares.

I have lowered the VPN-Logon-security (password instead of certificates,
etc.), now shares are accessable.
 
Thomas said:
Same problem here. Everything works fine, except shares.

I have lowered the VPN-Logon-security (password instead of certificates,
etc.), now shares are accessable.
Click to expand...

hmm... i'm using "security options" -> "typical" -> "require secure
password". i can't see any other security related option in vpn. what
else did you change to make shares work?

thanks,
thomas
 
I haven´t tried "typical". I am using MS-CHAP now. With EAP-TLS the shares
don´t work, anything else does.

Maybe there is more than one problem with shares ...

greetings
thomas
 
Thomas said:
I haven´t tried "typical". I am using MS-CHAP now. With EAP-TLS the
shares don´t work, anything else does.

Maybe there is more than one problem with shares ...
Click to expand...

defenitely seems like there are more problems. when selecting "typical",
it uses "MS CHAP V2" in our w2k3 vpn environement. i can force it to
use "CHAP" and no data encryption, but that doesn't make any difference
when trying to use remote shares - i'm always getting "system error 59 -
an unexpected network error occured".

gruss,
thomas
 
May have a solution for this..

I logged it with our MS TSC, and he came up with this new kb article:
http://support.microsoft.com/?id=929853

I found I had to disable IPv6 for the vpn, add the destinations dns suffix
as detailed in the kb article to the dns advanced tab of the vpn connection.

Then I could map a drive to \\machine.doman.local\c$ (for example). It only
seems to work using the FQDN. I have only tried this on a VPN back to the
office (a domain my pc is a member of).


Good luck!
 
Thanks Fred,

That was right on the money for me(Vista VPN to Win2k Server). I think the
DNS was the key. I though I was losing it.

Tony.
 
Back
Top