Make Client IPs and name visible beyond Terminal Server

[NLPB]

Hello,

I'm wondering is there a way to make the IP and or name of a client visible
to an application once it's connected to a Terminal Server. Here's my
situation. I have an application that when installed and used from a regular
computer is set to an optimized mode when connecting to it's backend database
server. You know this by checking the properties within the app and it
states the workstations name and IP. However, I am now testing Thin Clients
with the app frontend installed on a Terminal Server. I can connect to the
server and run the app but it's in non optimized mode because when you look
at the properties within the app this time, the IP and name of the Terminal
Server itself are used as the connecting choice. My hope was that I could
have the client's IP and or name "pass through" the terminal session and
trick the application into thinking it's running directly on the thin client
just like it does when installed locally on a regular computer.

Thanks.

 

[Vera Noest [MVP]]

Re: Make Client IPs and name visible beyond Terminal Server

This is something that has to be built into the application. It can
retrieve the %clientname% (as opposed to the %computername%, which
is the TS) and the client's IP number with the
WTSQuerySessionInformation function. Have you contacted the vendor
of the application?

http://msdn2.microsoft.com/en-us/library/aa383838.aspx

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TkxQQg==?= <NLPB@discussions.microsoft.com> wrote on 17
dec 2007 in microsoft.public.windows.terminal_services:

> Hello,
>
> I'm wondering is there a way to make the IP and or name of a
> client visible to an application once it's connected to a
> Terminal Server. Here's my situation. I have an application
> that when installed and used from a regular computer is set to
> an optimized mode when connecting to it's backend database
> server. You know this by checking the properties within the app
> and it states the workstations name and IP. However, I am now
> testing Thin Clients with the app frontend installed on a
> Terminal Server. I can connect to the server and run the app
> but it's in non optimized mode because when you look at the
> properties within the app this time, the IP and name of the
> Terminal Server itself are used as the connecting choice. My
> hope was that I could have the client's IP and or name "pass
> through" the terminal session and trick the application into
> thinking it's running directly on the thin client just like it
> does when installed locally on a regular computer.
>
> Thanks.

 

[Leythos]

Re: Make Client IPs and name visible beyond Terminal Server

In article <4BCFE4B1-4625-4851-8557-4870E3146962@microsoft.com>,
NLPB@discussions.microsoft.com says...
> I can connect to the
> server and run the app but it's in non optimized mode because when you look
> at the properties within the app this time, the IP and name of the Terminal
> Server itself are used as the connecting choice. My hope was that I could
> have the client's IP and or name "pass through" the terminal session and
> trick the application into thinking it's running directly on the thin client
> just like it does when installed locally on a regular computer.

But the terminal device doesn't matter - the Terminal Server is where
the program is running, not the client terminal computer.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)