Author Topic: Not able to protect outgoing mail  (Read 19315 times)

0 Members and 1 Guest are viewing this topic.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re:Not able to protect outgoing mail
« Reply #15 on: October 31, 2003, 01:51:30 AM »
You can use tcpview to find out what program is listening on which port.

http://www.sysinternals.com/ntw2k/source/tcpview.shtml


Vojtech, thank you for the link  ;)
Could you answer my posted question? Could you tell us the range for port numbers, I mean, what is the range (from... to...) the user can set for listening ports to use Internet Mail...  ;)
The best things in life are free.

Offline vojtech

  • Avast team
  • Advanced Poster
  • *
  • Posts: 939
    • ALWIL Software
Re:Not able to protect outgoing mail
« Reply #16 on: October 31, 2003, 11:06:52 AM »
Port is a 2-byte number, i.e. 0-65535. Some numbers are declared as 'well-known' and some as 'registered' (see http://www.iana.org/assignments/port-numbers). But on an ordinary-user computer only few of them are used. You can choose as you like from the ports that are not already used on your computer.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re:Not able to protect outgoing mail
« Reply #17 on: October 31, 2003, 12:16:16 PM »
Port is a 2-byte number, i.e. 0-65535. Some numbers are declared as 'well-known' and some as 'registered' (see http://www.iana.org/assignments/port-numbers). But on an ordinary-user computer only few of them are used. You can choose as you like from the ports that are not already used on your computer.


Thanks again for your information ;)
What does that link do? It seems a list of ports managed by IANA but not mine, I mean, who is connecting their server at which port...  :-\
The best things in life are free.

Hornus Continuum

  • Guest
Re:Not able to protect outgoing mail
« Reply #18 on: November 05, 2003, 08:11:01 AM »
Technical,

The IANA port lists identify known uses for TCP/UDP ports.  "The Well Known Ports are those from 0 through 1023 and on most systems can only be used by system (or root) processes or by programs executed by privileged users."  Their use is standardized, to perform a specific task using a specific protocol.  For example, the FTP and FTP_DATA ports (ports 21 & 20 respectively) are used for FTP transfers, and all FTP servers expect FTP clients to use these ports in a standard fashion to establish connections and perform a transfer.

The Registered Ports are those from 1024 through 49151.  "The Registered Ports are listed by the IANA and on most systems can be used by ordinary user processes or programs executed by ordinary users."  Product and service developers register their products to use these ports.  Applications using these ports may use standard or proprietary protocols.  Examples are TCP/UDP ports 1214, which are registered for use by the KAZAA network.  Rights to use these ports are not exclusive evidently as IANA indicates that TCP/UDP ports 4000 are used both by Terabase and ICQ.

The Dynamic and/or Private Ports are those from 49152 through 65535.  These ports are for use in situations where the port on which a connection is made changes with each use or in private networks.  Applications using these ports may use standard or proprietary protocols.  For an example of dynamic ports, a client makes a connection to a static port, and the server examines a list of ports that it services and responds with an available port to be used for a transaction.  An example of private port usage: an equipment manufacturer provides for Internet connections using a private port for firmware updates.

Using the IANA port list won't tell you exactly what is going on with a particular connection, but it can provide a clue as to whether it is legitimate or not.  For example, if your firewall log indicates that a connection made by an application, whose executable you don't recognize, is using TCP port 1352, a check with the port list will show you that this port is registered for use with Lotus Notes.  If you are using that application, then you can probably relax, but if not, it may be an indication that your computer is infected with some malware, and you should do some investigating.

Regards,
Hornus

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re:Not able to protect outgoing mail
« Reply #19 on: November 05, 2003, 11:49:42 AM »
Thanks for your time, patience and knowleagde...
I'm becoming to understand a little about ports and communications...
The best things in life are free.