How To Restart VNC Server After VNC Service Hangs or Stops Unexpectedly?
How difficult is to restart the VNC server or service? Well, there is certainly no difficulty at all, if you’re in front of the server.
Now, imagine that server is at few hundred miles away and nobody is there to restart that bloody machine.
Worst still, simply reboot the machine might not able restart the VNC server.
So, what could you do in order to get the VNC server back to work? Precisely, if you can’t VNC to the remote server, how could you attempt to restart the VNC service?
OK, here are the tips and tricks for VNC server running in Windows or Linux machine.
To apply this method, however, there must be network connection between you and the remote server.
Restart VNC service of a remote computer running Windows 2000 or above
You must do the following steps on a computer running Windows 2000 or above as well. Let say this is a Windows Vista Ultimate machine.
1) Click the Vista Orb (Start button), right-click on Computer and select Manage option from the pop-up menu. This will open Computer Management window.
2) Right-click the Computer Management (Local), the top node on left pane, and select Connect to another computer….
Alternatively, click the Action menu to find the same option.
3) In the Select Computer dialog box, opt for Another Computer and type the computer name in the text box.
If you can’t remember the computer name, click Browse button follow by Advanced button and click Find Now to list all computers detected.
Now, hopefully this step will be succeed. Otherwise, it ends here :-(
Once you’ve connected the remote computer, click Services and applications node on the left pane of Computer Management window. From there, locate the VNC service on the right pane and restart it.
Restart VNC service of a remote computer running Red Hat Enterprise Linux
With Linux, this job is easier :-)
Other than network connection, you must able to remotely login the Linux server, be it the vulnerable telnet or secure SSH protocol.
After login to Linux command prompt (via telnet or SSH), just execute
If there is no auto-start setup, then do the manual ways as you’ve done:
1) If the VNC server process stills exists, and it was started with DISPLAY:1, then kill it will command
2) Start it again by executing
Now, you can confirm the VNC server is up again by executing netstat command:
If the VNC server is started for DISPLAY:1, the netstat result should shows Xvnc listening to three different ports: 5801, 5901, and 6001.
Worst still, simply reboot the machine might not able restart the VNC server.
So, what could you do in order to get the VNC server back to work? Precisely, if you can’t VNC to the remote server, how could you attempt to restart the VNC service?
OK, here are the tips and tricks for VNC server running in Windows or Linux machine.
To apply this method, however, there must be network connection between you and the remote server.
Restart VNC service of a remote computer running Windows 2000 or above
You must do the following steps on a computer running Windows 2000 or above as well. Let say this is a Windows Vista Ultimate machine.
1) Click the Vista Orb (Start button), right-click on Computer and select Manage option from the pop-up menu. This will open Computer Management window.
2) Right-click the Computer Management (Local), the top node on left pane, and select Connect to another computer….
Alternatively, click the Action menu to find the same option.
3) In the Select Computer dialog box, opt for Another Computer and type the computer name in the text box.
If you can’t remember the computer name, click Browse button follow by Advanced button and click Find Now to list all computers detected.
Now, hopefully this step will be succeed. Otherwise, it ends here :-(
Once you’ve connected the remote computer, click Services and applications node on the left pane of Computer Management window. From there, locate the VNC service on the right pane and restart it.
Restart VNC service of a remote computer running Red Hat Enterprise Linux
With Linux, this job is easier :-)
Other than network connection, you must able to remotely login the Linux server, be it the vulnerable telnet or secure SSH protocol.
After login to Linux command prompt (via telnet or SSH), just execute
service vncserver restart, if the VNC server is configured to auto-start when Linux boots up / reboot.If there is no auto-start setup, then do the manual ways as you’ve done:
1) If the VNC server process stills exists, and it was started with DISPLAY:1, then kill it will command
vncserver -kill:12) Start it again by executing
vncserver :1Now, you can confirm the VNC server is up again by executing netstat command:
netstat -tulpan | grep vnc
If the VNC server is started for DISPLAY:1, the netstat result should shows Xvnc listening to three different ports: 5801, 5901, and 6001.
Custom Search
2010 •
Hi
your document is very help for configuring new vnc..thanks for that..
i am not able to connect vnc sessions.. please help
this is how i created vnc session for me
[root@localhost ~]# vncserver
New ‘localhost.localdomain:7 (root)’ desktop is localhost.localdomain:7
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/localhost.localdomain:7.log
this machine is not in NIS. when i try to connect the session from windows by using vnc software. it is not connecting, i have to configure anything additionally..
error: unable to connect to host: A socket operation was attempted to an unreachable host.(10065)
thanks in advance..
faizal
I guess there is no network connection between VNC client and server.
thanks. A ton, windows remote service reset worked!!
Hello….I was hoping we could go further with the instructions on how to “Restart VNC service of a remote computer running Windows 2000 or above”. Reason being, the instructions will not work if VNC has bombed on the server. In other words, if VNC Server bombs out and an error message is up on the screen, the the steps above will not work. When you try to restart VNC server, it won’t work – the service is unable to stop. So, any thoughts on what to do then? One thing I wanted to try was to RDP into the server and end task the VNC server error message….however, I don’t know what that process is named, and if I am running something on that box, I don’t want to end task things without knowing exactly what they are. Any thoughts?
Maybe you can try the pskill to terminate the VNC processes in remote server.
1) Download the pskill of Sysinternals Utilities.
2) Take note of the VNC processes running in your server (so that you can pskill them remotely if so unlucky the case happen again).
I hope that will help. Please let me know your testing. Appreciated that.
Thanks for this very clear to follow information. Saved me a 30 mile round trip!