Ok, here we go >>>

We have a strange problem - We have 2 Servers, Server1 is
a Terminal Server and Server 2 is a SQL server. We also
have a piece of VB

software that derives information from our SQL databases.
This is how it is all set-up and how it SHOULD work >

- Terminal Services clients connect to the Terminal Server
- The Terminal Server has VB Software installed along with
the appropriate ODBC/DSN links that link on to Server2
(SQL Server)
- The users can then access the database via the software

We also have users connecting via 'thick client' ie NOT
via Terminal Services client < Now these users can connect
with no problems whatsoever.

However the users connecting via Terminal Services CANNOT
access properly and we get access denied error messages
etc when trying to

use the application. The ONLY thing that lets the
Terminal Services users access the system is if I add
those particular users to the Domain

Admins group via AD Users & Computers - obviously this is
NOT good. does 'anyone' know of 'anything' I can do to
diagnose this problem ?... is

this a 'known' type of issue when trying to access SQL
over terminal services and are there any simple workarounds

I installed the VB application on the Terminal Server
in 'Application Install' mode on the Terminal Server and
then switched back to 'Apllication

Execute' mode...so I don't think this could be the problem

ANY help at all would be fantastic

many many thanks in advance guys

cheers - Craig

How is your VB application sending across its connection
information? If you are using trusted integration then
your application is attempting to send the terminal
services user id to the SQL server, therefore only adding
the terminal services user id will resolve it this way.

You VB app should use a generic account or a application
ID in SQL to run against rather than using the trusted
integration system.

cjones
DBA

>-----Original Message-----
>Ok, here we go >>>
>
>We have a strange problem - We have 2 Servers, Server1 is
>a Terminal Server and Server 2 is a SQL server. We also
>have a piece of VB
>
>software that derives information from our SQL
databases.
>This is how it is all set-up and how it SHOULD work >
>
>- Terminal Services clients connect to the Terminal Server
>- The Terminal Server has VB Software installed along
with
>the appropriate ODBC/DSN links that link on to Server2
>(SQL Server)
>- The users can then access the database via the software
>
>We also have users connecting via 'thick client' ie NOT
>via Terminal Services client < Now these users can
connect
>with no problems whatsoever.
>
> However the users connecting via Terminal Services
CANNOT
>access properly and we get access denied error messages
>etc when trying to
>
>use the application. The ONLY thing that lets the
>Terminal Services users access the system is if I add
>those particular users to the Domain
>
>Admins group via AD Users & Computers - obviously this is
>NOT good. does 'anyone' know of 'anything' I can do to
>diagnose this problem ?... is
>
>this a 'known' type of issue when trying to access SQL
>over terminal services and are there any simple
workarounds
>
>I installed the VB application on the Terminal Server
>in 'Application Install' mode on the Terminal Server and
>then switched back to 'Apllication
>
>Execute' mode...so I don't think this could be the problem
>
>ANY help at all would be fantastic
>
>many many thanks in advance guys
>
>cheers - Craig
>.
>

Craig, can you send me a direct email

So I can send you some example code

I have vb6 running on Windows2003 Server TS
accessing SQL Server version 7 on NT4

users dont get prompted about username, etc