Thanks for the reply. I decided to go with EFW for VPN only because i've
noticed other enterprises use CISCO VPN solutions through a hardware
appliance. However, you do bring up a good point and I guess I could
implement it on the server. Care to share a good VPN in Win2k3 doc?
On Tue, May 20, 2008 at 4:52 PM, McJerry <[EMAIL PROTECTED]> wrote:
>
> Nothing special, just configure your routing rules as you would any other
> situation.
>
> While I do not use EFW presently in production, I am using IPCop to
> accomodate like setups to what you described. It works well and EFW worked
> well when we used it. Windows 2003 Server or Windows 2008 Server aren't
> really any different in the roles you are describing. Question though, how
> many remote users? Why not consider using built in VPN functionality of the
> 2003/2008 server to authenticate remote users thereby providing
> controlled/managed access to domain assets. You can change the default VPN
> listening port via regedit and you can port forward incoming VPN traffic to
> the appropriate server. On the client side, whether to use the established
> VPN connection as the default gateway is a function of checking a box in
> network settings for the VPN connection. If they are windows clients, this
> seems easier than having to support an additional OpenVPN client
> installation.
>
> Just Curious...Goodluck.
>
>
> toby-35 wrote:
> >
> > Hi all,
> >
> > I have a Windows 2003 environment (soon to be 2008) where I have one 2003
> > server and 5 workstations. The server is currently a domain controller,
> > file
> > server, and application server. My current router is the DHCP server and
> > will be replaced with the EFW. I plan on using EFW as a VPN appliance,
> > DHCP
> > server, IDS, and proxy to connect remote users to the domain controller.
> > What do i need to know before I implement this? Any caveats?
> >
> > Current LAN Network: 10.7.7.0/255.255.255.0
> > WAN Network: 79.x.x.x
> >
> > TIA,
> >
> > toby
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Efw-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/efw-user
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/EFW-2.1.2-install-in-Windows-server-2003-environment...-tp17343471p17351744.html
> Sent from the efw-user mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Efw-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/efw-user
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Efw-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/efw-user