Windows 2019 firewall blocking windows service with signalr

Question

0.00/5 (No votes)

See more:

Hi,

I am trying to host a windows service containing a signalr hub which has a custom port number (in my case 7777) on windows server 2019. However, the firewall is blocking my calling systems (.net clients) from calling the hub in the service at all. The network is the only place where this service/client interaction will occur. There is an external system but that is on a web site and I haven't had any real issues with that - yet - so my question is excluding that scenario for now. Can anyone advise as to how to set up a firewall rule in such a scenario short of switching off the firewall?

I've been checking several links and nothing seems to be resolving my issue and I think it is most probably something really small I am missing. Any advise will be greatly appreciated!

What I have tried:

0 - Running the client app on the server itself just to make sure it works correctly (which it did)
1 - Switching off the firewall to verify that everything is working correctly. The client app from other pcs on the network connects successfully but is obviously not what is needed for production.
2 - Set up an inbound rule for the actual service (on any port with any protocol) which did not work.
3 - Set up an inbound rule for the "services.exe" on my specific port I want to use which did not work.
4 - Set up an inbound rule specifically for the port (not specifying any program or service or protocol) which did not work.

Posted 2-Sep-19 15:00pm

nortee

Add a Solution

Comments

[no name] 2-Sep-19 23:30pm

Isn't there an IP address in there somewhere?

nortee 2-Sep-19 23:32pm

Hi Gerry,

No it's using the machine name. Like I said, it works fine if I switch off the firewall.

[no name] 18-Jun-20 17:30pm

After further investigation, it turns out the actual web listening was being hosted by the System process. As explained in answers to another question, apparently all HTTP listening winds up going through the System process.

Setting the application in the rule to "System" worked for this.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

User 14773238 · Answer 1 · 2020-06-18T11:29:00

Solution 1

After further investigation, it turns out the actual web listening was being hosted by the System process. As explained in answers to another question, apparently all HTTP listening winds up going through the System process.

Setting the application in the rule to "System" worked for this.

Posted 18-Jun-20 11:29am

User 14773238

Updated 18-Jun-20 11:44am