Why Windows Remote Desktop service is automatically disabled

This is another problem that has plagued me for a long time. because you often need to call company files or access the company's LAN resources when you go home, and the company has not enabled VPN, you have been using RDP (Remote Desktop) to access the company's computer.

Suddenly, one day of a month in a year, I found that I could not connect to the system, and asked the "remote computer did not respond" prompt for a night's stay. return to the company the next day, check the port ing on the route, and check the Terminal Services Service of the system. The result is normal. the Remote Desktop was closed. I was a little nervous and thought it was infiltrated, or the system had viruses and Trojans. after some hard work, check whether the system is correct.

Google, there is no result that matches my situation. you have no choice but to restart the Remote Desktop. You can find the connection at home in the evening. I am very surprised to say that this problem is not the cause of the system itself, but will happen under certain conditions.

After returning to the company, I installed the Registry monitoring software and finally found the culprit. When I started the China Merchants Bank Professional Edition Software, the following key will immediately become 1:

HKLM \ systemcurrent \ ControlSet \ Control \ Terminal Server \ fdenytsconnection

So I finally realized that I was raped by China Merchants Bank. I re-enabled registry monitoring and re-confirmed that the problem was found in the file C: \ windows \ system32 \ cmbpb40.exe.ProgramCompatibility makes it unable to modify to the registry key value. Right-click cmbpb40.exe and select Properties to switch to the "compatibility" tab.

Select "Windows NT4.0 (SP5)" from the "compatible mode" drop-down menu, check before "run this program in compatible mode", and finally confirm to complete the settings, in this way, he will not be able to rape at will.

PS: We just found that the Professional version 5.0.0.0 and later is named "personalbankportal.exe" instead of "cmbpb40.exe ".