Max Renshaw-Fox wrote:

> We have a client who has installed a Windows Server 2003 R2 (with the
> "new" MS TCP/IP stack - and new security rules) for their Firebird
> database.
>
> They can connect locally through localhost - all works OK.
>
> They can't connect from another machine (sorry don't have the exact
> message - but will get it if necessary) because they say port 3050 is
> closed (R2 now has "server roles" so, eg, "Email Server" opens ports 25 &
> 110).

Sounds like another 'Mother knows best'. If you can't manage the machine
the way *YOU* want then the software is not 'fit for purpose'.

> Their network guys are better than me on this - so I'm assuming they've
> done their homework - they say there is no "obvious" way to open port 3050
> - so have asked me to ask here - and they'll ask MS.

9 times out of 10 'Their network guys' haven't the faintest idea what
they are doing :(

> Does anyone have experience / pointers / articles that will set me on the
> right path before I "reinvent the wheel" - I'm assuming this will become
> an FAQ topic.

We have had enough fun so far getting 2003 working at all. It sounds as
if we are about to get another batch of 'support calls' as windows shuts
down the servers on the sites that 'Will only run the latest "secure"
version of windows'. But at least *EVERY* other supplier on those sites
is having the same problems - and the customers are starting to accept
that MICROSOFT are the real problem ;)

--
Lester Caine - G8HFL
-----------------------------
L.S.Caine Electronic Services - http://home.lsces.co.uk
Model Engineers Digital Workshop -
http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/index.php