one server multiple public ip

[melgamal3]

Hi, I have the following configuration which involves multiple default gateway

http://www.mydomain.com

-> 66.xx.xx.xx -> router 1 (10.1.1.1) -> nic 1 (10.1.1.15) default gateway: 10.1.1.1 (on server 1)
-> IISwebsite1

help.mydomain.com -> 67.xx.xx.xx -> router2 (192.168.1.1) -> nic 2 (192.168.1.10) default gateway: 192.168.1.1 (on server 2) -> IISwebsite2

I can't use iis host headers cause I also want to use multiple services using default port #'s

the problem is multiple default gateways on the same server (192.168.1.1 and 10.1.1.1) creates problems in windows 2003 removing one of them e.g. 192.168.1.1 will result on traffic comming to nic 2 to be responded thru nic 1 at which the wan client doesn't receive the response.
Please advice

 

[Stevehewitt]

Need a better description of the problem I think. Windows 2003 fully supports multiple NIC's, subnets and gateways. Maybe worth playing with the 'route' command.



Steve.

"They have the internet on computers now!" - Homer Simpson

 

[MITPRO]

Have you tried multihoming?

 

[blakey2]

Hi,

I'd build an open source router using pfsense:

http://www.pfsense.com

It will support multiple external IP addresses, and multiple WAN links if required.

Super duper easy to install with a v.nice web interface for configuration.

Then just use NAT (port Forwarding) for your external IPs to the internal IIS servers.

Cheers.

 

[melgamal3]

Thanks everybody for your replies.
but this configuration used to work well on windows 2000 server, now after we upgraded to w3k, we are facing the issue of the default gateway getting dropped for one of the nics randomly after some time, and wan clients to that server can only browse thru the nic with an un-dropped default gateway

 

[melgamal3]

for multi-homing, all I found falls under adding additional nics or ip

and here is the current routing table after removing one of the two default gateway
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 a0 24 bb 94 fe ...... 3Com 3C905TX-based Ethernet Adapter (Generic
)
0x10004 ...00 13 20 0a 30 2e ...... Broadcom NetXtreme 5751 Gigabit Controller
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.11 1
10.1.1.0 255.255.255.0 10.1.1.11 10.1.1.11 1
10.1.1.11 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.1.1.11 10.1.1.11 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.3 192.168.0.3 1
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.3 192.168.0.3 1
224.0.0.0 240.0.0.0 10.1.1.11 10.1.1.11 1
224.0.0.0 240.0.0.0 192.168.0.3 192.168.0.3 1
255.255.255.255 255.255.255.255 10.1.1.11 10.1.1.11 1
255.255.255.255 255.255.255.255 192.168.0.3 192.168.0.3 1
Default Gateway: 10.1.1.1
===========================================================================
Persistent Routes:
None

 

[melgamal3]

Now the configuration below used to work in windows 2k server and works in windows 2003 server for a while before it drops one of the default gateways

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 a0 24 bb 94 fe ...... 3Com 3C905TX-based Ethernet Adapter (Generic
)
0x10004 ...00 13 20 0a 30 2e ...... Broadcom NetXtreme 5751 Gigabit Controller
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.11 1
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.3 1
10.1.1.0 255.255.255.0 10.1.1.11 10.1.1.11 1
10.1.1.11 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.1.1.11 10.1.1.11 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.3 192.168.0.3 1
192.168.0.3 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.3 192.168.0.3 1
224.0.0.0 240.0.0.0 10.1.1.11 10.1.1.11 1
224.0.0.0 240.0.0.0 192.168.0.3 192.168.0.3 1
255.255.255.255 255.255.255.255 10.1.1.11 10.1.1.11 1
255.255.255.255 255.255.255.255 192.168.0.3 192.168.0.3 1
Default Gateway: 10.1.1.1
===========================================================================
Persistent Routes:
None

 

[SuperJenks]

I have basically the same set up on windows 2k and it works fine with multiple gateways. However, experts still recommend not having multiple gateways, but I have been running this setup on my 2k server for 3 straight years and have never had one problem. I dont understand why it would be an issue on 2003 server, especially when you have 3 different subnets. I can understand if they were all on the same segment of the subnet, but why shouldnt you be able to assign multiple gateways on seperate subnets and NICS. What you may want to try in the route add command is this:

Notice in the second table you show, you have 2 default gateways, both with the destination set as 0.0.0.0 That is the part that the server doesnt particularly like because ultimately it doesnt know which one to use. Try leaving the destination and subnet mask as 0.0.0.0 for the 10.x.x.x nic, and use 192.0.0.0 for destination and 255.255.255.0 for the 192.xxx.xxx.xxx Nic. The ultimate goal would be to only have one true default route with 0.0.0.0 destination so the server doesnt get confused and drop it. It should still route the traffic against the route table while eliminating one of the default routes. Also, make sure you assign the correct interface number corresponding to the proper network. Hope this makes sense to ya.