Re: Can't Map Drive over VPN to Win2K Server but can to desktops

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 12/02/04 

Date: Thu, 2 Dec 2004 09:37:08 -0500

Martini Murphy wrote:
> Hi, Seems there are various threads on mapping drives over VPN but
> none seem to answer this. I have set up a VPN to the network at my
> office and can connect from home ok but I can't connect any drives to
> shares on the Windows 2000 Domain controller. I can connect to
> shares on the XP Pro desktops with no problem.
>
> The Server is Win2k Small Business Server and is configured as the
> domain controller running DHCP, DNS, Exchange, SQL Server, etc. The
> network uses the 192.168.0.0 (255.255.255.0) range of addresses with
> the first 20 reserved for fixed addresses.

Fine, but remember that nobody on the other side of the VPN tunnel can be
using the same IP addressing scheme.

> iThe desktops within the
> LAN are XP Pro/Win2k Workstation and don't have any problems
> connecting
> to shares on the server during normal network operation. The VPN is
> using a D-Link DFL-700 Firewall/VPN which comes straight into the
> network switch. The PC at home is running XP Pro and is using the
> D-Link client software to connect. The PC is not in the domain and
> connects to the internet using BT Broadband (U.K. ADSL). I have also
> tried a 56k dial-up and get the same results.
>
> After connecting with the VPN I can ping the desktops and the server
> using both IP addresses and the host names (I set up the domain suffix
> on the client connection). If I connect to shares on the XP Pro
> desktops then I am prompted for a user id and password which connects
> if entered ok. The problem is connecting to shares on the Win2K
> Server. I just get the message 'network path not found'.
>
> In simple terms, from home I can do 'net view xxxx' for the
> desktops ok (although get the 'access denied' message as expected)
> but for the server I get the 'network path not found' message.
> (Strangely, I can do 'net view' to one of the Win2k Workstation
> desktops and it gives me the list of shares without asking for a
> user/pwd). I have tried using WINS on the server but that seems to
> make no difference.

Did you configure WINS properly? In your DHCP scope on the server, make sure
you also select hybrid node (0x8) and make sure the server also points at
itself for WINS. Then the VPN user should specify the WINS server private IP
in his/her ip config.

> NetBIOS is enabled on the clients.

Doesn't matter - it's broadcast, and won't go across the VPN tunnel

> I've even
> tried NetBEUI on the server.

No - and it won't help you either - not routable. Take it out.

 I am assuming the problem is in the
> configuration of the NT Server as connecting to the XP Pro & Win2K
> Workstation machines work. Reading various posts I think it has
> something to do with WINS or NetBIOS but the fact is I can connect to
> shares on the XP Pro machines without WINS. (All machines are fully
> service packed).

Relevant Pages

  • Re: [Full-disclosure] Remote Desktop Command Fixation Attacks
    ... This set of steps is redundant in many places, and it's also enormously expensive, since you're using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator), in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license. ... Your computers necessarily don't have full access to your network infrastructure when they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to be applied. ... Turning on, enabling, and implementing every possible security setting and device you think of is not defence in depth, and will probably only have two effects - your users won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful* security measures. ...
    (Full-Disclosure)
  • Re: VPN with SBS 2003 (not R2) and DSL.
    ... Reading property value for VPN returned OK ... Reading VPN Server Name returned OK ... identical network cards. ... it seems doubtful that SBS will work properly with two NICs ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... on the SBS 2003 server just not sure where to go for help on it. ... Next time I'm at my home PC, I'll VPN in and see what IP info I'm getting ... client PC on your LAN, you should be able to do so from a remote VPN client, ... get the network path was not found. ...
    (microsoft.public.windows.server.sbs)
  • Re: RRAS as VPN Server Configuration Questions...
    ... Ethernet adapter VPN: ... Name resulotion on VPN Connection issues on DC, ISA, DNS and WINS server as ... Issue in a VPN client ... ... How to Setup Windows, Network, VPN & Remote Access on ...
    (microsoft.public.win2000.ras_routing)
  • RE: VPN Error 800
    ... The VPN client IP is 10.0.1.40, this is a private IP address. ... server IP address is 81.137.105.244, this is a Internet IP address. ... not test VPN connection from your perimeter network. ... SBS on your switch to make it work. ...
    (microsoft.public.windows.server.sbs)
Loading