"Terry tmnet" <tdecruz@tm.net.my> wrote in message
news:44d1c6e1$1@newsgroups.borland.com...
> The computer in question can receive messages from the client
> on another computer when the application is running as a normal
> windows application. It does not respond when running as a
> service.
In order to figure out why connections can reach one application but not the
other, please provide the actual IP addresses that your two machines are
using, the IP/Port that your server is listening on, the IP/Port that your
client is trying to connect to, the router configuration for those IP/ports,
and the firewall permissions for both server applications.
There is no difference between connecting to a server inside a service
versus connecting to a server inside a normal application. A service is a
normal application anyway. Just one that is executed by the SCM instead of
the user. The .exe file itself is a normal .exe like any other, it just
calls a few extra API functions at startup. Otherwise, there is no
difference between them. Connections are accepted on a per-port basis. If
you can connect to a port inside a normal application, but not to a port in
a service, then something is blocking the connection to the service's port.
That has nothing to do with the project being a service itself. So the port
being used by the service is either being blocked (firewall issue), or the
server is reporting errors when trying to accept new connections on the port
(OS/software issue), or the client is not able to reach the server port at
all (router issue).
Gambit
