Home > OS >  Windows server 2008 r2 server suddenly can't remote, restart recovery after a period of time an
Windows server 2008 r2 server suddenly can't remote, restart recovery after a period of time an

Time:11-11

Windows Server 2008 r2 Enterprise Server suddenly appeared unable to remote connection problem recently, after restart the Server can return to a short period of time, then will disconnect unable to remote, checked the network is normal, normal Server remote port, firewall is shut, allow remote connection, the great god, please help analysis may be what reason cause analysis, how to solve?

CodePudding user response:

Have error screenshot?

CodePudding user response:

reference 1st floor chang_bo response:
have error screenshot?

CodePudding user response:

Reference:
https://blog.csdn.net/u010433704/article/details/50678203

CodePudding user response:

The
reference 3 floor chang_bo response:
reference:
https://blog.csdn.net/u010433704/article/details/50678203

My problem and is not the same as in this article to describe, the firewall to allow the application of remote desktop, the original has been normal, recent problem to be remote, good server restart once, but over a period of time and can't remote,

CodePudding user response:

Problem solved? I also encountered the same problem, the remote server port can't open, can access the rest of the all project

CodePudding user response:

First try to Intranet

CodePudding user response:

If the server is too busy.

CodePudding user response:

I also appear such problem, not remote login, directly to the local server log in, CTRL + Alt + delete not to appear the interface for password... later returned to the CTRL + Alt + delete
The superior solution

CodePudding user response:

I also met such situation, the remote desktop services is busy or jammed, suggest reshipment server system,

CodePudding user response:

Windows server 2008 r2, 64 - bit operating system to run for a few days, the network automatically interrupts normal after the restart, how to deal with?

CodePudding user response:

I also appear this situation, there is a great god have a solution? Because the server hosting is far, so back and forth across the scene processing more troublesome

CodePudding user response:

Or set the problem

CodePudding user response:

1, the client Telnet server IP 3389 check whether can
2. Running on the server netstat ano check whether 3389,

Mostly terminal services stopped, try to manually start, or there are other reasons for causing the service stopped

CodePudding user response:

Turn off the firewall?

CodePudding user response:

Please rule out the possibility of poisoning,

CodePudding user response:

I also encountered such a problem, restart, personal rule out the reason: 1. Several computer remote connection to the server, 2. There is something wrong with the system installation

CodePudding user response:

Suggest modify the remote port, port scanning now very frequent, many sensitive port, similar to 3389 ports easily into sensitive
A key change port to
http://down.gchao.com/1-%E4%B8%80%E9%94%AE%E4%BF%AE%E6%94%B9%E8%BF%9C%E7%A8%8B%E7%AB%AF%E5%8F%A3%E5%92%8C%E5%B1%8F%E8%94%BD%E5%8D%B1%E9%99%A9%E7%AB%AF%E5%8F%A3.zip

CodePudding user response:

How to solve the building Lord, I here is also every other two days to restart can be connected, I saw my CPU is above 90, basic of memory is not big, has accounted for half of CPU system, kingdee account for more than 40 again

CodePudding user response:

Problem solved, please? I also met, boot soon after cannot be remote, then any all say I haven't had enough permissions, operation, and it is strange

CodePudding user response:

Do you remember the last is how to solve??????? Only reshipment system???
  • Related