Information générale
Catégorie:
Fonctions Windows API
Titre:
Communicating Between Terminal Server Sessions
Versions des environnements
Network:
Windows 2003 Server
Hi All,
I'm looking for some advice. I have an application that communicates between clients on individual PCs using UDP using the Winsock activeX control. It works fine, but I ran into a snag when trying to run the same application on multiple terminal server sessions. The first user's session grabs the UDP listening port and the other sessions get an error "port in use" when they try to launch, which makes sense.
I'm exploring alternative methods of communication between the hosted sessions. An installation could have a mix of individual clients and hosted clients.
I'd rather not use a timer or a file based method, as the message display on the clients needs to be synchronized as closely as possible. An event hook would be ideal. I was thinking of creating a system service specifically for Terminal Servers which could handle listening over the UDP port, but I'm looking for a good method of communicating between that service and the hosted clients.
Any ideas or advice are greatly appreciated.
-Matt
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement