Thanks for the tip, I'll get my hands on the WinSock error one way or the other. As I've said, I'm almost certain the message will be "time out" (or winsock-talk for time-out), and that's why this is worrying. I mostly feel bad because my application gets the blaim for something that's not its fault.
Thanks, Cosmin Prund Wilfried Mestdagh wrote: > Hello Cosmin, > > Just tried telnet.exe on a NT machine, and it does give you the winsock > error neather :( You mention ICS in a previous post. You can setup a > client using TWSocket to connect and display the winsock error in the > appropriate events (OnSessionConnected and OnSessionClosed) in minutes. > Knowing the winsock error is probably halfway ! > > Yes you correct. If the server listens on 0.0.0.0 it is listening on all > interfaces, so including all NIC. > > --- > Rgds, Wilfried > http://www.mestdagh.biz > > __________________________________________________ > Delphi-Talk mailing list -> Delphi-Talk@elists.org > http://www.elists.org/mailman/listinfo/delphi-talk > > __________________________________________________ Delphi-Talk mailing list -> Delphi-Talk@elists.org http://www.elists.org/mailman/listinfo/delphi-talk
