|
Symptom
|
Resolution
|
| When you logon to RealTick® you receive a "No Accounts Available" message. |
This message could mean one of two things, either your account has not been configured properly, or your router or firewall has not been configured to connect to the machine where your account resides.
|
| You receive an "Invalid username, password, domain" message. |
Check that you've entered your password in the correct case. Usernames and domain names are always all uppercase (capital letters), but passwords are case sensitive. |
| You receive a message saying "Connecting to sbperms**" when you attempt to log on, and the message never disappears. |
This message indicates that RealTick has made its first connection, but is unable to make its second one. Check all local physical connections before proceeding with the diagnostics below. |
| Check whether you can telnet://63.75.60.224:1723. If not, try to telnet://63.75.60.224:1838. If you can reach 1838 but not 1723, you must create a new line in the [TALIPC] section of the TAL.INI. The line reads: |
| UseNewPort=Y |
|
If you are using SOCKS to access high TCP ports, you must create a new line in the [TALIPC] section of the TAL.INI that specifies the IP and port for your Socks Server. The line reads:
|
|
SocksServer = your socks IP:Socks port (usually 1080)
Example: SocksServer = 208.208.208.208:1080
|
| You receive a PERMS URL PROBLEM message when you attempt to log on to RealTick. |
Frame Relay Connection
1. Verify that the firewall is configured properly to connect to the correct networks and ports. Verify that all static routes are built on your LAN. RealTick connects to outgoing TCP ports 1723-1743, the return connection is on random ports.
|
|
2. If you are using a proxy server, RealTick is proxy aware only if you are connecting on port 80. If you are not connecting on port 80, you must create a new line in the [PERMCACHE] section of the TAL.INI that will specify the IP and Port of your proxy. The line reads:
|
|
proxyserver = your proxy IP:Proxy port (usually 80, 8080, or 8888)
Example: Proxyserver = 10.129.38.10:8080
|
|
3. Verify that your DNS server is able to resolve tal.taltrade.com to 198.207.140.200.
|
| This server provides the initial handshake between the client and the NYSE Arca network. If you are not using DNS you must set your domain's scriptfile to refer to all NYSE Arca servers by IP address. |
|
4. For testing purposes, try running RealTick outside the firewall. This will narrow the problem down to your firewall.
|
| When you are ready to test you can ping and tracert to beacon.taltrade.com or simply log on to RealTick. |
|
Internet
All of the suggestions listed above can also be applied to an Internet connection. However, this message may also reflect a problem with your Internet connection or a routing issue. If you have followed the instructions above and still see the problem, try these additional steps:
|
| 1. Check your Internet connection for trouble. |
| 2. Verify that your firewall is configured to connect to ports 1723-1743 on the correct network. |
| 3. Verify that the workstation knows to route over the Internet. Use the "Add route" command through the DOS prompt to point it to the Internet. |
