"Ted" <ted21@yahoo.com> wrote in message
news:44d19a3f@newsgroups.borland.com...
> No, it does.
No, it doesn't rule it out. I've already explained that.
> Reread his post.
>
> He said:
Which is exactly the same thing that I said. Computer 1 is not able to
accept inbound connections from Computer 2. That is what he has described
several times now. Again, running a server socket inside a service *IS NO
DIFFERENT* than running it from inside a normal application. The socket API
has no concept of the environment it is being run in. It's behavior inside
a service is identical to its behavior in a normal application. So either
Computer 1 is behind a firewall/router that is blocking Computer 2's
connections, or else Computer 2 is not specifying Computer 1's IP/Port
properly when trying to connect. Those are the only two possibilities that
can explain the symptoms he has described so far. The service/non-service
topic is irrelevant. For all we know, his service may simply not be
configured in the firewall properly and his normal application is. Or his
router's port forwarding settings are not configured properly on one port
that the service is trying to use, but are ok on another port that the
normal application uses. There is no way to know at this point because he
has not provided any specific details about his particular network setup or
code configurations, so there is no way to trace the problem further. He
didn't even show any code or error messages yet.
Gambit
