I'm not sure whether this is a Windows problem or a .NET problem (i.e. whether it belongs here on on SO), but I've written a small HTTP server program in C# (using the .NET HttpListner class) which works fine for the most part, but Windows Firewall seems to be refusing to let connections through to it from anything other than localhost. I've added exceptions for TCP and UDP in the "Inbound Rules" section of the firewall settings, essentially duplicating existing rules for other HTTP-based services which work fine (e.g. foo_httpcontrol). Specifically, I've added separate rules for TCP and UDP connections covering all ports, specific to the executable I'm running.

There's no problem when Windows Firewall is disabled, but if I enable it, the connection simply times out.

link|improve this question

60% accept rate
feedback

2 Answers

HttpListener uses Http.sys. See this msdn article.

link|improve this answer
feedback

Are those other HTTP-based services still running when you try to access your server?

link|improve this answer
Yes, but on different ports, of course. – Will Vousden Jan 12 '11 at 9:45
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.