| Subject | Re: [firebird-support] Re: Cannot connect to a local database |
|---|---|
| Author | Helen Borrie |
| Post date | 2004-08-12T07:35:20Z |
At 07:14 AM 12/08/2004 +0000, you wrote:
files. And, of course, the IP address isn't an attribute of a file, either.
associate a static IP address with a specific server name, at both server
and client stations. That way, with the use of path aliases, the
application can be totally dumb about what it's connecting to...all
provided you standardise on TCP/IP, of course.
them straight! <g>
As for your connecting problem, the client version in your system dir is
the right one (the compatibility client). Search around your system to
find out if you have another, rogue version sitting in a path somewhere
that IBExpert sees before it looks at \system32. For example, on XP, look
in the Windows dir...
/heLen
>IfNope. It's the SERVER service that holds the port, not database
> > you were able to just "connect to the server", what would you expect
>to see/do?
>I thought I'd be able to serve up (eg) c:\Database0 on port 3050 as a
>default (and optionally c:\temp\Database1 on port 3051,
>c:\temp\Database2 on port 3052, etc.), so a client just connects to an
>IP and a pre-determined port for a particular database.
files. And, of course, the IP address isn't an attribute of a file, either.
> > >(is this going to work when it's on their machine?).You can do this, but DNS isn't the way to do it. Use the hosts file to
> >
> > Provided you have configured you app to connect to the correct
>filesystem
> > path for the database file, yes.
>Yep... We may have one install with a server on XP and MAC & linux
>clients connecting to it, and another setup with the server on linux
>and windows & MAC clients connecting to it. This is why it's nice for
>a client to be able to simply connect on a known port (and server
>machine name discovered via DNS) to get the database service.
associate a static IP address with a specific server name, at both server
and client stations. That way, with the use of path aliases, the
application can be totally dumb about what it's connecting to...all
provided you standardise on TCP/IP, of course.
> > Aliasing helps a lot here. Have the appNo, it applies on all platforms. If ibexpert.info tells you otherwise, put
> > connect to an alias and configure the path in aliases.conf. When
>deploying
> > then all you need to do is edit aliases.conf on the deployed server.
>Ummm... is that platform-specific (www.ibexpert.info page 16350.html
>suggests its for win32 only :-( )
them straight! <g>
As for your connecting problem, the client version in your system dir is
the right one (the compatibility client). Search around your system to
find out if you have another, rogue version sitting in a path somewhere
that IBExpert sees before it looks at \system32. For example, on XP, look
in the Windows dir...
/heLen