"Nindz Kornjaca" <nindzakornjaca@nil.ca> wrote in message
news:452da6eb@newsgroups.borland.com...
> Server IP is public.
> Client is behind a firewall (and proxy).
What kind of proxy are you using? If it supports the SOCKS protocol, then
you can attach a TIdSocksInfo to the TIdTCPClient. Then set the Host and
Port properties of the TIdTCPClient to the public IP/Port of the
TIdTCPServer, and set the Host/Port properties of the TIdSocksInfo to the
IP/Port of the proxy.
> To test it, I used firewall A on the server to trace all connection
requests
> and I can see on the server that TCPClient tried to establish connection.
> Firewall A let the
> request through (I opened the port).
Then the TIdTCPClient is waiting for a reply that is not being sent, or is
being blocked. That is the only way a timeout error can be occuring. Are
you receiving an EIdReadTimeout or EIdSocketError exception?
> In the morning, I start my home comp with TCPServer and public IP.
> I go to work, launch the TIdTCPClient and try to connect to the
> server--->Times out.
Please provide more details about what EXACTLY is happening.
Gambit
