Microsoft Terminal Services and RPG socket programming

Distribution/logistics applications
Microsoft Windows
SQL Server
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?

Answer Wiki

Thanks. We'll let you know when a new response is added.

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.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • CraigFox
    Summary of question: You have clients that access an AS400 environement through an application runnning on a Terminal Server. The AS400 uses the connecting IP information to distinguish between the various clients and they all look the same to the AS400, the WIndows Terminal Server. Resolution: Citrix Presentation Server 4's engine has been rewritten to resolve this type of problem. Amongst other isolation capabilities, each session can be assigned a unique IP stack. THis should allow the AS400 to distinguish between differing sessions from the same TS server. Notes: It may be cheaper to change the app than go to Citrix and you should be able to get an eval of Citrix to see of this will resolve your problem. Hope this helps
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: