Troubles with InterBase on uncommon port

[cbc700]

When installing InterBase XE3 with the multi-instance support enabled, it's possible to specify a port for the about-to-be-installed instance. So it's possible to have InterBase instances on ports other than the default of 3050. However, the TUniConnetion dialog has the port field disabled for InterBase, and the documentation mentions the port value being used for a number of databases, but not InterBase.

With my server on port 3051, I've had a whole range of troubles getting a TUniConnection to see it. For the most part, it does not work, whether via the TUniConnection dialog or a TUniConnetion component running in an app. But, there was a time where I used a TUniConnection component via just the property inspector, and was able to get it to connect via setting everything up correctly and checking then Connected property. Not clear as to why, but after some time, I cannot reproduce this. I think there is some bug here. I of course have cleaned up any dupes of gds32.dll and have tried with ClientLibrary set and unset.

Any thoughts here? Thanks.
-C

[cbc700]

After a bit more digging and trying on this, I've found out that there is a InterBase/Firebird syntax when specifying the server that allows for the port specification. A typical server-only value will of course default to port 3050. But a server specification of server/port will allow for port control. Given this, I'm now seeing that I have no trouble getting to my server on 3051.

I found this article particularly helpful...
http://www.destructor.de/firebird/multiinstance.htm

Thanks.
-C

[ViktorV]

Glad to see that the issue was resolved. Feel free to contact us if you have any further questions about IBDAC.