Re: Connection Lock-Down in Indy10 with D7 on Windows XP SP1

Giganews Newsgroups
Subject: Re: Connection Lock-Down in Indy10 with D7 on Windows XP SP1
Posted by:  Thorsten K (thorstenklamm…@gmx.net)
Date: Tue, 18 Jan 2005

Nobody any ideas?

I don't know, but for my simple mind the code looks as if it _should_ work
and in fact it does for localhost. My problem now is to find out where the
problem lies - is it just working for localhost because of a bug in
conjunction with the local loopback or is it not working because of a bug in
conjuction with the ethernet connection between my two test-computers? So
does anybody have a clue whether the code is supposed to work? Or has
someone some free time to test it on a different machine? On one machine
simply drop an IdTCPServer on a form, copy the code to the onexecute event,
set the default port to 1500 and active to true... And on the other machine
drop an IdTCPClient and a button, copy the button code to the click event,
set the port to 1500 and the host property to the ip/name of the server.
Then click the button and watch your network traffic - if the connection
persists and data is transferred, the code works... Takes just 2-3minutes...

Thx ahead,

Thorsten

Replies

None

In response to

Connection Lock-Down in Indy10 with D7 on Windows XP SP1 posted by Thorsten K on Mon, 17 Jan 2005