Hi Dan, me again. If you recall I've been having problems connection to my
server using Firebird 1.0. Well sometime ago in answer to one of my
postings someone asked how I had installed Firebird. I stated that I
installed it onto the server from my client machine. Well after that I
still had problems and many postings after that. I almost gave up. But, I
decided to install Firebird onto the server AT the server. Everything works
great now. I was naive enough to think installation could be made from the
client. But nobody picked up on that one small item. Anyway, I wanted to
thank you and everyone else who tried to help me. I'm sure you'll be
hearing from me further when I finally get into transfering the desktop
databases to client/server and using SQL.

Thanks again
Wayne

----------
From: nitaligavino <Dan.Crea@...>
To: ib-support@yahoogroups.com
Subject: [ib-support] Re: Can't connect to server
Date: Monday, January 13, 2003 11:13 AM

Hi Wayne:

Sorry, I could not remember if nslookup was part of Win95 or not.
Anyway, the domain trust may, possibly, be the issue. However it's
difficult to say without being able to "touch" these systems myself.
To explain, if a client running on domain A wants to talk to a
domain, domain B, the client must be granted trust by domain B's PDC
(primary domain controller ) or BDC ( backup domain controller ).
This is because the client is not a member of domain B. The way I
understand it, the client will perform a lookup, IP resolution, and
then contact to the server directly. The server will check the
credentials of the client against the PDC / BDC for that domain,
domain B, and either allow the connection or reject the connection.
So if the client running in domain A is not trusted its credentials
will be rejected.

Since you are able to ping your server that means that the IP
resolution is okay and you can see the server. The server may
however be rejecting the connection. The only suggestions that I can
make are: