Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

KEPServerEX Uses a New Source TCP Port When Reconnecting to a Device

Last Update: 11/7/2018

The Microsoft operating system keeps a list of all unused public ports available. When a KEPServerEX Ethernet driver makes a connection to a device, it asks the operating system for a port and is given one (sometimes referred to as a TCP Socket). This port is used as a TCP or UDP source port until an error is received (like the device is not longer responding). At that time, the socket will be released and KEPServerEX will ask for a new one. The operating system automatically gives the next available port, thus ensuring that a bad message is not sent back erroneously from the device. Because the operating system is managing this, the ports are eventually re-used and there is no impact on the available system resources.

Related Products