Subject Re: Windows 2003 server is actively refusing connection to client machines
Author graeme_edwards2000
The connection is being made and I am sure that the connection
string is correct. I'm pretty sure that there must be something
blocking port 3050 on Windows 2003 because the server cannot even
talk to the firebird server itself.
I have seen the same issue on a windows 2000 machine running windows
2000 server, with the exception that the server could talk to itself
but clients could not.
In this case I was able to get the client talking using a netbeui
connection. I may have to try the same on the Windows 2003 server.

--- In, "davidalbiston"
<dalbiston@c...> wrote:
> I've seen that message but cannot remember the circumstances. Does
> connection string have the correct path to the database? If you are
> using an alias, does it have the correct path or, if you changed
> alias did you re-start the server?
> --- In, "graeme_edwards2000"
> <g.edwards@s...> wrote:
> >
> >
> > I have a client running windows 2003 small business server who
> > setup the firebird server on this machine and has clients
> > to the machine via a delphi application.
> >
> > When trying to make a TCP/IP connection to the server, the
> > message, "No connection could be made because the target machine
> > actively refused it" appears for all client machines.
> >
> > This happens even when the server attempts to connect to itself
as a
> > server. The server is able to connect using Local protocol.
> >
> > Using the netstat utility, I have been able to establish that
> > when the firebird server is started, there is no evidence of the
> > server listening on the port 3050 (gds_db). There is no entry at
> > for this port.
> >
> > The firebird server has been uninstalled and re-installed
> > times without any change in this behaviour.
> >
> > I have experienced a similar problem on Win XP Service Pack 2
> > has been able to be corrected by opening up port 3050 in the XP
> > firewall.
> >
> > I am using version 1.5.1 of the firebird server.