Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 326
  • Last Modified:

strange port communication

Hi,
I have two computer communicating (one inside the network, the other on the outside the network).

The are both using strange port numbers that are not commonly used.  (Port 52497 for the external IP address and 9678 internally)

My question is
1. Shouldn't the firewall  be configured to prevent outgoing ports except for typical ports (80, 443, etc?)
2. Should the firewall be configured to only allow in commonly used ports (port 80, 443)?

Thanks.
0
NYGiantsFan
Asked:
NYGiantsFan
  • 2
4 Solutions
 
brokenbyteCommented:
1. Most firewalls allow outgoing traffic through most ports, especially when the traffic is initiated internally as a request, which might then be sent out on a different port, depending on the service.

The default action for a firewall is to block all unsolicited traffic coming in to your network.

2. Even if you configure a firewall to allow say, port 80, 443, 3389, to come in as an example, the originating port could be a random port (such as 52497 in your case.) The important port is the *destination*. And that is the port that is the focus when setting up your firewall rules.
0
 
Ugo MenaCommented:
Port 9678 is registered to EMC2 (Legato) Networker or Sun Solcitice Backup (Official) processes. Do you know if any of these backup services are supposed to be running to/from your network?

Depending on the type of firewall in your environment, most of the outgoing ports are going to be open to allow internal clients to connect to various external resources. Unless you are hosting a site/application/etc from your local network, almost all of the incoming ports to your network should be closed by the firewall to prevent incoming connections.

To get a better indication of who you are connecting to, you should check for the external IP address and then check it against whois
0
 
Ugo MenaCommented:
Could also be someone streaming Quicktime content.
0
 
giltjrCommented:
Some protocols also negotiate to use different ports.  Example: FTP.  

FTP has two connections, a command/control connection and a data connection.  

There are two types of data connections: active and passive.  If doing active FTP, the server initiates a outbound connection to the client from port 20 to a random high port.  When doing active the client tells the server what port it is listening on buy the FTP PORT/EPRT commands over the command/control connections.

 If doing passive the client initiates a connection to the server from a random high port to a random high port.   In this situation the server tells the client what port it will be listening on using the PASV/EPSV commands.

Most firewalls "listen" in on the command/control connection (typically port 21) for the PORT/EPRT/PASV/EPSV commands and dynamically create a rule to allow the data connection.   Once the transfer is done, based on the data connection being reset, the firewall dynamically removes this rule.

I believe there are other protocols/products that do this also.
0

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

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