# TCP Driver Diagnostics Error

**URL:** <https://forum.inductiveautomation.com/t/tcp-driver-diagnostics-error/18996>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [July 27, 2018, 12:33pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-diagnostics-error/18996 "2018-07-27T12:33:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![steve.korber](https://avatars.discourse-cdn.com/v4/letter/s/9fc348/32.png) [@steve.korber](https://forum.inductiveautomation.com/u/steve.korber)\
**Post date:** [July 27, 2018, 12:33pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-diagnostics-error/18996/1 "2018-07-27T12:33:38Z")

</div>

Hello,

I am having trouble with the TCP Driver. I notice this issue arises after the TCP Server I am running has been inactive for a while. When I close the TCP Server the Status tab says 0/1 Connected but the OPC Diagnotics tag “Is Connected” is still true. This is a problem because I use the “Is Connected” tag to update the PLC on the TCP status.

I will try to attache images.

Running Server 7.9.7 on Linux

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e4e35ccda313d36f3a67a3c127c307df27d01fa6.png)

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/393bcb7e97e5ea29d62e1a6366fa8bf95d193aff.png)

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/b/b79c2248577d2fa2ea6a9c7944a82ea031e5e88d.png)