Interbase and Terminal Server

[MontrealSoft]

Hi guys,
Borland just sent me their support request response, saying that they don't support terminal services w/interbase, but that I should be able to find information on the net about this.

My customer would like to switch to a terminal-server based setup (he has over 30 locations with 1-2 computers each). I installed everything on a 2000 server test bench, along with interbase 5.5 (his version) and even with plenty of licenses, only one user seems to be able to open his custum-built software at a time. Username are differents and both are admins.

Any clue ? MontrealSoft.com

http://www.montrealsoft.com

 

[johnacb]

We are using Interbase 5.5 sitting on a Win2k Server running Terminal Services. We have 4 uses connected no problems. Only thing that stops us is termina lServices Licensing

Is the app running on the same server as the terminal server??

Are you running terminla Services in Remote Admin mode or Application Mode?

What are you running at he client end??

 

[MontrealSoft]

Applications is running on the same server.
Terminal Services are in remote Admin mode, probably switching in applications mode.
Running Interbase 5.5.0.742

MontrealSoft.com

http://www.montrealsoft.com

 

[johnacb]

This is from MS Knowledge base, hope it helps. If you have a test server you will probably swith to app mode and test.
We switched and set up users who accessed straigh waay with no real problems.

When you use Terminal Services in Remote Administration mode, the server accepts only two Terminal Services client connections. When you use this mode, you do not require licensing; however, only members of the Administrators group can gain access to the server. It is recommended that you use this mode for non-Terminal Services servers to configure remote control-type access to remote servers.


Application Server mode: When you use Terminal Services in Application Server mode, the server accepts more than two simultaneous connections by non-administrators. When you use this mode, you must install the Terminal Services Licensing service on a domain controller (you can install this service on any server in a workgroup environment). You also require a Terminal Services Client Access License if you use any non-Windows 2000 Professional-based clients.

 

[MontrealSoft]

Problem is definitly not related to terminal server licensing, we've been working more than a year on different sites implementing TS and we can say we know a lot bout it.

It starts looking like it's the temp database that our custom built software is using. If this one is already opened by a user, no way to make it work with another use.

Yet I changed the config to open this database on the F drive (which I mapped differently for my 2 users) and still have the problem. We'll talk to the programmer that actually built the software and get his opinion on this.

Thank's,

MontrealSoft.com

http://www.montrealsoft.com