The end result of what I'm trying to do is to host 2 different SSL sites on one Windows Server machine. My current setup is as follows starting from ISP and following to the server - 1 DSL modem into 1 switch running into 2 routers, each configured with a different static public IP address. Each router is connected then to one of the 2 network cards on the Windows Server 2003 machine. The internal IP address of router A is 192.168.1.1 and corresponding network card A is 192.168.1.2. The internal IP of router B is 192.168.11.1 and corresponding network card is 192.168.11.151. Router and NIC A have been working well for quite a while hosting 1 SSL site. The problem is when we now want to host a second SSL site. My understanding is that because this is a secure site, the SSL certificate has to be tied to its own public IP. Thus, using host headers and just hosting on our other IP is not an option. It seemed that this configuration would work. It is a mirror image of the setup of the first site including port forwarding and domain name registration. This second site does actually work if I disable network card A on the server and allow NIC B to be the only one. But, as soon as I enable NIC A making the first site come back up, the second site on NIC B no longer functions. I must be missing something about how to setup dual NIC. When I configure the second NIC it gives me an error message about having 2 default gateways on the same network not working properly. I've tried to put both routers on the same subnet and that didn't help. I really think there must be some way to host 2 secure sites on one machine. Thanks.