Posts: 49
Joined: 5.Feb.2005
From: Edmonton, Alberta
Status: offline
Greetings,
I'm configuring OWA using SSL bridging and now have this error from external clients. OS is W2k3, ISA2004. I started getting this error after entering the IP/name in the HOSTS file on the ISA server.
Error Code: 500 Internal Server Error. Internet Control Message Protocol (ICMP) network is unreachable. For more information about this event, see ISA Server Help. (10051)
The OWA/IIS system is a Virtual Machine running on a WindowsXP system with Microsoft Virtual Server 2005. I'm using ICS on my second NIC and my virtual machines are bound to this NIC. I've opened port 80/443 to my Virtual Server and the certificate is being passed just fine.
We're having a similar problem. Here are the details:
ISA Server 2004 Server 2003 P4 2.4GHz, 1GB RAM Minimal users connecting through ISA to a Server 2000 server running a web-application that's talking to a SQL server.
Following error is displayed when trying to connect to a web-application through ISA (outside network): --- Error Code: 500 Internal Server Error. Internet Control Message Protocol (ICMP) network is unreachable. For more information about this event, see ISA Server Help. (10051) ---
I have never seen this error before today, and the only way I've been able to get around it is by restarting the ISA server (ie. reboot)... This has now happened several times today. Any thoughts/help would be GREATLY appreciated...thanks in advance!
I had this happen just recently. Things were going fine last week, but this week I got the error.
I logged into the ISA server console and tried pinging the internal server (the webserver) that I told ISA to direct traffic to. It was coming up with the outside IP address for some reason. Weird. My split dns infrastructure hasn't failed me yet...
Anyway, I filled in the formerly blank textbox titled "Computer name or IP address (required if the internal site name is different or not resolvable" with the internal IP of the server and it fixed the problem.
Next step for me is to figure out what's up with my DNS, but at least I got it working.