Remoting & Terminal Server

  • Thread starter Thread starter rverschuur
  • Start date Start date
R

rverschuur

We have two .NET desktop applications. The applications
communicate with eachother via .NET Remoting. Application
X marshals an object on a tcp channel. Application Y
connects to that object to communicate with X.

When we install those 2 applications on a Terminal Server
(Citrix), and we start 2 sessions, then the applications
work fine on the first session. X and Y can communicate
via .NET remoting.

On the second session, the 2 applications cannot
communicate. This is because the port that is used by the
tcp channel is already in use by the first session.

Is there a solution to this problem? So that various
desktop applications can communicate with eachother in one
session?

We finally want to have 2 desktop applications communicate
with each other on each session via .NET Remoting.
 
rverschuur said:
We have two .NET desktop applications. The applications
communicate with eachother via .NET Remoting. Application
X marshals an object on a tcp channel. Application Y
connects to that object to communicate with X.

When we install those 2 applications on a Terminal Server
(Citrix), and we start 2 sessions, then the applications
work fine on the first session. X and Y can communicate
via .NET remoting.

On the second session, the 2 applications cannot
communicate. This is because the port that is used by the
tcp channel is already in use by the first session.

Is there a solution to this problem? So that various
desktop applications can communicate with eachother in one
session?
Click to expand...

This doesn't seem to have anything to do with Terminal Services, or even
with remoting.

Two processes cannot use the same port.

So, use different ports.
 
Back
Top