Jump to content

Remote Desktop Protocol (RDP) problem


Recommended Posts

the RDP session cancels at times. I believe that another application is using the RDP port causing the failure

can TCPlisten be used to track the application? or is there another way,  I need to find out what application is doing this

Link to post
Share on other sites

Hello,

if the RDP session is already established, then the TCP:3389 is occupied and due to my best knowlege no other process will be able to open TCP:3389. I belive this is already fact, when the RDP service is just running and listening, without an active RDP connection.

 

Perhaps you could provide a more detailed description of your environment? (flat LAN, routed LAN, VPN tunnel to Corp. LAN, ...)

to see what's going on use a CMD.EXE box and execute this command:

netstat -ano

the last column will give you the PID of the process that port is belonging to.

 

CU, Rudi.

Earth is flat, pigs can fly, and Nuclear Power is SAFE!

Link to post
Share on other sites
  • Developers
Posted (edited)
4 minutes ago, rudi said:

if the RDP session is already established, then the TCP:3389 is occupied and due to my best knowlege no other process will be able to open TCP:3389.

Nah ... not really as a TerminalServer can handle multiple clients. ;) 

Obviously only one program running on the server can open end listen to that port.

Edited by Jos

SciTE4AutoIt3 Full installer Download page   - Beta files       Read before posting     How to post scriptsource   Forum etiquette  Forum Rules 
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Link to post
Share on other sites

The OP states as problem "RDP Session cancels at times".

I interprete this as "The RDP session is established, and then dies".

When the RDP session is already opened, then on the target RDP Host the RDP service has TCP:3389 occupied already and due to my best knowlege no other process should be able to register for TCP:3389 as well, causing "RDP Sessions to cancel".

"TS can handle multiple clients"

of course. Like a web server, that many HTTP/HTTPS clients can connect to at the same time.

But only one web server instance can occupy TCP:80 or TCP:443 at the same time, as it is "occupied" by the already running process, no other process will be able to *LISTEN* on the same TCP port again.

Earth is flat, pigs can fly, and Nuclear Power is SAFE!

Link to post
Share on other sites
  • Developers

We are totally in agreement... multiple Clients on the same port can connect and only one process on a server can open a specific port. (As I also stated.) ;) 

 

 

SciTE4AutoIt3 Full installer Download page   - Beta files       Read before posting     How to post scriptsource   Forum etiquette  Forum Rules 
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...