Subject Re[3]: [firebird-support] Firebird performance on Dual Core machine
Author Helen Borrie
At 08:24 PM 2/01/2006 +0700, you wrote:

>First, I've install the classic server using this command:
>instreg install -z
>instsvc install -auto -classic -guardian -z
>instsvc start
>
>Second, I try to connect (with IBExpert) the database. I Configured
>like this:
>Server = remote
>Server Name = localhost
>Protocol = TCP/IP
>Server Version = Firebird 1.5
>Database File = c:\program files\firebird\firebird_1_5\examples\employee.fdb
>
>When I tried to connect to this database, IBExpert is hang. What's the
>problem?
>
>Another way, i use the server type to local and the database file i
>was changed to localhost:c:\program
>files\firebird\firebird_1_5\examples\employee.fdb but the error
>message occured, with this message:
>
>Connecting... Failed!
>------------------------------------
>Unsuccessful execution caused by a system error that precludes
>successful execution of subsequent statements.
>Unable to complete network request to host "localhost".
>Failed to establish a connection.
>No connection could be made because the target machine actively refused it.
>.
>
>Attempting to connect to services manager... Failed!
>------------------------------------
>
>Unsuccessful execution caused by a system error that precludes
>successful execution of subsequent statements.
>Unable to complete network request to host "localhost".
>Failed to establish a connection.
>No connection could be made because the target machine actively refused it.
>.
>
>I've checked the task manager at the tab service, and the service
>fb_inet_server.exe is running.

You have a network configuration problem. The most likely one is that you
have XP and installed the service pack without opening port 3050 in the
firewall.

Contrary to what someone else (wrongly) said, the local loopback server
exists on any machine where TCP/IP is running. Test this by going to a
command window and typing

ping localhost

You should also check whether TCP/IP is actually running, of course!

However, so far you haven't mentioned what version of Windows you are
running. If your Windows is Server 2003, and you are using Remote Desktop
locally, the local loopback might not be available, since Windows sees your
RD as just another remote client and localhost can not be accessed by any
remote client. In that case, you will need to use the machine's node name
instead of localhost.

./heLen