The Login box includes the checkbox Use/store settings on server. Check this box to have TWS automatically save any session changes to the server, and use that saved version the next time you log in from any PC.
If you are not yet our customer, email us at helpdesk@colsecurities.com.hk to request for a TWS demo. If you are our customer, you can open a paper trading account, which allows you to use the full range of trading facilities in a simulatedd environment using real market conditions.
The nightly log off is required for maintenance and cannot be disabled. However, you can modify the log off time from the Lock and Exit page of Global Configuration.
You need to set the timing to "Allow order to be activated, triggered or filled outside of regular trading hours." You can define this seting from the Timing section of the Order Preset for a specific asset type, or on a per-order basis from the Time in Force field checkbox "Fill outside RTH.". If outside regular trading hours is not available for the specific order you are submitting, you will not be allowed to populate the checkbox.
You can record mouse-click shortcuts for specific order creation and transmission commands, such as buy, sell, transmit and cancel and many others.
The TWS settings file is named tws.xml and is located in a subdirectory of c:\Jts. Search (CTRL F) the c:\Jts directory for the most recently modified file. TWS Log files are named log.day.txt (e.g., log.Wed.txt) and are located in the c:\Jts directory.
TWS runs on Windows, MAC and Unix operating systems. To ensure that you have an adequate Internet connection and proper system requirements to run TWS, please see the Minimum Requirements details,
The table below outlines our suggestions for both minimum and recommended system requirements to run the COL Global Access Trader WorkstationSM.
If you have a slower computer or Internet connection, we recommend that you use the standalone version of TWS.
If you use the browser-based version, you can access TWS from any internet PC, and do not have to manually update to get the latest version. Both require that you install the minimum recommended version of Java.
A. Your Internet connection may drop off due to connectivity or Internet Service Provider (ISP)-based issues.
B. This problem has also been known to occur with problematic Ethernet cards.
This may be due to a corrupted or improper install of TWS or the Java Applet.
Outdated or corrupted browsers can cause this to occur. Please upgrade or uninstall if necessary.
Or, your browser display settings may be preventing you from viewing the entire screen.
Your browser's cache may have a problematic page stored in it.
Dial-in customers or customers with a poor connection may periodically experience problems loading an applet through a browser. Browser download and installation of applets tend to stall on slower connections.
This typically occurs if:
Your ports are being blocked by either:
This may happen for a variety of reasons. Try the following:
This may happen for a couple of reasons. Try the following:
This may be the result of a problematic Ethernet card, or improper driver installation of display adapters. Download the latest version of your video drivers. You may have other PC problems which require immediate attention by an authorized PC technician.
Depending on the amount of data you are receiving (number of ticker symbols entered) most TWS sessions will function properly on a reliable 56k connection. However, the use of other network applications while you are using TWS may slow down your connection. The typical TWS client will utilize 6.5k/second to retrieve market data for 100 symbols of data.
TWS does not use any UDP.
TWS will function in a shared environment, provided that a reliable connection exists. The connection that a TWS machine receives must have sufficient bandwidth to operate. Users should take care when using NAT (Network Address Translation) and DHCP. While TWS will work if NAT and/or DHCP are configured properly, data loss and unpredictable behavior can result from improper configurations. For more information on NAT and DHCP, review the section below on those topics.
There are many types of broadband available. Cable, xDSL, Corporate Networks (T1, T3, Frac-T), Dial-on-demand ISDN and Satellite are all broadband solutions. All of these services provide much higher throughput (compared to a dial-in line) and typically use routers or special modems to become part of a hardwired network. Some services emulate this method rather than actually performing this way. Availability of different services may be limited in certain areas; contact vendors in your area for a list of available services.
TWS connects to our servers via ports 4000 and 4001; it will not function on any other port. To use TWS from behind a firewall, users should download the standalone version, and will be prompted during installation to specify proxy settings that will be used by TWS for all http requests.
Testing with these systems has proved inconclusive. Some satellite providers list trading software (or anything that requires a reliable connection) as an "at your own risk" practice. Customer feedback has indicated that satellite services are sometimes unreliable.
As with any type of connection, be sure the provider allows TCP/IP routing with open access to Internet service ports. TWS connects to our servers via port 4000 using a source port in the publicly addressable space above port 1024. Our servers listen on port 4000; it will not function on any other port. For users behind firewalls, the installed version of TWS includes provisions for using a specified outbound port.
Extraneous network adapters and drivers which are not connected, are inoperative or unnecessary should be removed from your system. These can cause unpredictable network behavior.
Important: If you are not sure about any of the adapters in your Network settings, consult your network administrator before removing them.
Latency due to physical distance from your ISP, routing within your ISP's network, packet loss and many other factors can affect the reliable operation of your TWS. Please review the connectivity troubleshooting tips below to test the quality of your connection.
The Ping command will test the quality and latency of your connection. If it shows 4 round-trip reports without a reply (does not say not found, timed out, etc.) your connection is healthy. To use this, type ping tws.colsecurities.com.hk at the command prompt. A healthy ping should look as follows:
Pinging gw1.ibllc.com [208.245.107.3] with 32 bytes of data:
Reply from 208.245.107.3: bytes=32 time<10ms TTL=254
Reply from 208.245.107.3: bytes=32 time<10ms TTL=254
Reply from 208.245.107.3: bytes=32 time<10ms TTL=254
Reply from 208.245.107.3: bytes=32 time<10ms TTL=254
If the ping results show excessive latency (>500ms), timeouts/packet loss, or no replies, a network problem exists between you and the TWS network.
The tracert command is used to isolate routing issues. This will show you all of the "hops" from your connection to our network. A timeout, indicated by "*" or time above 200, indicates a slow or dead hop and may be a problem. Over 15 hops can also be a problem.
To look at a traceroute, type tracert tws.colsecurities.com.hk at the command prompt.
The following are sample traceroutes. Included is an explanation and suggested course of action. This traceroute is an example of a healthy connection. The ping times and the number of hops are low (lower is better). No course of action required.
1 gatekeeper (206.42.160.1) 1 ms 1 ms 2 ms
2 jfk-edge-19.inet.qwest.net (63.237.128.53) 19 ms 26 ms 21 ms
3 jfk-core-03.inet.qwest.net (205.171.30.189) 22 ms 19 ms 24 ms
4 ewr-core-03.inet.qwest.net (205.171.5.89) 20 ms 19 ms 20 ms
5 ewr-brdr-01.inet.qwest.net (205.171.17.98) 20 ms 26 ms 19 ms
6 205.171.1.122 (205.171.1.122) 30 ms 20 ms 22 ms
7 sl-bb23-nyc-3-0.sprintlink.net (144.232.7.109) 20 ms 19 ms 19 ms
8 sl-bb22-pen-6-0.sprintlink.net (144.232.9.18) 25 ms 37 ms 21 ms
9 sl-bb26-pen-9-0.sprintlink.net (144.232.16.58) 21 ms 26 ms 22 ms
10 sl-gw26-pen-4-0-0.sprintlink.net (144.232.5.190) 24 ms 23 ms 24 ms
11 sl-thllc-4-0-0.sprintlink.net (144.232.190.222) 35 ms 31 ms 29 ms
12 206.106.137.111 (206.106.137.111) 28 ms 28 ms 30 ms
This is an example of a marginal connection. The ping times and number of hops are fairly high, but the connection should still be usable. Contact your ISP to see if this is a common occurrence. If this is what you can expect, you may want to shop around for another provider. Higher times indicate line latency (slowness) and the high (17) number of 'hops' results in a higher potential for outage, in the event that one of the providers involved experiences a problem.
1 195.130.108.1 (195.130.108.1) 3.258 ms 2.325 ms 2.32 ms
2 athens-teiath-ATM.grnet.gr (194.177.209.149) 3.894 ms 3.546 ms 2.935 ms
3 athens-2-athens.grnet.gr (194.177.210.226) 3.299 ms 4.549 ms 13.643 ms
4 grnet1.uk1.uk.geant.net (62.40.103.181) 78.624 ms 72.213 ms 73.457 ms
5 uk.se1.se.geant.net (62.40.96.125) 104.912 ms 105.978 ms 104.695 ms
6 so-6-0-0.ar2.CPH1.gblx.net (208.48.23.153) 142.148 ms 115.03 ms 114.235 ms
7 so2-1-0-622M.cr2.CPH1.gblx.net (62.12.32.77) 113.658 ms 116.135 ms 114.903 ms
8 pos1-0-2488M.cr2.LON3.gblx.net (195.8.96.181) 134.768 ms 138.151 ms 132.05 ms
9 pos1-0-622M.br1.LON3.gblx.net (195.8.96.189) 130.876 ms 131.726 ms 134.405 ms
10 sl-bb21-lon-5-0.sprintlink.net (213.206.131.25) 132.904 ms 131.369 ms 134.111 ms
11 sl-bb20-msq-10-0.sprintlink.net (144.232.19.69) 209.434 ms 212.069 ms 209.79 ms
12 sl-bb20-nyc-11-3.sprintlink.net (144.232.9.102) 215.735 ms 208.302 ms 207.316 ms
13 sl-bb20-pen-10-0.sprintlink.net (144.232.18.37) 400.633 ms 352.33 ms 274.419 ms
14 sl-bb25-pen-8-0.sprintlink.net (144.232.5.174) 212.023 ms 215.237 ms 215.472 ms
15 sl-gw26-pen-0-0-0.sprintlink.net (144.232.5.186) 213.755 ms 212.104 ms 211.378 ms
16 sl-thllc-4-0-0.sprintlink.net (144.232.190.222) 218.742 ms 221.021 ms 217.51 ms
17 206.106.137.111 (206.106.137.111) 218.028 ms 222.549 ms 218.867 ms
The next example shows a network outage. The connection fails between hop 8 and 9. In the event that this occurs, you should contact your ISP and give them this information. These types of outages are very obvious and are the easiest for an ISP to troubleshoot.
1 kauge.aso.ee
(195.80.96.219) 0.432 ms 0.323 ms 0.357 ms
2 uninet-gw.aso.ee (195.80.96.211) 1.094 ms 7.688 ms 2.332 ms
3 194.204.4.161 (194.204.4.161) 1.489 ms 1.403 ms 1.425 ms
4 kista-atm.uninet.ee (193.229.72.105) 135.413 ms 129.594 ms 136.073 ms
5 Pos5-0.GW7.STK3.ALTER.NET (146.188.34.13) 141.723 ms 140.031 ms 122.782 ms
6 so-3-0-0.XR2.STK3.Alter.Net (146.188.5.37) 113.354 ms 98.346 ms 90.857 ms
7 ge-1-0-0.TR1.STK2.Alter.Net (146.188.11.242) 94.762 ms 115.168 ms 130.034 ms
8 so-4-0-0.IR1.DCA4.Alter.Net (146.188.5.197) 257.747 ms 288.965 ms 255.057 ms
9 request timed out * * *
10 request
timed out * * *
11 request
timed out * * *
12
request timed out * * *
The last example is possibly the hardest to troubleshoot and the most frustrating. The occasional timeout (marked with *s) appears several places in the traceroute. This indicates that intermittent packet loss is taking place. These types of errors are elusive and may not have been reported yet. Contact your ISP about this issue.
1 <10 ms <10 ms 10 ms 206.106.137.1
2 <10 ms 10 ms 10 ms sl-gw26-pen-5-0-1.sprintlink.net [144.232.190.21]
3 <10 ms 10 ms <10 ms sl-bb25-pen-0-7.sprintlink.net [144.232.5.185]
4 <10 ms * <10 ms sl-bb21-pen-8-0.sprintlink.net [144.232.5.237]
5 <10 ms 10 ms 10 ms sl-bb23-rly-0-0.sprintlink.net [144.232.20.32]
6 10 ms 10 ms * 144.232.20.44
7 10 ms 10 ms 10 ms sl-ameronl-14-0.sprintlink.net [144.223.246.14]
8 10 ms 10 ms 10 ms bb1-ash-P1-0.atdn.net [66.185.139.209]
9 10 ms 10 ms 10 ms bb1-dtc-P0-2.atdn.net [66.185.152.114]
10 10 ms 10 ms 10 ms pop1-dtc-P14-0.atdn.net [66.185.140.6]
11 * 10 ms 10 ms ow3-dtc-P0-0.atdn.net [66.185.144.254]
12 10 ms 10 ms 10 ms ow1-dtc-P9-2.aol.com [205.188.131.218]
13 10 ms 10 ms 10 ms www2-dr6-P0-0.aol.com [205.188.172.126]
14 * * * Request timed out.
Create a snapshot of your computer screen and e-mail it to COLHK.
Name and save the file, and send it to helpdesk@colsecurities.com.hk as an attachment, along with a detailed verbal description of your support issue.
Try logging in and testing with another computer that you know works (with the same account) to see if the problem is the same on both computers.
If you have multiple Accounts, try another one of your accounts on your machine. If you don't have a second account, try using our demo system, or having a friend try their account on your machine will help to determine if there is a common issue among accounts (or systems) and where that problem may be.
Trying both systems may indicate that the problem is with a component installed on your computer or somewhere else.
To open the Control Panel, click Start, then select Settings>Control Panel.
With Windows XP, click Start>Control Panel.
Depending on the version of Windows you are using, its appearance may vary slightly from what we describe.
If you need to uninstall software, you should only do it from Add/Remove Programs window accessible from the Control Panel. Use this window to remove Trader Workstation or Java, or to repair your browser. When you uninstall a program, you will usually get a confirmation message ensuring that you do indeed want to remove the item that you have selected.
Note: Java does not support automatic upgrades. Before you upgrade Java, you must uninstall the current version.
Whether you're downloading an encryption upgrade, a new browser or a service pack, all official Windows upgrades can be acquired from http://windowsupdate.microsoft.com/, shown above. Click on the "products update" link on the left-hand side, select the updates you wish to install, and follow the instructions.
Note: If you are running a non US-English version of Windows, you need to install the international plug-in.
Be aware of the protocols and network devices that may affect you. The following is information about your TWS connection that you or your Network Administrator will want to know when troubleshooting your connection to us.
DHCP (Dynamic Host Configuration Protocol) is a way of automatically assigning IP addresses. If your DHCP server is assigning a private address (addresses which are not associated with the Internet) the server may be doing NAT (Network Address Translation) to get to the outside Internet Depending on the particular configuration, the router or server may be trapping requests from our server to your computer.
TCP/IP is the basic protocol from an Internet service provider. This, along with DNS (Dynamic Name System) and basic socket access are all that is required for a "functioning Internet connection" and for running TWS software.
NAT (Network Address Translation) is one of the basic components behind home routers (and some professional private routers). Done properly this should be transparent; the address on the outside should translate to your internal (non-Internet) addresses without your PC knowing the specifics of the routing.
Terms and Conditions Risk Disclosures Client Agreement
COL Global Access is a registered trademark for the service offered by COL Securities (HK) Limited a limited liability company incorporated in Hong Kong and licensed in the regulated activity of Securities Dealing AHF149.