Why does the network routing configuration change?

Question

I have 2 NIC cards set up in my machine (running Windows 2003 Server), I have one on an internal network (192.168.1.3, gateway 192.168.1.1 and mask 255.255.255.0) and the other on internet facing network x.x.x147 and default gateway x.x.x.145, mask 255.255.255.240. I have configured the internal card (actually DHCP) with a metric of 999 for the connection. The internet facing card with a metric of 1 for gateway and connection.

I have added a persistent route to the internet gateway, and it makes the internet connection the default connection (what I want). But without warning the default connection changes to the Internal network, with the result that the machine is not visible from the internet.

Anyone could help me or tell me a better way to accomplish this would be greatly appreciated.

Answer 1

Well at least you know enough not to post your internet facing IP address ;)

I dont understand why on internal net nic you have the gateway as 192.168.1.1? It should be x.x.x.147. You state that the internal card is DHCP, which contradicts you setting the .3 address. This is where the conflict is. You need to turn off all DHCP and use only static routes on this machine. I assume the external address (.147) is not assigned by DHCP from your ISP, but rather a dedicated address.

Another way of doing this, and probably safer, is to put a router on the ISP connection, but configure up a DMZ which will allow the static address to your server from the net. This WILL require a 2nd IP address from your ISP.

Port 2 of the router should be DHCP server using NAT as 192.168.1.0/24, and should take the place of your 2nd NIC. Local workstations would be DHCP client, and would be able to get to the server as a true address on the Internet (via the DMZ). This way, you free your server from routing as well.

Answer 2

maximum prompt routers : -- have automobile-detect workouts that enable for configuring community settings and to setup static/dynamic IP's for prompt and the actual ethernet ports because you want to derive the make sure-IP from eth2 on the linux gadget ... which may be the WLAN enter to the router ... and also you'll draw extra factors from it. i do not realize the area the position you aspect out you may want to apply the linux gadget because the router ... in view that surely, you've a linux twin-adapter host ... it would want to easily finally end up forwarding all site visitors to the prompt router ... and that would want to do the forwarding to different hosts