Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
Based on your description, please kindly review the following steps to help investigate the issue that you occurred.
Step 1: Check Port Reachability
Run the following command from the client machine to check if port 3389 (used for RDP) is reachable: tnc <hostname/IP> -port 3389
This can help identify issues such as:
- Network connectivity problems
- Firewall blocking the port
- RDP service not running
Step 2: Reproduce Session Behavior
Reproduce the scenario:
"If a user has an active session (established through the console), they are able to RDP into the server and assume that active session."
To test this:
- Access the VM via console (e.g., through Hyper-V, VMware, or cloud provider's console access).
- Once logged in, open Remote Desktop Connection (mstsc) inside the VM.
- Try to RDP into the same VM using localhost as the target.
This simulates a user connecting to their own active session via RDP.
Step 3: Inspect Active Sessions
On the affected machine, run: qwinsta
This will list all active sessions. Look for:
- SESSIONNAME (e.g., console, rdp-tcp#X)
- USERNAME
- STATE (e.g., Active, Disconnected)
This helps determine how the user is connected and whether the session is being reused or duplicated.
Hope this helps a bit, and I’m here if you need more details.