[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 450
  • Last Modified:

port issues

I have a server that will not allow custom ports like 8080, 502 and 20 open.

My firewall has the ports open, but I don't see my server listening for the ports. Where do I set that? I already added the ports to the windows firewall.
4 Solutions
Dave BaldwinFixer of ProblemsCommented:
To open a port, you have to have a program that 'listens' at that port.  Programs that do that usually 'open' the ports when they are installed.  Why or what do you need those ports for?
To view the ports you are currently listening on go to start > run > cmd > type netstat -a  and press enter. As DaveBaldwin says you will need an application running on your server listening on those ports, opening ports on your firewall and windows firewall just means that any traffic destined for those ports can get through the firewall, it doesn't necessarily mean there is anything on the server listening on those ports.
Sorry @DaveBaldwin, I am going to try to scratch from you some points.
Port 20 is usually used by an ftp server application, so if you install an ftp server, the application will ask the server to route the traffic to itself.
Port 8080: Is usually used on http server. So you can set your web server to book that port. Microsoft Web Server is IIS.
Port 502: Don’t know what is used for…
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

jmahlmannAuthor Commented:
Hey all. Just found out that though it says the ports are closed we can actually use them! Port 18082 is for an anti-virus that is connected to a sever at another location. I checked that and the systems at the location A with the ports that are said to be closed are communicating just fine with the AV main console at location B.

Also it says 8080 is not working, but that too is working fine being able to get to OWA.

Also, I have run that command before which is why I knew the server was not listening for those ports.
Dave BaldwinFixer of ProblemsCommented:
With the standard Windows Firewall, it will allow outgoing connections to any port while blocking incoming connections.  You only need to open incoming connections when you have a service listening on those ports.  You don't need to open it when you are connecting to that port and service on another computer.  More sophisticated firewalls can be set to block in both directions.
Please close this question, if you dont need help with this anymore.

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now