Howto make Samba shares available to microsoft clients via VPN

I have been looking for some time for a simple howto that describes
how to make a SAMBA share visible to Windows clients via a VPN.

I want the setup on the client side to be identical to the setup
required for setting up VPN to a Windows 2003 server, ie. follow the
MS instructions to the letter, and gain access to the files on the
SAMBA share. This keeps user support to a minimum.

I have had some success with VPN linux to linux and windows to
windows, but there are so many options, and the simple fact that
communications are encrypted and thus very difficult to debug.

Can anyone point me to an existing HowTo, or current docs that I can
use to help me get this working? I will be glad to summarize and post
the necessary steps back to the newsgroup.

------------------------

On the linux side: Debian 3.1 w/ 2.6.17.5 kernel. This is a simple
host box at a colo. Only one interface.

On the client side: Windows XP.

Also, I would want to setup multiple VPN's on the Debian box for
isolated access to strategically separate SAMBA file shares.

-----------------------

Any help is greatly appreciated.

.

Relevant Pages

  • Re: OS X 10.4.11 - Win2003Server: Zugriff per smb
    ... wenn ich nur den Client will. ... This variable controls whether Samba clients will try to use ... client use spnego = yes ... Windows 2003 requires SMB signing. ...
    (de.comp.sys.mac.misc)
  • RE: VPN and Remote Desktop Problems
    ... The internal VPN client must be configured as a SecureNAT client. ... > resolved by Windows XP SP2. ... For a complete list of Microsoft Product ...
    (microsoft.public.windows.server.sbs)
  • Re: RRAS IPSec on W2003 Server behind NAT
    ... Clients are Windows XP SP2 or later and have found out that with SP2, ... Vista/7 clients to be able to connect to a Windows 2003 VPN server [not ... IPSec are appreciated ... either an issue in your VPN config on the server, and/or on the client. ...
    (microsoft.public.windows.server.networking)
  • RE: VPN and Remote Desktop Problems
    ... The internal VPN client must be configured as a SecureNAT client. ... there is a known issue for Windows XP or SP1 and it is ... you could contact Microsoft Product Support Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Best VPN server to use on Fedora
    ... Best VPN server to use on Fedora ... > server and windows xp clients you would have to install OpenVPN on the ... > already has a client built in, I would like a Linux server that would work ...
    (Fedora)