Web Proxy fails to bind its socket and Proxy chain loop
Posted on 2003-02-24
I have a Windows 2000 box with Small Business Server 2000. It has two NICs. 1- WAN Internet, 2-office LAN. I have a problem with event id 14148 in Microsoft Web Proxy. The description is the web proxy service failed to bind its socket to xxx.xxx.xxx.xxx (the WAN IP address) on port 80. The thing is, it DOES seem to be binding to the WAN IP on port 80. I ran a port information program and it shows w3proxy waiting on the WAN IP, port 80.
Unless I'm mistaken (and I could be) I want it (w3proxy) binding to the LAN NIC not the WAN. The problem it causes is that Inetinfo can't grab port 80 on the WAN side to serve web pages like it should. w3proxy and Inetinfo seem to be fighting over port 80 on the WAN IP. If I stop w3proxy, Inteinfo will take the WAN IP over on port 80, but if I restart w3proxy, it takes over again.
(I'm going to give several pieces of information because I have a hunch they're connected, but don't know for sure. )
In a related note, I also have event id 14141 - proxy chain loop. I have a routing policy error apparently. I have only 2 rules and a Last Default rule. I can give more info on that if needed. I don't know if that's related to the event 14148.
In Microsoft's Technet, I read that 14141 chain loop can be related to a bad NIC or high network traffic on the NIC. In the SBS Administrator console Health monitor, there are two critical alerts on the NetworkInterface. On the first, the threshold info is "Bytes Total/sec > 500000" Network Interface Critical Condition WMI status: 2147749889. The second one is also "Critical" The threshold says: "Error Code (from WMI)" and it gives the same alert as #1. Looking at the hub, I see no major traffic, certainly not "> 500000 B/s". It's a small office, less than 8 PCs.
That's all I have for now.
I'm all ISA'd out. Hope you can help.