Check with the Firewall. There are 2 things. NAT translation, which is cheap firewall method, where you expose and route the port. Good firewalls also have the firewall level on top of NAT which grant permission based on IP, Packet content etc.
Generally you might set NAT to 5420 -> 192.168.1.5 (server) and in the firewall set WAN(allow any) port 5420 LAN(allow 192.168.1.5) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Scadden Sent: Wednesday, 3 May 2006 3:02 p.m. To: nZ Borland Developers Group - Delphi List Subject: [DUG] Confusion of Indy TCPServer/Client and firewalls. As a complete novice with indy components, I am getting my first taste of firewalls hassles. I have extremely TCPServer on one machine and simple TCPClient on an app in another. Work fine when on the same network but hitting problems when there is a firewall. The port is set to 5420 and firewall set to allow traffic on that port. Should the client have other components to be able to talk through a firewall? ---------------------------------------------------------- Phil Scadden, Institute of Geological and Nuclear Sciences 764 Cumberland St, Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232 _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
