Newsgroups : Borland : borland.public.delphi.internet.winsock : 2005 Jul : Problem in a Clien/Server with Indy

www.cryer.info
Managed Newsgroup Archive

Problem in a Clien/Server with Indy

Subject:Problem in a Clien/Server with Indy
Posted by:"Cristian Zujew" (cazuj..@ing.unlp.edu.ar)
Date:Wed, 20 Jul 2005 10:47:02

Hello:

I'm writting a Client/Server application who sends text messages over any
local network (and also some file transfer functions).
Well, I put a TidTCPServer on both sides (on the server and on the clients)
active and listen their own port (50000 and 60000 respectively) on the IP:
0.0.0.0 (everyone)
When I need to send anything then activates a TidTCPClient to the contrary
port (the client to the server port and so) to makes the stuff and then
becomes inactive.
I love this method because donīt makes any overload of packets in the
network.
Sounds very good but I think I have any problem with de IP used in the
TidTCPClients because everytime I get some socket connection refused or
sometings like that.
Tested on one machine alone (with 127.0.0.1, I get the same)
Is something wrong in my process?
Who is the right way to setup the IPs directions?
Is there any authomatic way or authomatic configuration where the Indy
components can setup themselves the IPs needed?

Please, I am working too hard and too much time with this and I need any
little satisfaction. :(
Thanks in advance:
Cristian.-

Replies:

www.cryer.info
Managed Newsgroup Archive