IB TWS reconnect after router IP change?

Anyone know how to reconnect IB TWS to IB data farm server after router changes it's IP address?

If router changes its IP address while TWS is running, the connection to IB server is lost and TWS went all purple. I always have to close and restart TWS in order to re-connect to IB server.

However, I noticed that the moment that I click close buttun, TWS then briefly reconnect to IB server then shutdown. Apparently, there should be a way to reconnect TWS to IB server without restarting TWS.

Anyone has any idea?

 

there is a hotkey, dont remember and dont want to do your work, so study the Users guide

 

Typical useless ET response.

 

Check out this thread, third post by JackR.

http://www.elitetrader.com/vb/showt...426&highlight=Midnight+disconnect#post3054426

 

Thanks a lot. That's a great thread.

 

Just a few minutes ago. TWS went all purple again.

I tried CLTR-ALT-R, no effect.
Pressed CTRL-Alt-F, was disconnected right away.

Pressed CTRL-ALT-R again, no effect.

Had to shutdown then restart TWS.

 

I think the more important question is why is your router randomly changing its IP address?

 

I think it's the route from Los Angeles to NY is too far. And Verizon DSL network or the network out of Verizon is just not reliable.

This time it does not change IP.

The ping time from here to IB is already around 100ms-110ms if there is no network problem.

Like this.

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 23 ms 22 ms 10.35.120.1
3 22 ms 22 ms 23 ms P0-3.LSANCA-LCR-08.verizon-gni.net [130.81.193.1
6]
4 24 ms 24 ms 24 ms so-7-0-1-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.142]
5 24 ms 25 ms 24 ms 0.so-2-2-0.XL4.LAX15.ALTER.NET [152.63.10.121]
6 25 ms 77 ms 25 ms 0.ae4.BR3.LAX15.ALTER.NET [152.63.113.189]
7 25 ms 25 ms 25 ms 204.255.168.134
8 105 ms 105 ms 110 ms cr2.la2ca.ip.att.net [12.123.30.150]
9 110 ms 110 ms 110 ms cr1.slkut.ip.att.net [12.122.30.29]
10 111 ms 111 ms 111 ms cr2.dvmco.ip.att.net [12.122.30.26]
11 110 ms 110 ms 111 ms cr1.cgcil.ip.att.net [12.122.31.86]
12 104 ms 104 ms 104 ms cr2.cgcil.ip.att.net [12.122.2.54]
13 112 ms 111 ms 111 ms cr1.n54ny.ip.att.net [12.122.1.1]
14 104 ms 104 ms 104 ms cr83.n54ny.ip.att.net [12.122.105.50]
15 109 ms 108 ms 108 ms gar25.n54ny.ip.att.net [12.122.115.21]
16 104 ms 105 ms 105 ms 12.89.125.38
17 106 ms 111 ms 111 ms www.interactivebrokers.com [206.106.137.3]

Here you see that it adds 80ms just jumping from Verizon (ALTER.net is Verizon) to AT&T

 

Try getting a utility called pingplotter it aggregates pings over time, sometimes the link is fine and then every-now and then it drops packets but one successful ping will not show this.

 

This is interesting. I have a 3G modem connected to my router as a backup connection and whenever the main connection fails it automatically switches to the 3G modem.

Obviously the IP address would change during the failover and I never have to relogon to TWS. Everything went seemless: main connection fail -> fail over to 3G -> TWS went purple for a few seconds -> TWS purple went away and everything was fine again.

So in my case TWS handles IP address changes seemlessly.