> You shouldn't have to put MX-records on your external nic. Your
> make those MX-records and point them to your public IP.
Thank you for replying, but I think you misunderstand what I am
Very simply, my SBS 4.5 external NIC has three public IP
When Exchange 5.5 starts, it binds to port 25 on each and all of
these IP addresses.
I want to server proxy port 25 on two of these IP addresses,
which means Exchange has to let go of them.
Allan Williams informed me that this cannot be done with Exchange
In microsoft.public.exchange.admin, Rich Matheisen, Exchange MVP
confirmed that Exchange 5.5 has no provision for specifying which
IP address it will bind to; but if another application binds to
the socket first, Exchange will not grab it.
So, I created a client wspcfg.ini that incorporates ProxyBindIP,
ServerBindTcpPorts, and ForceCredentials.
Stop the Exchange IMS on the SBS to free the bindings.
Start the client program which allows IIS to bind to the ports as
a server proxy for the client.
Start the Exchange IMS which binds to the remaining free IP
Thanks all for your help.