Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, August 16, 2015 6:38 AM
Hi,
I am facing one issue with one application, that application is running on port "1423". Currently Application is not working and we found that other member servers are not able to connect to application server on port "1423". I added the Inbound and Outbond rule in Windows Firewall for port "1423" but still we are not able to connect to the application server, also that opened port is not showing in "netstat -ano" and we are not able to telnet the server on that port from other servers.
Now questions..
1. Why Netstat is not showing opened port "1423" even after we added the rule.
2. If port is opened why telnet is not working from other server.
3. Why Telnet is not working locally on application server where port is opened.
As per my understanding the application for which we added the port should take control of that port and only after that the port will be showing as Listening.
Need expert suggestion on this.
Regards,
SGH.
MCP, MCTS
All replies (2)
Sunday, August 16, 2015 7:16 AM âś…Answered
On Sun, 16 Aug 2015 06:38:07 +0000, Hi_SGH wrote:
As per my understanding the application for which we added the port should take control of that port and only after that the port will be showing as Listening.
Need expert suggestion on this.
Have you tried temporarily turning off the Windows Firewall completely? It
is possible that there is a problem with the app itself.
Paul Adare - FIM CM MVP
Wednesday, September 9, 2015 9:48 AM
Hi,
>1. Why Netstat is not showing opened port "1423" even after we added the rule.
The result of the netstat is not determined by firewall. Firewall is like a door, which will allow or deny traffic according to its' rules. Even we don't open the port in the firewall, the application is still able to bind on the specific port.
>>As per my understanding the application for which we added the port should take control of that port and only after that the port will be showing as Listening.
Correct!
If we didn't find the port in the result of netstat, it means that your application may be not able to bind on the port 1423 due to some reason.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].