如TWS登陆有问题 就用网络交易者

Discussion in 'Interactive Brokers(盈透)' started by weijian, Jun 12, 2008.

  1. 我为什么这么说?

    因为我的登陆服务器已从美国换到香港, 登陆连接一切正常,基本上不再出现粉红界面!
    接下来的问题就是出现问号的问题,也就是其中的譬如ushmds2a 历史数据, usfuture等的中断问题.

    从技术上说,听我直言, 这其实是软件工程师该思考的问题了!
    -----客户都已经正常登陆了IB的服务器,连接也非常正常, 可是其中部分服务器的连接老中断,why???
    -----有没有更好的方案??
    .......
     
  2. 问题不是你想的那么简单。用小软件连服务器,据说能“增加服务器压力”?我搞不懂中间的逻辑。
    我所能做的是拜托大家,网络连接不好的时候,尤其是香港时间,记得给香港客服打电话!!!不要沉默!他们也许觉得有电话记录就会真的有这样的问题
     
  3. 一个长治久安的办法是IB在中国大陆设一个具有高速出口的定向代理服务器,大陆客户可以选择通过这个代理服务器连接美国或香港的交易服务器。
     
  4. 首先,是要证实这个问题的存在,然后就可以投入资源了。就像我们成功争取香港服务器那样。
     
  5. 问题确实是存在!
    而且很严重!

    我昨天晚上一笔交易都没做!
    因为我在等着AB从IB的TWS取数据, 可是AB总在提示'历史数据是否连接...'!
    我昨天晚上就一直在等待取INDU, COMP, SPX, CL和ES等的数据,可是一直没取到完整的...
    AB只取到了小部分数据!:(

    然后是凌晨0:30,我决定放弃等待,睡觉先:)
     

  6. 众所周知,看电影,传图片对服务器的压力是很大的!

    土豆网在线看电影的人数至少也有几十万吧,也有可能最多有百万人级,

    IB的数据压力未必比这个大??!!

    “增加服务器压力”--一说,恐怕是软件工程师的托词!
     
  7. 我的服务器设为香港的,网通1M,没有断线,我建议各位照伟建兄说的做,基本可以解决断线问题
     
  8. 昨天晚上我耐心观察了一晚上,北京时间20:00-清晨1:00,基本上2-3分钟usfuture, ushmds2a中断一次,AB取不到完整的数据,只能取得一小部分数据.

    清晨1:00以后,一切正常了,AB也可以取得完整的数据.

    结论显然是与电信出口有关,哈:)

    可是难道与IB一点关系都没有么????
    IB的软件开发工程师,难道不应该有更好的数据连接加速方法么????
     
  9. 电信客服目前给我的解释是 网络国际出口是由国家安全局负责控制,所以他们也没办法!

    看来这个问题会悬很长一段时间了.....................
    看来网络中断要打持久战了:(.....................


    IB其实是可以有很好的解决办法的,
    譬如在HK增future历史行情服务器, 当TWS与美国那边的历史行情服务器不能正常通讯时, 便开始自动连接香港的服务器处理数据, 以保证客户TWS的数据总是源源不断....

    目前只能期待IB在这上面有点动作了:)
     
  10. 和METATRADER, ESIGNAL, TRADESTATION 比, IB 连接方面的问题是比较多,虽然后两者在中国的用户没有IB多,但是国内用METATRADER做外汇的人肯定比IB客户多,为什么很少听到METATRADER的用户反应行情中断的问题?

    IB 应该好好重视中国客户的呼声,硬件上该投入就投入,这些投资都会有回报的。
     
  11. 我需要数据。用数据说话,才有说服力。请大家提供数据,比如PING对比的METTRADER的服务器的数据,以及tracert路径的报告。也许需要重复上次咱们做的那些工作。
     
  12. 2008年6月14日18:32

    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=574ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=560ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=567ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=580ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=569ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=568ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=565ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=579ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=570ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=600ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=602ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=599ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=601ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=594ms TTL=107
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=586ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=579ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=593ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=590ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=583ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=592ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=592ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=597ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=585ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=586ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=586ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=597ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=588ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=579ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=590ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=584ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=562ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=565ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=565ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=561ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=580ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=580ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=567ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=563ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=563ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=562ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=564ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=567ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=559ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=569ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=567ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=568ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=574ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=566ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=562ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=555ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=554ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=566ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=579ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=564ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=568ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=567ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=580ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=571ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=571ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=574ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=563ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=565ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=566ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=565ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=568ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=565ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=563ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=564ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=558ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=555ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=553ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=554ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=550ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=551ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=547ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=556ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=555ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=551ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=560ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=566ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=555ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=559ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=560ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=564ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=557ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=566ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=557ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=543ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=544ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=534ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=545ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=543ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=540ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=542ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=549ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=551ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=554ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=548ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=553ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=547ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=559ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=557ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=566ms TTL=107
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=564ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=570ms TTL=107
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=570ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=588ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=590ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=583ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=586ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=588ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=570ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=571ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=564ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=569ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=584ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=588ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=590ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=583ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=579ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=580ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=574ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=589ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=585ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=590ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=594ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=591ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=595ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=596ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=588ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=583ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=568ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=569ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=574ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=588ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Request timed out.
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=589ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=580ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=586ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=587ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=591ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=591ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=586ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=578ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=577ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=570ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=583ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=580ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=582ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=585ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=579ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=569ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=575ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=559ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=556ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=558ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=564ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=568ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=559ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=561ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=574ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=602ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=588ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=596ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=586ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=581ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=574ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=572ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=567ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=573ms TTL=107
    Request timed out.
    Reply from 208.245.107.9: bytes=32 time=563ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=569ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=570ms TTL=107
    Reply from 208.245.107.9: bytes=32 time=576ms TTL=107
     
  13. 周日没交易, ping都如此:)

    对网络出口尤其是到美国出口的控制,我们的ZF是一贯的:)
     
  14. 我对专业的软件工程师说了一下目前的困境.
    他查了一下,分析了一下IB的TWS软件!
    他说IB是采取客户与数据服务器直接建立连接的方式,譬如和ustuture和ushmds2a直接建立连接,
    所以我的登陆服务器虽然从美国换到香港,但报价服务器依然要与美国那边的服务器相连,这种方法的弊端,就是目前我遭遇到的情况.

    其实IB有很多方法可以解决这个问题,
    1. 与美国报价服务器相连, 当出现问题,就与香港的备份报价服务器自动连接,这个方案需要在香港增加报价服务器.
    2. IB在香港服务器上建一个中转程序, 登陆到香港的客户查询美国的行情数据时,当TWS检测到客户与美国报价服务器网络不畅,就通过这个中转程序来转发数据,流程是香港中转程序把数据从美国服务器取得,然后分发到客户的TWS端,相当于在香港多一个中转站, 借道香港这样来避开了ZF对美国出口的控制....
    3. ......(留给大家来补充:) )
    ............

    4. 据有IT网络专业人士朋友的说法, 他说以上做法都需要修改软件,一下子又改不好软件.
    费力又花时间,短时间来说太麻烦.


    从网络工程师的地场来看,IB这个问题这不全是程序问题,至少有50%归属网络路由问题.
    他有一个'一二天就可以立即搞定的做法'.
    该网络工程师朋友说,"最简单的做法,就是在香港多增加一个路由服务器,让我们大陆的客户全部登陆,走这个路由."
    "你看, 你的登陆服务器从美国换成香港的服务器,登陆就一切OK"
    "那么现在的做法就是,把你全部的market data请求全部借道香港, 从这个新增加的路由服务器出口到美国,这不就解决了?!"
    -------呵呵,网络问题我不太懂,但好象听起来很解决问题哦:)


    5. ......(留给大家来补充:) )
    .
     
    Last edited by a moderator: Jun 15, 2008
  15. 是啊,为什么好象没听说MetaTrader用户反映行情问题呢?
    咱们部落也有几位TradeStation正式客户,如neo_cn,好象也没听说有行情中断问题。
     
  16. This is what happening to me. I live in ShenZhen and I am using Topways Cable. First time it happen was a month ago on a Friday. In the morning it was ok till 6:00pm. TWS start to have problem Logging in. I ping to the HK Server it was ok, but couldn't login. I keep on trying until 9:30pm went US markets open still couldn't do it. So I call the US call center, coz I thought someone might hack into my account. It was fine according to the guy on the phone. He said it should be my port 4000 that has the problem. The whole night I couldn't login but WebTrader is fine. On Monday next week everythings backs to normal until 1 week after the problem start again! This time it happens everyday start at 6:00pm. I couldn't login but ping to the server is ok. So, I call Topways Cable. They send someone to my house. The guy told me there is lots of people has this problem logon to web site and others that go outside China. It is due to the firewall setup by the government. The final fix was, they give me a software with password that route to other channel. The software is kind of like a VPN. It gives me a local address like 10.XXX.XXX.XXX. From there on, I been testing it for 2 weeks now, I still has a bit of problems disconnecting(There is more disconnecting on the last few days). It is workable but a bit scarey!

    I think the problem is due to the port 4000 on the old equipment they have in China on the route to HK. I don't think the server has been block by the government's firewall. If it is block you wouldn't be able to logon once a while. US server goes out with a different route(Trunk), that is why US server is a bit better. TWS only use port 4000 to connect and there is more and more IB user these days in China. I think their equipment handle this unusual port 4000 a little differently than the usual ones and all IB user lately are jamming this port 4000. It makes the old equipment they have become very unstable. This Trunk connect to HK could be very small, the whole China could be just sharing one very small channel to HK coz most of the HK site is block and the equipment handle the traffic is very minimal.

    There is some quick fix to the problem like open different ports for TWS to login, let the China equipment sharing some of the traffic with different ports. Or give us connection to a VPN in China to a VPN in HK and then logon to the HK server. There is lots of company provide dedicated VPN Line to HK in China. It is very doable for IB to implement to the TWS Network.

    But for the long run it is better for IB to setup a China Server. China is a huge market to IB. This is what they should do but will they be able to do it in China? That is another story.

    Due to the problem mostly happen after 6:00pm(lately in the afternoon also).
    It is not easy for some of people here to call your office.

    If what I suspect is right. This problem will get worst and worst in a very rapid rate. Specially, if you get more and more customers. IB should look into this problem very seriously.

    weijian, I hope you can help us push this forward to your company. This means a lot to us!

    If you need any help let me know!

    Thanks in advance!
     
    Last edited by a moderator: Jun 15, 2008

  17. 那确实!

    下午17:00以后, 你们的香港HK客服人员都下班了,怎么CALL?

    何况这问题,他们就算在听电话,也无法直接解决掉, 只是多一条电话记录:)

    一般情况,客户碰上需要立即解决的问题,才会打电话.何况打香港也算是国际长途,打起来总不顺手.假若IB是国内的公司,出现这样的问题,我可以保证你的电话会被打爆!:)

    象这种断断续续的问题, 仿佛人得了慢性病也不会马上求医生:),客户也不会常打电话的.
    不很恰当的比方:)
     
    Last edited by a moderator: Jun 15, 2008
  18. 我是福建的,电信宽带,ib开户,登录服务器由美国转到香港。
    最近也出现大家说的数据中断问题,我主要看外汇,时红时绿,很严重(好像却可以交易,但是看不到行情数据怎么敢交易?)
    我开ib的户有一年了,目前在手动交易,但主要目的还是做系统自动交易(开发中),这种情况怎么能自动交易?悲哀郁闷。早知道ib行情这样。。。。。唉
    话又说回来,除了ib行情这样(开户一年来,这种时断时续的情况经常发生),其它我都满意,希望ib能够把这个问题彻底解决!!
    如果weijian需要我提供数据,能否告诉方法、详细步骤、以及数据格式或形式,麻烦weijian啦!
     
  19. 下单和行情数据连接的问题确实存在,在某段时间也很严重,伟建应该重视起来,并抓紧去推动解决,在国内建服务器是很好的办法,不行应该租用专用线路来解决。效率应该快一点,没有的事情客户是不会频繁反映的。在此感谢伟建为此付出的努力!
     

  20. 4. 据有IT网络专业人士朋友的说法, 他说以上做法都需要修改软件,一下子又改不好软件.
    费力又花时间,短时间来说太麻烦.


    从网络工程师的地场来看,IB这个问题这不全是程序问题,至少有50%归属网络路由问题.
    他有一个'一二天就可以立即搞定的做法'.
    该网络工程师朋友说,"最简单的做法,就是在香港多增加一个路由服务器,让我们大陆的客户全部登陆,走这个路由."
    "你看, 你的登陆服务器从美国换成香港的服务器,登陆就一切OK"
    "那么现在的做法就是,把你全部的market data请求全部借道香港, 从这个新增加的路由服务器出口到美国,这不就解决了?!"
    -------呵呵,网络问题我不太懂,但好象听起来很解决问题哦:)


    5. ......(留给大家来补充:) )