help on server internet sharing

[timbo343]

I need help...

I need to be able to share a network connection on server 2003 R2 as this computer is acting as a gateway to another network which is providing the internet. So.. In the server there are 2 network cards... internet feed (1) and the second (2) which is the LAN. The server can get out to the internet no problem but i cant seem to get the computers that are connected on the second network card to connect to the internet. I know that the client can see the server as it is joined to its domain. Any ideas on sharing Internet connections

Thank you

Tim

[Dos_Box]

Please list your IP configuration details for both cards. This will help immensly. It soundl like a configuration issue. Do you run DHCP\DNS etc on this server too?

[timbo343]

right... coming into the server is
IP 182.16.24.1

network card 1 address is
IP 182.16.31.251
Sub 255.255.248
Default Gate 182.16.24.1

Network Card 2 address is
IP 192.168.1.2
Sub 255.255.255.0
Default Gate 182.16.31.251

I do run dhcp and dns on this server too

Thanks

[NetworkGeezer]

OK stupid question but are you running RRAS, a proxy or any other inter net sharing mechanism on the R2 server?

[timbo343]

we aint running owt like that we thought you could share a network feed by banging another card in the machine

[NetworkGeezer]

we aint running owt like that we thought you could share a network feed by banging another card in the machine

Well your clients on the secondary network need to be able to see the broadband router/switch or a proxy on the R2 server.

Basically even though the R2 server has is multihomed, does it actually know it's a gateway?

[timbo343]

well im testing it with a cross over cable to the other machine

[NetworkGeezer]

well im testing it with a cross over cable to the other machine

Well the server is connected to two networks but itisn't configured to route packets from one to the other.

[timbo343]

well how do i set that up??? could you help

[NetworkGeezer]

To be honest I not really sure how to do it on an R2 server. I tried reading the IPv4 routing guide on Technet and the will to live.

A quick and dirty solution would be to stick a proxy e.g. squid on the R2 server.

Alternatively if you have an old base unit knocking about why not put smoothwall on that and have it acting as the network bridge.
It would have the advantage of not straining your server while it does other things.

[Ric_]

Does R2 of Server 2003 not come with th Internet Cnnection Sharing?

Simply click the sharing tab for the properties of the Internet-connected NIC and tick the little box.

This will set up NAT and the like for you and run its own DHCP server - the address range, etc. cannot be changed.

My advice would be to set up a box running IPCop, SmoothWall, Censornet or the like. Any of these would give a lot more flexibility too - plus they will only take you half an hour to get up and running

[Dos_Box]

right... coming into the server is
IP 182.16.24.1

network card 1 address is
IP 182.16.31.251
Sub 255.255.248
Default Gate 182.16.24.1

Network Card 2 address is
IP 192.168.1.2
Sub 255.255.255.0
Default Gate 182.16.31.251

I do run dhcp and dns on this server too

Thanks

Please list your DNS settings too (it IS always DNS).

[Geoff]

Network Card 2 address is
IP 192.168.1.2
Sub 255.255.255.0
Default Gate 182.16.31.251

Gateway is wrong. Needs to be an IP on the subnet. eg, 192.168.1.1

[timbo343]

does anyone know of any open source software that i can use for a proxy server on this machine??

Thanks

[NetworkGeezer]

Squid is an OSS proxy which has a Windows version availible.