"Your session was closed. Exchange regulations forbid using same username from multiple places" after running two instances on the same PC?

[Glefdar]

One of my two TOS instances was disconnected with this error message this morning. Both are being run on the same machine, installed into two separate directories on the same C: drive. So I don't understand how this error message occurred. Should I be worried that my TD Ameritrade account was hacked and someone logged into it from another IP address? But in that case, why would one of my two TOS instances be closed, instead of both of them? Logically it seems like both would be closed since if a hacker had obtained my password and logged in, that would mean three instances were running. Has anyone had this error message occur before with seemingly no explanation? It also worries me that this happened because what if it happened while I was scalping during a live trade? Could result in significant losses to be disconnected like that. I will note that the weather where I am is bad and there is a storm here, maybe that affected my internet connection? I don't see how that could affect this, since my internet was working the whole time this happened and only one of the two instances was disconnected with the error message, but maybe it's related.

 

[howsdiswork]

assuming your MAC has one and only one network connection, hardwired or wireless, only one IP address would be used. You sure you weren't also logged into ToS with your phone when this happened?

It should be easy enough to reproduce in any case, can you do it again on this machine?

 

[Glefdar]

assuming your MAC has one and only one network connection, hardwired or wireless, only one IP address would be used. You sure you weren't also logged into ToS with your phone when this happened?

It should be easy enough to reproduce in any case, can you do it again on this machine?

I actually don't have ToS installed on my phone. I still have no idea how this could have occurred if my account password hasn't been compromised.

 

[wherelambo]

It happens to me when I’m logged in on my desktop and then log in on my laptop which connects to wifi instead of the hard wire that my desktop is connected to.

 

[MerryDay]

ToS Support has stated that this error can occur when:

If the system goes to sleep, the session can stay connected, upon wake-up it can create another session.

 

[Glefdar]

That's interesting, thanks for sharing. I can't recall if my system had entered sleep mode briefly and that was what happened in this case but I'll keep it in mind to disable sleep mode entirely during trading hours.

 

[JoeDV]

One of my two TOS instances was disconnected with this error message this morning. Both are being run on the same machine, installed into two separate directories on the same C: drive. ...

I had the same issue because I completely forgot that one of my computers was running a vpn for work (and yes, I have TOS running there too lol), so it was reporting it as coming from another location and would logout my personal pc every now and then.