Re: windows 2003 server routing and remote access setup
- From: "Steve Ireland" <Sandymount@xxxxxxxxxxx>
- Date: Thu, 29 Jun 2006 10:58:45 +0100
In that case, you can also enable security account (possibly either by user
or by computer) level permissions for using the outbound connections only
for certain periods of the day, I think.
<smilefirdose@xxxxxxxxx> wrote in message
news:1151556941.237677.85380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Steve,
The reason to do this is that the management has instructed to disable
the internet connection after 1800 hours and enable again at 0800 hours
because of the huge bills of ADSL. Since the users are using it for
over night downloads. We need to stop it. If we implement NATon the
server we can use batch files to disable the second NIC which will be
connected to the internet.
==========================================================================
Steve Ireland wrote:
Routing and Remote access allows you to both
...NAT for clients who are gettting out to the Internet
...and permit VPN for external users that you want to access your LAN.
NAT hides the IPs of one network (your internal LAN) behind an IP from
another network (the Internet). Your server needs to have access to both
of
these networks, one on either network card.
Maybe what you should do is set up the server with one NIC connected to
your
internal LAN (say 192.168.1.0/255.255.255.0)
The other NIC might be connected then directly to your Aztech Router -
that
network being the DMZ (say 10.1.1.0/255.255.255.0)
NAT would then be configured so that all of your internal LAN IPs
(192.168.1.0) would pass through the server, NAT'd as the IP address of
your
server's DMZ NIC (say 10.1.1.1) whereupon it would travel through the
Aztech
box and on out to the Internet.
But why would you do this when you already have a working Aztech router.
Does it not perform NAT itself?
Don't think this is what you want to do. But if you do, there are lots of
web pages that explain it a lot better...
for example...
http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Server-2003-act-NAT-router.html
<smilefirdose@xxxxxxxxx> wrote in message
news:1151492088.859453.214420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
i have windows 2003 server and Aztech 600eu router. Now the router is
directly connected to the switch and i have assigned it a static ip and
the lan clients connect to internet by this default gateway. I want to
setup routing and remote acess for the server. the server has 2 nic.
one connected to the lan and the 2nd idle. i tried to setup NAT but my
lan clients wont access internet.
the configuration i tried is as follows.
NIC 1=182.37.64.1(w2k3 server working as DHCP server and DNS server.)
default gateway 182.37.64.200, dns server =blank. forwarder to
182.37.64.200
NIC 2= 182.37.64.200 connected it to Aztech 600eu router /ADSL modem
which has a static ip
182.37.64.201.
for this NIC default gateway given as 182.37.64.201, dns server address
of the isp.
195.229.241.222/213.42.20.20
Even the server didn't connect to the internet.
Can anyone please help me with this issue.
.
- References:
- windows 2003 server routing and remote access setup
- From: smilefirdose
- Re: windows 2003 server routing and remote access setup
- From: Steve Ireland
- Re: windows 2003 server routing and remote access setup
- From: smilefirdose
- windows 2003 server routing and remote access setup
- Prev by Date: urgent please help ..microsoft event id +4199
- Next by Date: Re: Scheduled task won't be terminated
- Previous by thread: Re: windows 2003 server routing and remote access setup
- Next by thread: Windows NT4 Systems account missing
- Index(es):
Relevant Pages
|
Loading
