Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Problem with IB, keeps opening the login screen

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NinjaTrader_Brett
    replied
    Hello,

    Welcome to the support forums!

    For assistance with login issues please email me at support at ninjatrader dot com. This way we can assist on your individual case.

    I look forward to assisting you further.

    Leave a comment:


  • curmudgeon
    replied
    IB resets itself on logging in

    I seem to be able to log in to IB via Ninja Trader only about a tenth of attempts.

    It shows the login screen, by the time I input my password and my security code, I then get a flash screen and it loads peaceably. But then Ninja Trader seems to kill the session, tries to restart with a fresh login screen, and I put in the login, password, and security code yet again, to come to the same thing, with a progressing progress bar at the bottom.

    Is there a way to increase the delay that Ninja Trader waits before aborting the IB login ? It does seem to take a bit of time for me, and your system does not appear sufficiently patient.

    For the avoidance of doubt, I have no intention of disarming the security code mechanism, and do not feel comfortable having Ninja Trader or any other system retain my username and password. If the delay of me inputting security is the problem, then there's a design issue here

    PS: TWS 917.9a

    PPS: it does work better when I turn off any other applications that use Java, but this is a nuisance to stop them and restart each time I want to log in to NJ/IB
    Last edited by curmudgeon; 10-03-2011, 01:14 PM.

    Leave a comment:


  • mate41
    replied
    Hello,
    if this can help:
    i readed the full thread and nowhere it appears that the API-Orderpage must be filled on the TWS.
    This Orderpage has to be filled every time you connect to IB.
    This is what i have to do with version TWS 917.8.

    Leave a comment:


  • NinjaTrader_Brett
    replied
    Hello,

    We will update our version of IB TWS at regular intervals with our releases as development tests and issues an update. Due to the number of releases IB has, we naturally will be behind them in releases simply since we do not release our product as often.

    Also, our development team does update our supported version of TWS as needed.

    As of current the supported version of TWS is still 917, you will find that we will almost always be behind IB current release due to the above facts and that we like to test our product integration and make sure everything works before we up our supported version.

    Thanks for your understanding.

    Leave a comment:


  • DaveDave
    replied
    NinjaTrader_Brett, your comments about testing API stuff I think was the reason for claiming that NT does not connect to a "new" version of IB?

    But surely the point about why it has stopped working is not that there has been an API change (other programs still work I find), but that they changed an undocumented aspect of the TWS that you happen to rely on, namely the way they caption the window title bar?
    And thus onus is on you to address it promptly rather than makes excuses?


    Anyway many thanks to HKinani for the workaround.

    Leave a comment:


  • Jeremytang
    replied
    Workaround

    Just verified that the workaround suggested by HKinani works:
    - use your actual IP address (not localhost or 127.0.0.1) to connect to the TWS

    This will circumvent NT's flawed Auto Login routine that apparently doesn't recognize that TWS is up on the local machine.

    Checking Auto Login off really should just skip this routine, but it doesn't for some odd reason (as far as I can tell the Auto Login option actually does nothing).

    The same work around can be used to connect to the IBG.

    Jeremy

    Leave a comment:


  • NinjaTrader_Brett
    replied
    Originally posted by mate41 View Post
    Hello,
    maybe you finally found the problem.
    But did you think about put tickers (instruments) in your API page on the TWS platform ?

    Not sure I understand sorry.

    Leave a comment:


  • mate41
    replied
    Hello,
    maybe you finally found the problem.
    But did you think about put tickers (instruments) in your API page on the TWS platform ?

    Leave a comment:


  • aviat72
    replied
    Brett:

    The changes in IB API very rarely if ever break existing code. I use other commercial programs which use the IB API and they are able to update it, often in advance. It seems IB will share their upcoming releases with those vendors who are interested.

    Leave a comment:


  • piptek
    replied
    Gave up on IB TWS

    TWS is a primitive platform so as IB's charts. I use TWS platform for their great comm. I am only using futures(/GC and /CL) from TWS and Mbtrading for the stocks in two different computers. So I am good. I hate to interact IB customer support . If I subscribe NT datafeed , I will pick anyone other than interactive brokers that much I can garauntee.

    Leave a comment:


  • NinjaTrader_Brett
    replied
    Hello,

    This is actually not the full case.

    The auto start is not the reason why we do not allow future releases to be used. It is one of the reasons but is not all of the reasons.

    There are many API changes from IB that we have to test and make sure they don't change how the connection works and many other changes that we need to test before we update. Yes you could go ahead and install the latest version of TWS and use that with the below fix. However it is not recommended, especially for traders that want something that simply works and works well.

    We like to reduce chances for problems, this is the reason for this.


    Let me know if there are further questions I can answer.

    Leave a comment:


  • Exhorder
    replied
    Originally posted by aviat72 View Post
    Connecting to IB via an API is very very simple. Do emphasize the need to fix it.

    You may need the windows name stuff for auto-logon but most of us will not mind starting TWS independently instead of NT doing auto-logon as long as we can use the latest TWS.
    99% of all users unable to run NT on the latest TWS release just for saving the trouble of doing one mouseclick for maybe 1% to start TWS manually is a pretty high price to pay in my view.

    Since there is an easy way to solve the problem (thanks @HKinani), this could have easily been fixed in the ....0.7 release by just adding a checkbox which lets the user choose if he wants auto logon or not. This could also make NT compatible to all newer TWS releases instantaneously.

    Leave a comment:


  • piptek
    replied
    Originally posted by NinjaTrader_Brett View Post
    Hello,

    Interactive brokers requires and exchange setup for the instrument to request the data. Other providers do not require this however IB does.

    To get data you will need to go to control center->tools->instrument manager->edit the stock->check the exchange it trades on.



    Let me know if I can be of further assistance.
    Thanks Brett for the solution. However I am not going to do that tidious process going through 100s and 100s of tickers and edit exchange individually . Can't believe in this day and technology someone has to do that to make IB datafeed work. I will stick to MB or TDA (TD ameritrade) or esignal.

    Leave a comment:


  • dimkdimk
    replied
    Originally posted by HKinani View Post
    Bypass the problem by configuring the IP setting of the NinjaTrader IB Connection with the IP of the machine. (instead of the local host 127.0.0.1).
    Mate! I will buy you a beer if I could find you :-) Finally, one reasonable workaround !

    To NT guys: Common guys! This is totally inappropriate to keep people waiting for some "ETA" etc. Simple solution even without any "new releases". Grow up please ! Half of your clients uses IB and don't want to use older IB versions: it is about money after all !

    Regards

    Leave a comment:


  • HKinani
    replied
    IB Connection bypass version dependance

    Bypass the problem by configuring the IP setting of the NinjaTrader IB Connection with the IP of the machine. (instead of the local host 127.0.0.1). This will make a connection to the port without trying to start up TWS. Which wou will need to have up and running. Add the same IP to the Trusted IP Addresses in the API configuration or else accept the connection pop up from IB when NinjaTrader establishes a connection.

    By the way no need to set name and password.
    Last edited by HKinani; 08-11-2011, 04:29 PM.

    Leave a comment:

Latest Posts

Collapse

Topics Statistics Last Post
Started by CaptainJack, 05-29-2026, 05:09 AM
0 responses
365 views
0 likes
Last Post CaptainJack  
Started by CaptainJack, 05-29-2026, 12:02 AM
0 responses
236 views
0 likes
Last Post CaptainJack  
Started by charlesugo_1, 05-26-2026, 05:03 PM
0 responses
205 views
1 like
Last Post charlesugo_1  
Started by DannyP96, 05-18-2026, 02:38 PM
1 response
290 views
0 likes
Last Post NinjaTrader_ChelseaB  
Started by CarlTrading, 05-11-2026, 05:56 AM
0 responses
246 views
0 likes
Last Post CarlTrading  
Working...
X