Question

Microsoft Terminal Services and RPG socket programming

AS/400, Security, Servers, Microsoft Windows, RPG, Management, Distribution/logistics applications, OS, Desktops, SQL Server, DB2 Universal Database

Quick background: We are a software developer of medical billing software and have recently partnered with a document imaging company and have developed an interface between our AS/400 database and their document imaging server using RPG socket programs. Most of our clients are using Client Access to communicate with the 400 and our socket programs use the PC's TCP/IP address to determine what port to send messages to.

Problem: We have a client running a Microsoft Terminal Services network and all the PC's are running a thin client environment. Since all the PC's are using the same TCP/IP address, which is the address of the Terminal Services Server we are having a problem determining how to send data back to the individual PC that requested the information.

Question: Is there a way of identifying the workstation on the Terminal Services Server from within the RPG socket program or at least from the AS/400?

I know that all the clients have unique addresses between themselves and the server. You seem to say that the only address the '400' sees is that of the server itself. The server is supposed handle routing between client and outside world. If a client issues a request and the '400' responds does the data not get to the originating client?
Part of the purpose of 'Terminal Services' is the isolation of client from outside source. Are you using rpg:sockets for out of band connection?
Waiting for clarification - hopeful but confused.