[pptp-server] WAN->WAN question

[George Vieira]

OK first things first.

Why run a VPN when the offices are dialling directly into the Corporate
office?
Seeing all the machines on all networks will be difficult because network
broadcasts don't route so they won't go over the dial up link..

There are a number of ways to try this (and I mean try):

1) Setup a WINS server on the dial up server machine
2) each dialin machine is linux and sets the "remote announce =
dialupserverip" in samba (smb.conf)
3) each dialin machine sets the "wins server = dialupserverip" in samba
(smb.conf)
4) each site should use a different workgroup name "Sydney, Melbourne,
Perth, etc"...

Now the problem I can see with this one is that each linux dialup client
should have samba installed and act as a master browser to collect all
workstation broadcasts. They will remotely send this info to the WINS server
too but the server (I don't think) will not send that data to the other
servers and this is the problem I'm seeing. Unless it's samba and possibly
set to remote announce to each sites dialup machine...?????

THOUGH, if ALL of the workstations use the corporate server as a WINS server
in their TCP/IP setup then they can map to the other sits as the WINS server
should resolve all their IPs on the other subnets...

But network neighbourhood will probably only show the local workgroup..
Bummer!!

Others on this list could possibly make a better setup..



thanks,
George Vieira
Systems Manager
Citadel Computer Systems P/L


-----Original Message-----
From: Jeremy Mann [mailto:jrmann1999 at yahoo.com]
Sent: Friday, 21 December 2001 4:07 AM
To: pptp-server at lists.schulte.org
Subject: [pptp-server] WAN->WAN question


I'm about to implement a solution to link up 4-5
remote offices to a corporate office.  I'm wondering
what sort of documentation someone could point me to
on how to do this via VPN.  My idea is as follows:

I will run a VPN server at our corporate office, have
all of the remote locations then "dial-in" to that
server.  Each office will be on it's own subnet on the
192.168.x.x mask and then sort of pseudo-linked via
VPN.

My goal is to make this as seamless to the end user as
possible(when the good ol win98 folk open network
neighborhood they can see every share from every other
computer on the network).

If I'm totally off base here just point me where I
need to look.

Jeremy Mann

=====
Jeremy Mann
"To learn cobol is an injustice, therefore it should be a crime to teach
it."

__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
_______________________________________________
pptp-server maillist  -  pptp-server at lists.schulte.org
http://lists.schulte.org/mailman/listinfo/pptp-server
--- To unsubscribe, go to the url just above this line. --