Joel Cooper wrote:
[much snippage]
> Does anyone have any ideas? Is this because my server has the option to be
> contacted on TCPPort 1500? I don't want to use the Windows scheduler to
> handle this, but I have to cover these servers.

The server can only listen on one port - if you define it more than once in
dsmserv.opt, it will use the last one.

Are you running the scheduler in polling mode or prompted?

The limited amount of testing I have done shows that when you use prompted
mode, the server contacts the client on the assigned port, and all the
traffic goes through that one server-initiated TCP session.  This good
because it means one less inbound port that you have to open up.

I haven't done any tests with more than one client though, so I'd be
interested to hear how you get on.

I'm not currently running any clients through a firewall, but I'm a place
where it could be required sometime.  So I'm interested in this topic, but I
just haven't done a lot of testing.