![]() If I choose Console, the user gets kicked out as expected. This image is the problem client's computer: if I click on choice 1, nothing happens, but it SHOULD connect to the live user's session without kicking out the user. Today, I even made two videos showing them, but I probably won't hear back for a couple of days. I have sent them proof that it works.a screen shot of a live RDP session on one monitor with Splashtop connected to it on another monitor, and both live. The "Active" named session should allow BOTH simultaneously. He only would be correct if I were trying to connect to the Console session, but that is NOT what I told them I wanted to do. Their first response was, "Splashtop and RDP use the same ports, so this would force one user using a RDP/Splashtop to boot the other user off." At that point, I knew I was in for a long week. This method DOES work in my office to connect to a Windows 7 VM or a Win 10 physical computer. I need to be able to have us BOTH on the computer.the user via RDP, and me via Splashtop. If I try to help one of those RDP users via Splashtop, when I log into their RDP session via Splashtop's choice to connect to the active RDP session, it kicks them out of their RDP session, and if they log back in via RDP, it kicks ME out of the Splashtop connection. RDP is NOT open to the Internet in general). I have users on Windows 7 who are accessing their work computers from home via Remote Desktop Connection (don't worry, it's only after they authenticate to their WatchGuard firewall. They have COMPLETELY MISSED what I am telling them or have given me false information. I have a ticket open with Splashtop support (#111861) but I am getting ABSOLUTELY NOWHERE with them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |