VDS server mouse.

[Syrox]

I've had this problem twice now, it is that the server side mouse don't work/react to when I move it or clicking, I've tried connecting through the vcn console in control panel and through tightVNC, I've also tried connecting through another computer.
I have also tried to restart the VDS through the control panel but nothing happens after it.

Any ideas what the problem is?

[soja]

Don't use VNC

[Syrox]

Can't get Remote Desktop to work :/

[soja]

Remote desktop is set up automatically, and should be used instead of VNC. There is no configuring that needs to be done on a NFO VDS.

[Syrox]

Well when I try to connect from my computer it says that its not enabled on the server/That its wrong IP/that the server computer is not on :/

[Edge100x]

Both methods should work fine, but RDP is definitely preferred. Do you have a firewall that is blocking RDP?

[Syrox]

No.

[Edge100x]

Are you having other problems with the VDS, such that it is unpingable or can't pull up webpages in its web browser?

[Syrox]

not really, had a problem with it restarting itself constat for about 1 hour until an staff could force shutdown and do disk check or something and then its this problem with the mouse.

[Edge100x]

In that case, a firewall problem is most likely (on the client side, inside your OS, or on the Firewall page of the control panel). You should also check to make sure that the terminal services / remote desktop service is enabled.

[Syrox]

Edge, you asked if the server was unpingable and I've answered no, but I retried ping it and it fails.
What can be the problem then?

[Edge100x]

That would be a firewall issue, an IP misconfiguration, or an OS freeze-up.

[soja]

What is the response when it fails? This can be an indication of the cause.

[GRSteelers]

If your VDS is running Windows Server 2012 and you cannot connect via RDP, it is very likely that there has been a glitch in the firewall setup by the server. Windows Server 2012 is known to occasionally fail to establish a rule properly to allow the incoming RDP connection (TCP port 3389) on all domains. The solution would be to change the serverside firewall settings by adding an exception to the incoming connection firewall for that port on all domains, however the fact that you cannot click poses a problem. Beyond changing it in the GUI through a VNC client, I am unaware of a solution for access to the firewall settings.
Hopefully, you'll catch the VNC functioning properly at some point so you can apply the fix ASAP and get access to your box.

[Syrox]

It says connection timed out when I try to ping the server.