I'm currently using 2003SBS to host two sites that require SSL.
I've assigned two public IP's to the WAN adapter to accomplish
this. I also have a 2000 server running ISA that act as the
gateway for my LAN. Here's some crappy ASCII art that may help
describe my setup
--- [2000 server] ---| <--- LAN gateway
ISP / |
--|---- |
Router \ |
--- [2003 SBS] -----|
|
|
\---- LAN
public IP pool address range: x.x.105.73 - x.x.105.78
public IP pool subnet mask: 255.255.255.248
Currently, my router has x.x.105.73, the 2000 server has x.x.105.75
, and 2003 SBS has x.x.105.74 and .76 all set staticly.
This setup works great unless the 2000 server is restarted (or its WAN
interface is disabled, then re-enabled). When it comes back online it
reports an IP address conflict on it's WAN interface. A quick look at
the ARP table on the SBS server reveals that it has assigned the
2000 servers public IP to its own WAN MAC address causing a conflict
on the 2000 server!
I've traced the network traffic during this process, and the SBS
server does indeed send an ARP response indicating that the
desired IP (x.x.105.75) is in use by the SBS server which simply
isn't true.
Is this a 'feature' of 2003SBS that prevents this type of setup?
I've never encountered this sort of behaviour before.
I have already replaced the WAN NIC on the SBS server to rule
it out.
Help!
Scott