CODEWITHSUNDEEP
iisiis-express
Jammer
Jammer

Reputation: 10206

Binding IISExpress to IP Address Failing

I've had this working on the same Windows box in Win8 Win8.1 and Win10. Yesterday I performed the Threshold 2 upgrade to Windows 10 and now I can't launch my API in IISExpress.

The bindings are setup like this:

<binding protocol="http" bindingInformation="*:51258:jamhq" />
<binding protocol="http" bindingInformation="*:51258:192.168.0.8" />

I've triple checked all my netsh settings and at the moment Windows Firewall is completely disabled whilst I troubleshoot.

Every time I try to launch this I'm now presented with an error like this:

Failed to register URL "http://192.168.0.8:51258/" for site "<name>" application "/"
Error Description: The Network location cannot be reached.
For more information ... (0x800704d0)

I can ping this IP (obviously since I'm pinging myself), I can ping this location from my other machines / devices.

It seems like some extremely low level network setting has been changed.

Has anyone seen this problem or have a solution?

Upvotes: 9

Views: 3040

Answers (2)

mad lim
mad lim

Reputation: 1

I fix this by enable it globally thru my network, not only in specific IP.

From CMD(need to run as admin)

netsh http add iplisten ipaddress=0.0.0.0

Inside project applicationhost.config I put the binding globally as below:

<binding protocol="http" bindingInformation=":51258:" />

This will make your application can be accessed from all machine with the same network. Do note also for me I need to run visual studio as admin as well. It may not be true for your case.

Upvotes: 0

Jammer
Jammer

Reputation: 10206

So, this is something that might help others in the future, I've been going round and round on this problem today and have just fixed the issue.

It appears that the update removes IP addresses that the http.sys is listening on. So when executing:

netsh http show iplisten

The only entry I had after the update was:

::

So executing:

netsh http add iplisten 192.168.0.8

Bingo, everything is now working again.

Upvotes: 24

Related Questions