Multiple IP Addresses per NIC not working

[Guest]

Since installing Windows 2003 SBS we have had virtually no success in
getting the router to fully accept multiple IP addresses on a NIC. As the
server is not directly linked to our internal network, we use only one NIC in
the machine, which is intended to host several of our websites on separate IP
addresses (due to three having need for SSL). While we have a couple of
times managed to confuse the router into accepting multiple IP's on the
single NIC, we have found it to reset twice, and can no longer get more than
one address to show simultaneously. We have had to eliminate all additional
addresses, as the router seems to cycle through them.

Our internal network is linked to the modem / router via an ethernet
connection to a second router, behind which is our internal network. The
server is connected to the modem / router. This keeps our internal network
behind a firewall, while allowing us internal access to the server via a
different computer. Using multiple IP addresses on the server by adding them
to the advanced field, we are able to get a reply to pings from a computer on
the internal network, however, only a single address shows for the server on
the modem / router network list, and only the one shown allows traffic from
the internet.

My understanding is that the router should treat each IP address in the
NIC's list as though they were independent connections, and should show them
as individual connections. Is there something that we are missing in order
to make this happen?

Thanks in advance for any help.

Rick

 

[Phillip Windell]

Since installing Windows 2003 SBS we have had virtually no success in
getting the router to fully accept multiple IP addresses on a NIC. As the

What router?

Our internal network is linked to the modem / router via an ethernet
connection to a second router, behind which is our internal network. The
server is connected to the modem / router. This keeps our internal
network
behind a firewall, while allowing us internal access to the server via a
different computer.

None of that makes sense and just makes my head spin For it to make
sense you need to specifiy when you say router if it is a "real" router or
just a NAT based Internet Sharing Device. It also makes no sense why you
have a router between the SBS server and the rest of the LAN unless that is
really also a NAT Device and you are attempting to create a Back-to-Back
DMZ. But if it is not a NAT Device then there isn't much point in being
there.

If you are "publishing" these sites from a NAT Device so those on the
Internet can go to the Sites on the Server, then yes the NAT Device should
see each IP# separately and funtion fine, I don't know any reason it would
care that the MAC address is the same. However SSL may actually be the root
of the problem. You probably need to get it to work with basic HTTP first
to verify that it even functions to begin with before you introduce SSL.