The Cable NAT Device is the one that should be doing the VPN. It will be
more dependable than trying to pass the "Tunnel" to the Server. Some of
those Cable NAT Devices aren't capable of passing the Tunnel like that
anyway,...of course some can't act as a VPN Server either.....
Doing a Static NAT on port 1723 is not all there is to it. There is also
Protocol-47 (that's protocol-47 not port-47) that has to be dealt with as
well. The feature is often called "VPN Pass-through".
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Doug" <(E-Mail Removed)> wrote in message
news:1D0F601E-0D6E-4E1E-90C5-(E-Mail Removed)...
> I am trying to do this for my aunt's small business. I don't even work
there.
> They have a cable router. Connected to it through a switch is their server
> running Windows Server 2003. There are about 8 PC's also connected to the
> switch. The public IP is ported TCP/CP 1723 by the router to the server's
> internal IP. I have enabled the server role for the VPN. I setup a VPN
> connection on a remote client. I can connect to the server, and I can use
> Remote Desktop to control the server, but I can't see the shared folders
on
> the server. When I "ipconfig" I get an internal address to their network
on
> the remote machine, on the VPN connection.
>
> Any ideas why I can't see the folders? I am using a local user account
that
> the folders are normally accessible to.