Subject | Re: [firebird-support] Re: connection ! problem - centos 4.3, have tested with all versions of 1.5.3 |
---|---|
Author | Helen Borrie |
Post date | 2006-10-04T15:21:34Z |
At 11:44 PM 4/10/2006, you wrote:
The firebird.log file doesn't get written to during
installation. However, the gethostbyname clue says that a client
asked to connect to host by the name of asterisk1.local and the
network couldn't find a mapping for it. Apparently it's the
hard-coded server name the application is trying to connect to, not
the IP address you put in your ini file.
Look in the /etc/hosts file and see what's there for that IP
address....if necessary, add an entry:
192.168.2.10 asterisk1.local
(case-sensitive on Linux) and see whether the app has any better
success at connecting.
Might need a similar entry in the $windir$\system32\drivers\etc\hosts
file on the client, as well.
./heLen
>Thanks for this initial help helen.I don't know. There are no clues here regarding authentication, though.
>
>ib_sql on the windows workstation allows me to connect to each of
>the databases on the (i.p. = 192.168.2.10) server. No problems. I
>can browse each database. No error messages and nothing is generated
>in the firebird log file when I do this
>
>There is repeated message in the firebird log file which I think
>occurred during re-installation. This was due to an installation
>issue that I corrected...(I downgraded to 1.5.1 SS which is the same
>as the version I have in the office server)
>asterisk1.local (Server) Wed Oct 4 21:22:10 2006
>INET/INET_connect: gethostbyname failed, error code = 1
>
>I'm not getting any firebird log messages now
>
>Could there be a problem with security.fdb?
The firebird.log file doesn't get written to during
installation. However, the gethostbyname clue says that a client
asked to connect to host by the name of asterisk1.local and the
network couldn't find a mapping for it. Apparently it's the
hard-coded server name the application is trying to connect to, not
the IP address you put in your ini file.
Look in the /etc/hosts file and see what's there for that IP
address....if necessary, add an entry:
192.168.2.10 asterisk1.local
(case-sensitive on Linux) and see whether the app has any better
success at connecting.
Might need a similar entry in the $windir$\system32\drivers\etc\hosts
file on the client, as well.
./heLen