Problem with disabled windows on Terminal Server

This forum is for eXpress++ general support.
Message
Author
k-insis
Posts: 94
Joined: Fri Jan 28, 2011 4:07 am

Re: Problem with disabled windows on Terminal Server

#51 Post by k-insis »

"I also learned that I could access my Windows 10 server via RDP."

If that server is oriented towards Internet you should immediately disable RDP as it is huge target for intrusion script kiddies.
But if it is behind in LAN or behind solid VPN, no worries.

rdonnay wrote: Fri Mar 03, 2023 6:49 am What I learned from this experience is that trapping events, as recommended by Till, doesn't always work.
I also learned that I could access my Windows 10 server via RDP.
I always had used Teamviewer for this.
RDP is much preferred for it's drive mapping to the client.

Tom - I too was a bit concerned about trapping all _EDITPROTECTED errors, but I considered it a small risk in your case.
By the time you were ready to deploy your software to a Terminal Server, I would think it had been well tested.

BTW - The reason this happens only with _EDITPROTECTED is because that code block is not associated with an object that is disabled or hidden and therefore it can process events.
I never use EDITPROTECTED for that reason.
It was originally provided (many years ago) to deal with the issue that a disabled get would always be grayed, and some customers didn't like that, so this was really a workaround.

Post Reply