Product Support

Product FAQs

QUESTION

Why can’t I reconnect to my NPort after my client application unexpectedly closed?

After my client application unexpectedly closed and lost connection with my NPort, I am not able to reconnect to the NPort. I can open the NPort’s web console, but I cannot establish a TCP connection with the NPort.

SOLUTION

Specify a suitable TCP alive check timeout (default = 7 min) to ensure that the NPort closes the connection socket when a TCP connection times out.

Until the TCP Alive Check time is reached, a client is still considered to be “alive”. Hence the NPort
considers the client to be connected even though the client application has closed.

If you set the TCP Alive check timeout to 0, NPort will not send TCP Alive Check packets to the client. In this case, you might need to restart the NPort manually so that the client program can reconnect to the NPort.

Relevant Products

CN2600 Series · MiiNePort E1 Series · MiiNePort E2 Series · MiiNePort E3 Series · MiiNePort W1 Series · NE-4100 Series · NE-4100-ST Series · NPort 5000AI-M12 Series · NPort 5100 Series · NPort 5100A Series · NPort 5200 Series · NPort 5200A Series · NPort 5400 Series · NPort 5600 Series · NPort 5600-DT Series · NPort 5600-DTL Series · NPort 6100/6200 Series · NPort 6400/6600 Series · NPort Express Series · NPort IA5000 Series · NPort IA5000A Series · NPort IA5000A-I/O Series · NPort IAW5000A-I/O Series · NPort P5150A Series · NPort S8000 Series · NPort W2150A/W2250A Series ·

Was this useful?
Rate this article
Thanks for rating our content. Any comments or suggestions?
 
Thanks for your feedback!
  •   Print this page
  • You can manage and share your saved list in My Moxa
Contact Moxa Support

Still need assistance with your Moxa product? Get help and save time by initiating an online support request and we will connect you to an expert.

CONTACT US
Added To Bag