Subject Firebird 1.5.3 SS on Windows Server 2003 R2
Author Max Renshaw-Fox
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

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 &

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.

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.