configure windows 2003 as router OR router on our LAN?

I have a 2mbps adsl connection at work, the ISP terminated a RJ45 pin & left
it with us to setup the internet for our LAN of 15 users.

the ISP has provided us with the following

IP: 213.132.39.126
SUBNET: 255.255.255.252
GATEWAY:213.132.39.118

PREFERED DNS: 213.132.33.19
2ndary DNS: 213.132.33.20

The Server has one NIC configured as DHCP server with

IP: 192.168.1.5
SUBNET: 255.255.255.0

SCOPE is 192.168.1.15 to 192.168.1.200


Can I setup my windows 2003 server to act as a roouter so that the clients
can access the internet

OR

can you help me on how to configure my router to share this internet
connection

Please help

You need to buy something like a Cisco 877 to act as your gateway to the
Internet. When you run the Cisco setup it will guide you through using the
IPs the ISP has given you for the external connection, and you use your
internal IP's on the inside. You will need to set up Address Translation,
and access-lists to firewall your internal network from the internet,
Anthony
www.airdesk.co.uk




"sphilip" <sphilip@discussions.microsoft.com> wrote in message
news:025DAD5C-AC5A-4BA7-95BB-3C07B1BA155D@microsoft.com...
>I have a 2mbps adsl connection at work, the ISP terminated a RJ45 pin &
>left
> it with us to setup the internet for our LAN of 15 users.
>
> the ISP has provided us with the following
>
> IP: 213.132.39.126
> SUBNET: 255.255.255.252
> GATEWAY:213.132.39.118
>
> PREFERED DNS: 213.132.33.19
> 2ndary DNS: 213.132.33.20
>
> The Server has one NIC configured as DHCP server with
>
> IP: 192.168.1.5
> SUBNET: 255.255.255.0
>
> SCOPE is 192.168.1.15 to 192.168.1.200
>
>
> Can I setup my windows 2003 server to act as a roouter so that the clients
> can access the internet
>
> OR
>
> can you help me on how to configure my router to share this internet
> connection
>
> Please help

No need to have your server do routing. Let the router do it :) All the IPs
provided by your ISP would go in the router. Since you received a server IP
of 192.168.1.5 while assigned dynamically, we can assume your router is
already configured on the 192.168.1.x internal network. You can probably
also safely assume that your router's internal IP is 198.1.168.1.1. You will
follow suit with your server. It is always best for servers to have a static
IP.

Set up your server like this.... (turn off the DHCP server on your server,
if it is running, the router is running DHCP - there should be only one DHCP
server on the network)

Ethernet adapter Wireless Network Connection: (of your server)

Connection-specific DNS Suffix . : domainofserver.com
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.4 (static - outside of
routers scoped DHCP range)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

Set up your cleints like this...

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : domainofserver.com
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.165.1.5.........200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192,168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Sunday, February 11, 2007
4:21:03 AM
Lease Expires . . . . . . . . . . : Monday, February 12, 2007
4:21:03 AM

Note: personally, I would set the scope narrower (i.e. 192.168.1.50 -
192.168.1.150). This leaves more room for configuration of static IPs for
things like printers and more servers, etc.

-Frank

"sphilip" <sphilip@discussions.microsoft.com> wrote in message
news:025DAD5C-AC5A-4BA7-95BB-3C07B1BA155D@microsoft.com...
>I have a 2mbps adsl connection at work, the ISP terminated a RJ45 pin &
>left
> it with us to setup the internet for our LAN of 15 users.
>
> the ISP has provided us with the following
>
> IP: 213.132.39.126
> SUBNET: 255.255.255.252
> GATEWAY:213.132.39.118
>
> PREFERED DNS: 213.132.33.19
> 2ndary DNS: 213.132.33.20
>
> The Server has one NIC configured as DHCP server with
>
> IP: 192.168.1.5
> SUBNET: 255.255.255.0
>
> SCOPE is 192.168.1.15 to 192.168.1.200
>
>
> Can I setup my windows 2003 server to act as a roouter so that the clients
> can access the internet
>
> OR
>
> can you help me on how to configure my router to share this internet
> connection
>
> Please help

I would definitely use the router, not the server as the gateway to the
Internet. Just a warning though. Frankster's method will not work properly
if you are running the server as a domain controller. You will need to set
up DNS differently.

"Frankster" <Frank@SPAM2TRASH.com> wrote in message
news:jPCdnaGCNZNCFVLYnZ2dnUVZ_sSmnZ2d@giganews.com...
> No need to have your server do routing. Let the router do it :) All the
> IPs provided by your ISP would go in the router. Since you received a
> server IP of 192.168.1.5 while assigned dynamically, we can assume your
> router is already configured on the 192.168.1.x internal network. You can
> probably also safely assume that your router's internal IP is
> 198.1.168.1.1. You will follow suit with your server. It is always best
> for servers to have a static IP.
>
> Set up your server like this.... (turn off the DHCP server on your server,
> if it is running, the router is running DHCP - there should be only one
> DHCP server on the network)
>
> Ethernet adapter Wireless Network Connection: (of your server)
>
> Connection-specific DNS Suffix . : domainofserver.com
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.4 (static - outside
> of routers scoped DHCP range)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
>
> Set up your cleints like this...
>
> Ethernet adapter Wireless Network Connection:
>
> Connection-specific DNS Suffix . : domainofserver.com
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.165.1.5.........200
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192,168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.1
> Lease Obtained. . . . . . . . . . : Sunday, February 11, 2007
> 4:21:03 AM
> Lease Expires . . . . . . . . . . : Monday, February 12, 2007
> 4:21:03 AM
>
> Note: personally, I would set the scope narrower (i.e. 192.168.1.50 -
> 192.168.1.150). This leaves more room for configuration of static IPs for
> things like printers and more servers, etc.
>
> -Frank
>
> "sphilip" <sphilip@discussions.microsoft.com> wrote in message
> news:025DAD5C-AC5A-4BA7-95BB-3C07B1BA155D@microsoft.com...
>>I have a 2mbps adsl connection at work, the ISP terminated a RJ45 pin &
>>left
>> it with us to setup the internet for our LAN of 15 users.
>>
>> the ISP has provided us with the following
>>
>> IP: 213.132.39.126
>> SUBNET: 255.255.255.252
>> GATEWAY:213.132.39.118
>>
>> PREFERED DNS: 213.132.33.19
>> 2ndary DNS: 213.132.33.20
>>
>> The Server has one NIC configured as DHCP server with
>>
>> IP: 192.168.1.5
>> SUBNET: 255.255.255.0
>>
>> SCOPE is 192.168.1.15 to 192.168.1.200
>>
>>
>> Can I setup my windows 2003 server to act as a roouter so that the
>> clients
>> can access the internet
>>
>> OR
>>
>> can you help me on how to configure my router to share this internet
>> connection
>>
>> Please help
>

> I would definitely use the router, not the server as the gateway to the
> Internet.

Yep.

> Just a warning though. Frankster's method will not work properly if you
> are running the server as a domain controller. You will need to set up
> DNS differently.

Agreed. I started to write it up that way (as a DC server), but then I
figured, if it was a DC he would have said something about it. Or, maybe
not :)

-Frank