![]() |
Connect FailSolutions To Connection Fail |
This is a sample connect fail message:
Please wait: Resolving to IP Address...
204.71.200.245 is online.
Connecting.....
Connecting: retry with remote port 101
Connecting: retry with remote port 102
Connecting: retry with remote port 103
Connecting: retry with remote port 104
Connecting: retry with remote port 105
Fail to connect to <204.71.200.245 : Port 100 -- 105>
Possible Error(s): Invalid Remote Port Address OR Remote user is not in Ready mode
For the common error case, you may have problem of "Connecting......"
Even If you set the valid remote address and remote port, it may need to take a few seconds to connect successfully.
Invalid Remote Port
By default, the Port is 100 (also based on the setting in Property). After you are sure you set the valid Port for connecting, you may still have problem to connect. It may happen if remote x Chat had an unsuccessful connection before and the the original port address is closed. Remote x Chat may set the port address to another one after it detect an error of the original port.
If this is the case, your x Chat will keep trying with the same port for a period (based on the setting in Connect Timeout ). Then, x Chat will try the next 5 ports to connect again until it fails.
Respond Idle Time Too Short
If this is not the case, remote user is really using the same port address. Then, you may have unmatched connection speed. Try to slower the Respond Idle Time [Options - Advanced] to try again.
Remote User Making Connection At The Same Time
There is another case of causing error not related to your and remote setting. When you are connecting to remote user and remote user is connecting to you or someone else, you may have to wait and try again.