Lost or unable to establish communications with IB TWS/GW

[ejzj1]

The connection to TWS (Papertrading) works. I receive Level II data for FDXS.

If I create a market order with SuperDOM, the connection to TWS is cancelled. The order appears neither in the TWS nor in the NT chart.
If I create a market order with the Order Ticket, the connection to the TWS is also cancelled. After the connection is re-established, however, the order appears in the TWS and in the NT Chart.

Why is the connection lost?

NT: 8.1.3.1 64
IB: Build 10.31.1g

[NinjaTrader_Erick]

Hello ejzj1 ,

Thank you very much for your post and for mentioning your IB version.

This was reported to be causes by the IB sofware auto updating to an "unsupported: version.

For this connection to work properly within NT8, you need to have the required version of TWS.

Please uninstall your current TWS and install the supported:

TWS 10.23.2a - Download


Once you have the version of Trader Workstation or IB Gateway as specified above, connect to your account within TWS or IB Gateway.

• After you are connected in TWS or IB Gateway, you are then able to connect to the account within NinjaTrader.

From here connect to your account and test if the charts are updating, and also test to see if you get disconnected after your orders.


Please let us know if we may provide any further assistance.

[ejzj1]

It works with TWS version 10.23.2a. Thanks for the help.

[ejzj1]

Another similar problem

NT: 8.1.4.1
TWS: 10.23.2a
NT can submit an order with these versions. It is displayed in the TWS.

However, TWS reports when starting:
Die von Ihnen verwendete Version der Anwendung (1023.2) erfordert ein Upgrade, da die momentane Version ab 20250320 nicht mehr unterstützt wird.


With
NT: 8.1.4.1
TWS: 10.30.1
NT subitted also an order. It is also displayed in the TWS. However, NT immediately terminates the connection to the TWS with the following message:

Paper Interactive Brokers: Lost or unable to establish communications with IB TWS/GW Please verify TWS/GW is running on the target machine and try reconnecting or contact support if the issue persists (Panic)

Is there a solution for this?