Newsgroups : Borland : borland.public.delphi.internet.winsock : 2006 Oct : Re: Very URGENT Indy 10 FTP re-post again for gambit
| Subject: | Re: Very URGENT Indy 10 FTP re-post again for gambit |
| Posted by: | "Remy Lebeau (TeamB)" (no.spam@no.spam.com) |
| Date: | Tue, 24 Oct 2006 10:25:39 |
"Jack MacRank" <jack@macrank.com> wrote in message
news:453e26fc$1@newsgroups.borland.com...
> When your app bombs out it will show you all traffic to and
> from IdFTP. That way you can actually see what is being
> transfered and why it's bombing out.
If the socket API socket(), bind(), or connect() function is the one who is
failing, then there will not be any traffic for Indy's logging components to
intercept. Indy's logging components can only log the data that Indy itself
reads/writes at a higher level. If connect() is the failing function, then
you would need to use a packet sniffer, such as Ethereal, to look at the raw
TCP traffic to see if the connection is even being attempted in the first
place.
Gambit
none