Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

unable to connect

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

    unable to connect

    Hello,

    I am unable to connect (with Continuum). My version is 8.0.28.0 but it says gateway timeout or network connection to login system is unavailable.

    How can I solve this issue?

    Thank you.
    Last edited by Kaldo; 06-23-2023, 01:43 AM.

    #2
    I have the same issue since today (can not connect with Continuum) - I have now upgraded Version 8.1.1.6 -> 8.1.1.7 and still get the error message "unable to connect to the remote server" (Logon failed)
    I did not change anything related to my account or user credentials.
    Last edited by hgreschi; 06-23-2023, 02:54 AM.

    Comment


      #3
      Hello,
      Thank you for your post.

      I've detailed a few general network troubleshooting steps below that may resolve this error for you (test for the issue after each step):

      • Restart NinjaTrader 8
      • Restart your PC
      • Restart your modem/router
      Ensure that all available updates for your PC are installed from the Windows Settings > Update and Security page. Be sure to close NinjaTrader and restart your computer after any updates are installed.
      • Disconnect and reconnect to your network
      • Disable your VPN service (if applicable)
      • Clear your DNS: Open the Command Prompt > run the command ipconfig /flushdns
      • Ensure that you have the Documents\NinjaTrader 8 folder on the list of exceptions for your firewall, antivirus, or backup programs and software
      • If possible, try running your computer directly to your router/modem using an ethernet cable, or vise versa, through a WiFi connection if already hard-wired in

      ​If you continue to experience the same, please email us your log and trace files right form the NinjaTrader platform (Help-> Email Support).Ensuring 'Log and Trace Files' is checked will include these files.
      Thank you!

      Comment


        #4
        This is the standard response, which really is not fixing the problem. I have been successfully logging in for six years and something changed recently. My Windows Defender is off and am using Trend Micro. What WORKS is restarting the computer then starting NinjaTrader before everything is fully up.

        This is not a general networking problem it is something which appears to have changed in either Windows updates or Ninjatrader that causes this problem. Am using latest Ninjatrader.

        As stated the connections will work while the computer is starting, but not once the computer is fully up. The Ninjatrader image is in the apps list to ignore and all the firewalls in Windows Defender are turned off.

        Comment


          #5
          Hello,
          Thank you for your post.

          Please email us your log and trace files right from the NinjaTrader platform (by going to Help-> Email Support), so we may look into what occurred. Ensuring 'Log and Trace Files' is checked will include these files.

          Thank you!​​​

          Comment


            #6
            I have looked at the trace and log files and done more playing around. The problem is generic socket timeouts trying to open connections. This is to at least three different destinations and results in varied error messages about Login or Metadata or other. The trace and log do not easily show the host names, the host lookup IP or the Port which is used for the connection. I did see one port think 31586 which setup rules for inbound/outbound but the behavior continues to be intermittent.

            Was able to have Windows Defender firewalls on and Trend Micro running fine and connect about four times before things failed. Then they consistently failed with one of three timeouts.

            Forty years ago I flew from LA to Austria to fix a problem, which ended up looking at binary of executable to determine. The directory name was off by one character and thus the software failed with no error message when the developer could have spent three minutes to put in an error message and saved my company a lot of money.

            With Ninjatrader it opens multiple host / socket connections but does it totally behind the scenes, and even the debug logs are not very clear. It would take about a day to put up a dialog showing the connections being made and when success or failure is completed. Otherwise the tech support people are going to look at hundreds of these log files and tell everyone to go through a litany of "reinstall everything and reboot everything" which is not needed. This is something going on with the socket TCP connections in probably most all the cases, either a hostname that is incorrect or some port that is not being allowed. The security software might also intercede but a dialog showing ongoing connection progress/failure is sorely needed IMHO.

            My first Windows program was a network sniffer for X windows and have programmed massive amounts of socket code in the past thirty years. I switched to augmenting NT after retiring software that networked five computers together doing socket connections for trading - custom messaging. Just saying this so you realize have experience.

            The inability to connect might be external to Ninjatrader and be something in the firewalls, but presenting the information which shows exactly what fails w/o log/trace files should be done.

            Comment


              #7
              In my case this apparently is bad DNS information which is used along the way. My guess is stale information left in a table somewhere on an old server, but that is just a guess.

              I've interacted with the Tech Support people at NT and suggested this is the case and the way to clean up the connection problems which are coming from their support servers or the NT servers themselves. Hopefully at some point their software initialization will be augmented to give feedback to make failure conditions easier to track down.

              In the meantime when starting NT now use a command.com batch file to cleanout DNS and it appears to be working.

              StartNT.bat:

              echo starting....
              ipconfig /flushdns
              "C:\Program Files\NinjaTrader 8\bin\NinjaTrader.exe"


              If I rebooted the computer the DNS info would flush so startup worked for a time. Not sure exactly how/why the info gets corrupted once loaded but it you are having issues this might also be a solution until a better fix arrives.


              Comment

              Latest Posts

              Collapse

              Topics Statistics Last Post
              Started by argusthome, 03-08-2026, 10:06 AM
              0 responses
              111 views
              0 likes
              Last Post argusthome  
              Started by NabilKhattabi, 03-06-2026, 11:18 AM
              0 responses
              60 views
              0 likes
              Last Post NabilKhattabi  
              Started by Deep42, 03-06-2026, 12:28 AM
              0 responses
              38 views
              0 likes
              Last Post Deep42
              by Deep42
               
              Started by TheRealMorford, 03-05-2026, 06:15 PM
              0 responses
              43 views
              0 likes
              Last Post TheRealMorford  
              Started by Mindset, 02-28-2026, 06:16 AM
              0 responses
              79 views
              0 likes
              Last Post Mindset
              by Mindset
               
              Working...
              X