Re: VPN Folder Sharing

From: jackjenkins (jackjenkins_at_discussions.microsoft.com)
Date: 11/16/04 

Date: Mon, 15 Nov 2004 20:32:01 -0800

Robin,

Thank you so much for the time you have spent responding.
It is working however the ip addresses I chose were at the upper end of the
pool. I put them just outside the pool and could not connect again after
configuring firewalls, routers, etc. Then I extended the range just to get
things working again and I can now share folders with \\192.168.x.xxx\share.
I guess changing to 192.168.0.xxx and 192.168.1.xxx on the routers worked.
However there are some funny entries on ipconfig, nbtstat -c. I'll play with
it for a few days and see what happens.

Thanks again,
Jack

Server Testvpn ipconfig (remote box)

PPP adapter RAS Server <Dial In> Interface:

        Connection-specific DNS Suffix . :
        IP Address . . . . . . . . . . . : 192.168.0.202
        Subnet Mask. . . . . . . . . . . : 255.255.255.255
        Default Gateway. . . . . . . . . :

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . :
        IP Address . . . . . . . . . . . : 192.168.0.201
        Subnet Mask. . . . . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . . . . : 192.168.0.1

Client ipconfig (home box)

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . :
        IP Address . . . . . . . . . . . : 192.168.1.201
        Subnet Mask. . . . . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . . . . : 192.168.1.1

PPP adapter Testvpn 2:

        Connection-specific DNS Suffix . :
        IP Address . . . . . . . . . . . : 192.168.0.203
        Subnet Mask. . . . . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . . . . : 192.168.0.203

Client (home) nbtstat -c

Local Area Connection:

Node IpAddress: [192.168.1.201] Scope Id: []

                NetBios Remote Cache Name Table

        Name Type Host Address Life [sec]
---------------------------------------------------------------
Workgroup <1C> Group 192.168.1.201 -1

Testvpn 2:

Node IpAddress: [192.168.0.203] Scope Id: []

                NetBios Remote Cache Name Table

        Name Type Host Address Life [sec]
---------------------------------------------------------------
Workgroup <1C> Group 192.168.1.201 -1
Testvpn <03> Unique 192.168.1.201 -1
Testvpn <00> Unique 192.168.1.201 -1
Testvpn <20> Unique 192.168.1.201 -1

Server nbtstat -c

Local Area Connection:

Node IpAddress: [192.168.0.201] Scope Id: []

                NetBios Remote Cache Name Table

        Name Type Host Address Life [sec]
---------------------------------------------------------------
Workgroup <1C> Group 192.168.0.201 -1
Localcom-1 <1B> UNIQUE 192.168.1.201 -1

RAS Server <Dial in> Interface:

Node IpAddress: [192.168.0.202] Scope Id: []

                NetBios Remote Cache Name Table

        Name Type Host Address Life [sec]
---------------------------------------------------------------
Workgroup <1C> Group 192.168.0.201 -1

"Robin Walker" wrote:

> jackjenkins <jackjenkins@discussions.microsoft.com> wrote:
> >
> > I still get the password screen when trying to share. When I try
> > \\servername\share, the password screen immediately comes back up no
> > matter which user, password I use.
> >
> > Here is ipconfig and nbtstat -c from both sides:
> >
> > Server ipconfig (remote box)
> >
> > PPP adapter RAS Server <Dial In> Interface:
> >
> > Connection-specific DNS Suffix . :
> > IP Address . . . . . . . . . . . : 192.168.0.104
> > Subnet Mask. . . . . . . . . . . : 255.255.255.255
> > Default Gateway. . . . . . . . . :
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > IP Address . . . . . . . . . . . : 192.168.0.103
> > Subnet Mask. . . . . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . . . . : 192.168.0.1
> >
> >
> > Client ipconfig (home box)
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > IP Address . . . . . . . . . . . : 192.168.1.101
> > Subnet Mask. . . . . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . . . . : 192.168.1.1
> >
> > PPP adapter Testvpn 2:
> >
> > Connection-specific DNS Suffix . :
> > IP Address . . . . . . . . . . . : 192.168.0.103
> > Subnet Mask. . . . . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . . . . : 192.168.0.103
>
> The VPN virtual adapter on the client has an identical IP address to the
> Server's address on its own LAN. This is not right.
>
> I think the issue might be a clash between static IPs overlapping
> DHCP-issued ones.
>
> If you allocate a static IP to your VPN Server, you must ensure that this
> static IP address is within the sub-net of the router, but outside the DHCP
> allocation pool of the router's DHCP server. For instance, if the router's
> DHCP pool range is 192.168.0.100 and higher, then you should allocate static
> IPs in the range 192.168.0.2 to 192.168.0.99.
>
> So, first ensure that all statically allocated IP addresses are outside the
> DHCP ranges of the routers.
>
> Now, open the properties of "Incoming Connections" in the VPN Server's
> Network Connections. Click tab Networking. Select "Internet Protocol
> (TCP/IP)" and click Properties. There you will see a dialog for assigning
> the TCP/IP addresses for the VPN link. These addresses by default will be
> obtained from the VPN Server's DHCP server; i.e. the router. If you had
> allocated an IP address to the VPN server from within the DHCP pool of the
> router, then the same IP address could be issued by the router's DHCP server
> to the VPN link end-points. Another way of preventing this happening is to
> allocate a range of static IP addresses (within the router's LAN subnet
> range, but outside the DHCP pool) to the VPN link. You need two IP
> addresses per VPN connection (one for each end of the link).
>
> Once you have made these changes, try all the ipconfig analysis again.
>
> --
> Robin Walker
> rdhw@cam.ac.uk
>
>
>

Relevant Pages

  • RE: VPN, RRAS & DHCP
    ... Open DHCP console. ... Check the status of the local server. ... <VPN connections subsequently fail again. ... <I say fail but in practice both the server and clients are assigned IP ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS and NetBIOS names not resolving over a PPTP VPN using RRAS
    ... by all VPN clients. ... What if the VPN server has more than one network ... I have a separate DHCP server on the remote ... To assign the DNS and WINS to a VPN client for name resolution, ...
    (microsoft.public.windows.server.networking)
  • Re: DNS and NetBIOS names not resolving over a PPTP VPN using RRAS
    ... whatever DNS and WINS wettings are on the VPN server will be inherited ... by all VPN clients. ... with the DHCP Relay Agent. ...
    (microsoft.public.windows.server.networking)
  • RE: VPN, RRAS & DHCP
    ... DHCP correctly bound to Internal NIC. ... ISA firewall client was not used by the VPN client computer ... Check the status of the local server. ... <only when RRAS is set to obtain IP address from DHCP server. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Folder Sharing
    ... If you allocate a static IP to your VPN Server, ... static IP address is within the sub-net of the router, but outside the DHCP ... DHCP pool range is 192.168.0.100 and higher, then you should allocate static ... obtained from the VPN Server's DHCP server; ...
    (microsoft.public.windowsxp.work_remotely)
Loading