Can't connect to Aptafund:
Getting disconnected from Aptafund or running slow:
Aptafund uses a system called Terminal Services from Microsoft.
The server end is running on Windows Server 2003 Terminal Server and your client, which is an Active X control; is version number 5.2.3790.
I. In order for a connection to be made, the client attempts to contact the server on TCP port 3389. If this is not being allowed by a firewall or proxy, connecting to Aptafund or any other Terminal Server will fail.
If you or you network administrator need to add a firewall exception, it is TCP port 3389 to 206.191.35.4 (aptafund.harriscomputer.com)
II. Please keep in mind that connections can be denied by PERSONAL firewalls as well. Black Ice, Symantec Firewall, Zone Alarm and the like can prevent you from making this connection. In order to test, please shut down ANY firewalling service on your computer. If you are now able to connect, then most personal firewalls allow you to make exceptions. Read the documentation that came with your product.
III. It is possible that Internet Explorer or some other service is preventing the RDC Active X control from running. In order to test, you can use the built-in RDC in Windows XP. This is a stand-alone Remote Desktop Client separate from Internet Explorer that can also be used to connect to Aptafund.
This program is found under the START menu > All Programs OR Programs > Accessories > Remote Desktop Connection.
Once this is open, the field is asking what address to connect to, enter aptafund.harriscomputer.com
If this does connect, then the Active X control is prohibited from running or is not installed properly.
Terminal Services operates on TCP sockets to communicate with clients over the Internet.
The way that this differs from other services such as mail and web browsing, is that it is a real-time socket. In other words, the data being sent between the server and client is in real-time and thus must arrive at it's destination in order for the conversation to continue. Any significant interruption in this conversation, and the result is a disconnect.
Aptafund servers are set to automatically log off a user that has been idle for 5 hours. The servers are also setup to attempt to re-connect a disconnected session. The servers are constantly being monitored and although rare, disconnects as a result of our Datacenter Internet connection are possible. However, the vast majority of disconnects are going to happen near your network or even on your network.
Use this connection page to troubleshoot disconnects:
http://online.aptafund.com/rdp-connect-reperr/
This connection page has extra error reporting enabled, to better understand what may be causing the disconnects. Report any error you get to AptaFund Support.
I. The most common cause of disconnects results from a poor Internet connection. If the Internet connection in which you are relying on is experiencing drop packets, faults or the like - then a disconnect will result.
Most network administrators have the ability to check their network equipment for any problems that may exist. In most cases, the disconnects occur at the gateway router for an organization. Typically, this is the busiest piece of a equipment in the network and the first place to look for a possible problem. A sample output from a Cisco router is shown below, highlighting the critical information.
{---sample output---
Serial0 is up, line protocol is up
Hardware is HD64570 with FT1 CSU/DSU
Internet address is 10.10.10.1/30
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 4/255
Encapsulation PPP, loopback not set, keepalive set (10 sec)
LCP Open
Open: IPCP
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 8949 drops; input queue 0/75, 146 drops
5 minute input rate 299000 bits/sec, 39 packets/sec
5 minute output rate 25000 bits/sec, 33 packets/sec
26375072 packets input, 4224651253 bytes, 74 no buffer
Received 26375072 broadcasts, 0 runts, 0 giants, 0 throttles
19 input errors, 11 CRC, 1 frame, 4 overrun, 4 ignored, 1 abort
21855895 packets output, 3413415872 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
---sample output---}
If you are still having trouble,
Please contact Apta Software Support at support@aptasoft.com
or (toll-free) 1-888-949-APTA x146.
