検索機能を使用して 500 を上回る Kepware の知識ベース記事の中から閲覧します。結果を絞り込むか、クエリーを下部の検索フィールドに入力します。

解決策が見つからなかった場合には、当社の PTC eSupport Portal で追加資料を確認することもできます。eSupport Portal へのログインを要求された場合、My Kepware の認証情報を使用できます。My Kepware アカウントが必要ですか? こちらで作成

各種検索方法:
View All Solutions

Kepware Knowledge Base: Solution


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


Last Update: 2018/11/07

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
KEPServerEX