Sentry Page Protection
TCP IP 1

TCP Port 1666 may use a defined protocol to communicate depending on the application. A protocol is a set of formalized rules that explains how data is communicated over a network. Think of it as the language spoken between computers to help them communicate more efficiently.

 

Protocol HTTP for example defines the format for communication between internet browsers and web sites. Another example is the IMAP protocol that defines the communication between IMAP email servers and clients or finally, the SSL protocol which states the format to use for encrypted communications.

 

TCP Port 1666

 

 

 

Here is what we know about protocol TCP Port 1666. If you have information on TCP port 1666 that is not reflected on this page, simply leave a comment and we’ll update our information.

 

PORT 1666 – Information

•Port Number: 1666

•TCP / UDP: TCP

•Delivery: Yes

•Protocol / Name: netview-aix-6

•Port Description: maze

•Virus / Trojan: No

Tip! Use our free Digital Footprint and Firewall Test to help verify you are not infected.

 

 

Side note: TCP port 1666 uses the Transmission Control Protocol. TCP is one of the main protocols in TCP/IP networks. Whereas the IP protocol deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and also guarantees that packets will be delivered on port 1666 in the same order in which they were sent. Guaranteed communication over port 1666 is the key difference between TCP and UDP. UDP port 1666 would not have guaranteed communication in the same way as TCP.

 

Because protocol TCP port 1666 was flagged as a virus (colored red) does not mean that a virus is using port 1666, but that a Trojan or Virus has used this port in the past to communicate.

 

TCP 1666 – Disclaimer

 

We do our best to provide you with accurate information on PORT 1666 and work hard to keep our database up to date. This is a free service and accuracy is not guaranteed. We do our best to correct any errors and welcome feedback!

 

TCP Port 66 may use a defined protocol to communicate depending on the application. A protocol is a set of formalized rules that explains how data is communicated over a network. Think of it as the language spoken between computers to help them communicate more efficiently.

 

Protocol HTTP for example defines the format for communication between internet browsers and web sites. Another example is the IMAP protocol that defines the communication between IMAP email servers and clients or finally, the SSL protocol which states the format to use for encrypted communications.

 

TCP Port 66

 

 

 

Here is what we know about protocol TCP Port 66. If you have information on TCP port 66 that is not reflected on this page, simply leave a comment and we’ll update our information.

 

PORT 66 – Information

•Port Number: 66

•TCP / UDP: TCP

•Delivery: Yes

•Protocol / Name: sqlnet,sql*net

•Port Description: sql*net.oracle sql*net

•Virus / Trojan: No

Tip! Use our free Digital Footprint and Firewall Test to help verify you are not infected.

 

 

Side note: TCP port 66 uses the Transmission Control Protocol. TCP is one of the main protocols in TCP/IP networks. Whereas the IP protocol deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and also guarantees that packets will be delivered on port 66 in the same order in which they were sent. Guaranteed communication over port 66 is the key difference between TCP and UDP. UDP port 66 would not have guaranteed communication in the same way as TCP.

 

Because protocol TCP port 66 was flagged as a virus (colored red) does not mean that a virus is using port 66, but that a Trojan or Virus has used this port in the past to communicate.

 

TCP 66 – Disclaimer

 

We do our best to provide you with accurate information on PORT 66 and work hard to keep our database up to date. This is a free service and accuracy is not guaranteed. We do our best to correct any errors and welcome feedback!

 

 

Go to page 13