I'm facing an issue where workstations need to connect to a server using port 9091, but we're running into connection failures. While the Windows firewall shows that port 9091 is open, the server doesn't indicate that it is listening on that port. When I try to telnet from the workstations to the server, I receive a 'connection failed' error. This connection is crucial for specific software, but the vendor hasn't been able to identify the issue since their logs show an error stating 'Cannot connect to 192.168.0.134:9091.' I did run a Simple TCP Listener on the server to test and it successfully accepted connections on port 9091. I've also tried disabling the Windows Firewall and Malwarebytes completely, but the problem persists. Any help would be greatly appreciated!
3 Answers
I totally get your frustration! Have you tried looking at the server's application logs? Often, they can give you insight on whether the software itself is having issues. Also, it might be worth checking if the software needs certain permissions or configurations before it can bind to that port.
It sounds like you've done some troubleshooting already! Remember, only one program can listen on a given port at any time. Since your Simple TCP Listener worked, it suggests that nothing else is using port 9091 right now. You might want to check if the main application is crashing or possibly using a different port instead. Double-check the application's settings and logs.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures