I'm also getting the following in the event log:

Web Proxy service failed to bind its socket to 195.1xx.2xx.x port 80. This could
be caused by another service that is already using the same port or by a network
interface card that is not functional. The error code specified in the Data area
of the event properties indicates the cause of the failure. For more information
about this event, see ISA Server Help.

I've changed the incoming web requests to listen on the new IP address and
changed the external IP addresses on the sever publishing. Is there anything
else I can change or would you recommend a rebuild.

Jim

Give up on the dreaded 14120 error. There is no Unified Field Theory for the error, and we'll have to wait for a Q article or a service pack to see that one hit the road.

You should be able to change IP addresses for your publishing rules. I've tested web and server publishing rules with dial up connections that recieve different IP addresses each time they dial up. I have to change the IP address on the Inbound Web Requests Listener, and I have to change the IP address in all of the Server Publishing Rules. Then I restart the services (and hope the restart doesn't cause the connection to drop), and they all work fine.

You might try stopping all of the ISA Services, then disable and reenable the adapter, and then start the ISA Services and see if that helps.

Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

Get It Here