Subject | Re: [firebird-support] Installation problem |
---|---|
Author | Helen Borrie |
Post date | 2005-11-02T23:18:33Z |
At 08:42 PM 2/11/2005 +0100, you wrote:
1. localhost won't work from a remote desktop. Use the server's node name
with the syntax provided by Thomas.
2. If you still get the same exception, check that the service is actually
running.
3. If it is, and you still get that exception, add entries for the
server's permanent IP address into the hosts file of both the server and
your client (c:\windows\system32\drivers\etc\hosts).
./heLen
>Walter,Further comments:
>
> > I am trying to install Firebird on a server that I access by Windows
> remote
> > desktop.
> > The server is (I think, I have never seen it in the flesh) HP Proliant
> > ML350 G4 with Intel Xeon 3/00 GHz chip., Running Windows Server 2003
> > Enterprise edition.
> >
> > First I installed an Apache2 server, which works OK so I assume TCP/IP is
> > up an running on the server.
> >
> > Then I downloaded and ran Firebird-1.5.3.4854-0_RC2-Win32.exe and the
> > resulting directory structure looks OK.
> >
> > Next thing I wanted to do was change the sysdba password using gsec. In
> > the Command Prompt I did:
> >
> > C:\Program Files\Firebird\Firebird_1_5>bin\gsec -user sysdba -password
> > masterkey
> >
> > and got:
> >
> > unavailable database
> > unable to open database
>
>Try if it helps when you are specifying the security database by using
>the TCP/IP loopback protocol. For example:
>
>gsec -database localhost:c:\<path>\security.fdb -user sysdba -password
>masterkey
1. localhost won't work from a remote desktop. Use the server's node name
with the syntax provided by Thomas.
2. If you still get the same exception, check that the service is actually
running.
3. If it is, and you still get that exception, add entries for the
server's permanent IP address into the hosts file of both the server and
your client (c:\windows\system32\drivers\etc\hosts).
./heLen