asked on

Windows Firewall - Rule created ports still not opemn

I've created basic inbound and outbound rules on Windows Firewall on a server that is off the domain - It runs an application which connects (on the localhost itself) using Port 48200, so I'm told anyway.

I have created the rules as attached (currently I'm onto All profiles, I initially started with Private) - I get no successful telnet connection and a 'netstat -n -p tcp' for open ports does not show the server listening\established on that port. I have seen the below line in 'netstat -a -n' which indicates the port is blocked - where have I gone wrong?

TCP ServerIP:51668 ServerIP:48200 SYN_SENT

Thanks
Inbound48200.jpg
Outboud48200.jpg

ASKER CERTIFIED SOLUTION

McKnife

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Bash

ASKER

We have two instances of this application: one is listening on 48002
TCP 127.0.0.1:48002 0.0.0.0:0 LISTENING
TCP 127.0.0.1:48002 127.0.0.1:50053 ESTABLISHED

But the second instance running on 48200 doesn't display any results - therefore are you saying that the troubleshooting isn't firewall based, as those rules come into play later, that it's an application issue?

McKnife

Exactly.

DonConsolio

Make sure your service is listening on ANY interface (0.0.0.0) or on the Ethernet interface.
Listening on localhost (127.0.0.1) only allows the local PC (the one the service is running on) to access your service.

Also make sure the ports and protocol match (48002/tcp or 48200/tcp)

Bash

ASKER

Thanks for the answers - I've flagged it to the application team as an app issue rather than firewall - will see what they come back with.

We do only want it running on the local host as it's an app on the server itself.