Internet Connection Sharing

  • Thread starter Thread starter Simon Patten
  • Start date Start date
S

Simon Patten

Scenario:

The office system is using ICS (in Windows 2000 Server) to share the
ADSL internet connection to the local network.

We want to start using VPN but many of the people are also using ICS
at home and it seems that there's immediately a problem since both
ends have a 192.168.0.1 node.

The router cannot be configured to serve DHCP/NAT/etc.

Question:

Is it possible to persuade W2KS to use a different base address (i.e.
192.168.1.1) to resolve this problem or can anyone suggest an
alternative solution please?

Cheers,
Simon.
 
You can assign a different IP to the server using RRAS instead of ICS. Do
not use RRAS wizard for VPN server role.
 
Jetro said:
You can assign a different IP to the server using RRAS instead of ICS. Do
not use RRAS wizard for VPN server role.
Click to expand...

I've found where I can allocate an address block in the VPN section of
the RRAS wizard but when I complete it it kills the LAN!. How else
could I set up VPN other than by using that wizard? Would you mind
talking me through it or pointing me at some instructions please?

Also I assume that by not using ICS I'll have to set up DHCP but will
I also need NAT and maybe even DNS too?

Cheers,
Simon.
 
ICS is a limited version of RRAS. Unless the network is really small, DNS
and DHCP servers are a must.

http://support.microsoft.com/?id=299801
HOW TO: Configure a Windows 2000 Server as a Network Address Translation
Server
(Don't be confused with IP 192.168.0.1 you find in this article, it could be
any private IP)

http://support.microsoft.com/?id=243374
Enabling VPN in RRAS Causes Connection Issues to Remote Networks

http://labmice.techtarget.com/networking/ras.htm
Routing and Remote Access Services (RRAS)
 
Jetro said:
ICS is a limited version of RRAS. Unless the network is really small, DNS
and DHCP servers are a must.
Click to expand...

Many thanks for the pointers, Jetro, a couple of hours of fiddling and
it seems to be working! :-)

NAT provided the DHCP server automatically and I was able to set the
base address for the network to 192.169.10.n and then enable VPN so
all is now well. I couldn't have done it without those instructions
though, it's far from intuitive when you've never done it before.

Cheers,
Simon.
 
Glad it helped.
P.S. Nothing is intuitive enough in Windows beginning from the right-click
:o)
 
Back
Top