How To Setup Your Own Proxy Server?

How can i make my linux box my gateway and Windows Server DHCP server?

• Hi, i will appreciate any guidance for the problem whose setup is as follows. 1) I have a linux calrconnect 5.0 box with 2 network interfaces which acts as my gateway, firewall, content filter and web proxy. I have assigned a public ip to one NIC and have assigned a static private ip to the other NIC. 2.) I have a Windows server 2003 E.E with 2 NIC. i connected a UTP from the Linux box with private ip assigned to one NIC of the WIndows Server and from the second NIC of the Windwos server connected a UTP to the ethernet switch. I wanted the Windows server to act as the DHCP server due to management and let all internet bound traffic out through the linux box-clarkconnect for bandwidth allocation and security. Please advise how should i assign the ip addresses. On the linux box, i did not do a NAT and it automatically allowed controlled browsing. I tried to make the Windows Server 2003 the DHCP server but failed as none of the clients picked up the ip addresses. The ip addresses are as follows; ip assigned to the 1st NIC of the Linux box connected to the internet --------------------------------------… ip: 41.210.xxx.xxx subnet: 255.255.255.xxx gateway: 41.212.xxx.xxx DNS1: 41..211.xxx.xxx DNS2: 41.211.xxx.xxx ip assigned to the 2nd NIC of the LINUX box --------------------------------------… ip address: 192.168.1.1 subnet mask: 255.255.255.0 gateway: 41.210.xxx.xxx DNS 1 & 2: as assigned to NIC 1 above ip assigned to NIC 1 of Windows Server --------------------------------------… ip address: 192.168.1.2 subnet mask: 255.255.255.0 gateway: 192.168.1.1 DNS 1 & 2 : Same as assigned to NIC 1 for Linux box ip address to NIC 2 of Windows Server --------------------------------------… This is a problem because i tried to assign an ip address (192.168.1.3) and did a NAT with the gateway being (192.168.1.2) and it did not DHCP or seem to work. I will really appreciate if anyone could solve this problem beacuse i tried all possible until i had to make the linux box the DHCP server and connect the Windows server directly to the switch with a static private ip address. Thank you all.

• Answer:

  If you want NAT to work on the Windows server, the two interfaces need to be on different subnets. So make the second interface 192.168.2.1, but I'm not sure why you would want all your Internet traffic to go through two NAT boxes. It makes more sense to simply connect NIC 2 of your Linux server to your switch, and NIC 1 of your Windows server to your switch, and not use the second NIC, just as you have it connected right now. Make sure DHCP is not running on the Linux server and enable DHCP on your Windows server. Use a gateway of 192.168.1.1. If your workstations can't find the DHCP server, that means you don't actually have DHCP properly running. Make sure DHCP is not running on the Linux server. Verify by disconnecting the Windows server and your clients should not find a DHCP server. Once you know for sure DHCP is not running on the Linux server, then re-connect the Windows server and if you have it configured correctly, the workstations should be seeded an address.