RE: Terminal Services API

Al,

Do you mean from the iSeries being able to get the IP of the client to
TS? Or are you talking about a windows API that you can run on the
terminal server box to get the client's IP? 

If the former, I'm not aware of any. In the case of the latter, look at
WTSQuerySessionInformation (try this in google:
WTSQuerySessionInformation site:microsoft.com

Um, and in either case, what if the "client" to the terminal server is
in fact, yet another terminal server box that has it's own clients? I
don't know if you can nest TS connections, but I know I can run VNC to
control another box and then VNC or TS from that box to yet another,
I've done it.

-Walden


------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: rpg400-l-bounces+waldenl=techsoftinc.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+waldenl=techsoftinc.com@xxxxxxxxxxxx] On Behalf
Of Al Pineda
Sent: Tuesday, September 13, 2005 12:38 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Terminal Services API

We are currently using the QDCRDEVD API to retrieve the TCP/IP address
of the workstation device.  This API only returns the TCP/IP address of
the Terminal Server when connected via Terminal Services.  Is there a
corresponding API that works with Terminal Services to get the address
of the workstation?
 

Al Pineda
Senior Programmer/Analyst
CPU Medical Management Systems
800-597-0875
al@xxxxxxxxxx
 
******************************************
CONFIDENTIALITY NOTICE:
Privileged and/or confidential CPU information may be contained in this
message and may be subject to legal privilege.  This e-mail and any
attachments are intended only for the person or entity to which it is
addressed.  If you are not the intended recipient any dissemination,
distribution or copying is strictly prohibited. If an addressing or
transmission error has misdirected this e-mail, please notify the author
by replying to it and delete this e-mail from your system and destroy
any hard copy printouts.  Any views or opinions presented are solely
those of the author and do not necessarily represent those of CPU. The
recipient should check this e-mail and any attachments for the presence
of viruses. CPU accepts no liability for any damage caused by any virus
transmitted by this e-mail.