Connetion issue with Kinetickt today

[sys_trader]

I have Kinetick real time data feed. Today, it happened 3 times that Ninjatrader lost connection silently. The status was actaully green and connected. However, charts stopped moving and Level 1 stopped straming. On top of this, it failed silently. I did not hear "connection lost". So looked at the trace log. Here is what I found


016-06-07 13:19:35:571 (Kinetick) Kinetick.Adapter.connectionTimer: reconnecting to level1 by closing the socket, socket!=NULL
2016-06-07 13:19:35:571 (Kinetick) Kinetick.Adapter.connectionTimer: level1 socket closed
2016-06-07 13:19:35:571 (Kinetick) Kinetick.Adapter.L1Worker: restarting L1 thread after connection loss...
2016-06-07 13:19:35:571 (Kinetick) Cbi.Connection.ProcessEventArgs.ConnectionStatusEv entArgs ConnectionLost ConnectionLost NoError Unexpected disconnect from level1 data server. Trying to reconnect...
2016-06-07 13:19:35:586 (Kinetick) Kinetick.Adapter.L1Worker.Connect: '66.112.148.228:60003'
2016-06-07 13:20:17:902 ERROR: Kinetick.Adapter.L1Worker: System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 66.112.148.228:60003
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.Socket.Connect(IPAddress address, Int32 port)
at NinjaTrader.Dtn.DtnSocket.Connect()
at NinjaTrader.Dtn.Adapter3.L1Worker()
2016-06-07 13:20:17:902 (Kinetick) Cbi.Connection.ProcessEventArgs.ConnectionStatusEv entArgs Connected Connected NoError
2016-06-07 13:20:17:902 (Kinetick) Cbi.ConnectionStatusEventArgs.Process: ConnectionLost ConnectionLost

Then followed by a bunch of the following until I manually restarted it

2016-06-07 13:20:17:949 (Kinetick) Cbi.ConnectionStatusEventArgs.Process: Connected Connected
2016-06-07 13:20:25:558 (Kinetick) Kinetick.Adapter.connectionTimer: reconnecting to level1 by closing the socket, socket=NULL
2016-06-07 13:20:25:558 (Kinetick) Kinetick.Adapter.connectionTimer: level1 socket closed
2016-06-07 13:20:35:558 (Kinetick) Kinetick.Adapter.connectionTimer: reconnecting to level1 by closing the socket, socket=NULL
2016-06-07 13:20:35:558 (Kinetick) Kinetick.Adapter.connectionTimer: level1 socket closed
2016-06-07 13:20:45:558 (Kinetick) Kinetick.Adapter.connectionTimer: reconnecting to level1 by closing the socket, socket=NULL
2016-06-07 13:20:45:558 (Kinetick) Kinetick.Adapter.connectionTimer: level1 socket closed
2016-06-07 13:20:55:561 (Kinetick) Kinetick.Adapter.connectionTimer: reconnecting to level1 by closing the socket, socket=NULL
2016-06-07 13:20:55:561 (Kinetick) Kinetick.Adapter.connectionTimer: level1 socket closed

[NinjaTrader_DrewO]

Hello,

Thanks for your post.

When this behavior appears, or any connection losses in the platform, we recommend starting by restarting your PC, modem, and router. Wait a few moments and then restart these devices. If this behavior appears frequently, or if this does not resolve this matter, please reach out to us at Platform Support.

In this case, I'd like to check your log and trace files for other errors and relevant information. Please send me a note to platformsupport (at) ninjatrader (dot) com. Attach your most current log and trace files to the email, and put a link to this forum post in the body of the email. Please note "ATTN: Drew" in the body of the response.

You will find the log file on your PC in the (My) Documents > NinjaTrader 7 > Log folder.

The log file will be named "log.20160607.txt"

You will find the trace file on your PC in the (My) Documents > NinjaTrader 7 > Trace folder.

The trace file will be named "trace.20160607.txt"

I look forward to hearing from you.

[radicaltrader]

Hi sys_trader,

Was your problem fixed?
How often do you lose your connection?
Was this a once off event?

I wish NT was able to fix my silent disconnections, seam to be a connection issue between my broker and NT.

Its a real pain reestablishing strategies after the loss.

[sys_trader]

It is good now. It was actually my network issues.

Rarely do I encounter connection issues.