Ethereum cannot connect to the console

1. There is no problem at all, but relatively speaking, we must buy some reliable ones, because we must pay attention to them.

2. There are many reasons why the terminal can't connect to the server. It depends on what network you are, such as normal LAN? Thin client? What kind of server is it, such as web? ftp Can you Ping... Wait, ha ha

3. Check your router model, different models of router web management entrance IP is not the same

on your computer, use the command line, run CMD, enter the window, and use netstat - RN to view the gateway address. Usually, the gateway address is the web entrance of the router, but it is not absolute

4. 1、 First, enter the connection management terminal (VNC), which has two entries
1. In the alicloud management console - ECS - instance - more, as shown in the following figure:

2. The other is to enter the ECS server management page, as shown in the following figure:

2. The connection management terminal may encounter the following problems in use:
1 After entering the password of the management terminal, you will be prompted "console management terminal connection failed, please check the running status of the server and try again later", as shown in the figure below:

this is because the password of the management terminal (VNC) has been changed before, but the server has not been restarted to take effect through the restart button on the console. In this case, the user can log in normally after restarting the server through the restart button on the console. The restart button is shown in the following figure:

2. After entering the correct VNC password, the user will be prompted "successfully connected to the instance ^ ^ ^ ^ ^ *", but the gray screen will be displayed, as shown in the following figure:

this problem is caused by browser compatibility, Use "Google Chrome browser" to make it display normally.

5.

Remote desktop connection can't be connected, which involves several aspects:

1. check and click terminal services in my computer - right click - service to see if the service is running

2. check my computer - right click - properties - Remote - check remote desktop connection

3. check whether the firewall of the system is turned on, and if it is, please turn it off

4. by default, the remote login account password cannot be empty. Make sure you have a password By default, the user must set a password. If the password is not set, the user cannot log in with a blank password in the remote login interface. This is because the Group Policy (gpedit. MSc) of "computer configuration" → "Windows settings" → "security settings" → "local policy" → "security options" → "account: local account with empty password is only allowed to log on to the console" has been enabled. Modify it, double-click it and change it to "disabled" to log in with an account with empty password.)

5. Terminal Services allows users to connect to remote computers interactively. Remote desktop cannot connect, fast user switching, remote assistance and terminal server rely on this service - stopping or disabling this service can make your computer unreliable. To prevent remote use of this computer, on the system properties control panel item, clear the check box on the Remote tab. C:WINDOWSSystem32svchost.exe -k termsvcs

6. That's because you closed the connection directly instead of logging off when you exited from the last connection. As a result, the remote host thinks that your connection is still in effect. Generally, it takes some time for the host to log off automatically. This time depends on the host's settings. It usually takes 30 minutes or more. If you need a faster connection, you can only ask the system provider to log you off.

7. You should have opened two sessions at the same time, just turn off one. The simplest and most rude thing is to shut down and restart

8. There may be the following reasons:

first, ROS shields the management port, such as port 80.

Second, the local IP and subnet must be set according to ROS. The IP address should be in the same network segment.

Third, setting wrong rules will also lead to the failure of Routeros' winbox connection, It can also lead to disconnection.

solution: http://www.mikrotik.com/download/neighbour.zip Download to run, you can enter your ROS according to your Mac address!! It's in terminal mode. After entering, run this command: IP firewall rule input to enter your firewall rule input chain. Use the print command to see your rule settings. Generally, all connections are disabled. This rule is working. Look at the number of the rule that you prohibit all external connections! If you are right, use this command to disable: disable number. Try to log in again with winbox<

Four: can't connect, add firewall policy, can't use winbox to connect how to do
originally I wanted to make a firewall in firewall, the result estimated that the order is wrong or a step is missing, now I can't log in with winbox

1. Log in locally with ROS and remove the global drop
2. Log in locally with ROS, System reset

Five: could not fetch index from 192.168.0.243 (port 80): disconnect

Routeros winbox error
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Record
2. Enter IP enter and service enter respectively
3. Set www address = 0.0.0/0
in this way, the original state will be restored.

9. Check whether your own computer, including virtual machine, has occupied the IP address

10. Ah, this is not a personal version, this is for Internet cafe update server. You want to use the game to go to the Internet bar to one. This also needs to buy an account. Not recommended.