Using 1.0.9.6 on Win XP SP3 Not Connecting

Using 1.0.9.6 on Win XP SP3 Not Connecting

Postby ShawnIT » 2014-01-14 02:12

Ive installed 1.0.9.6 msi on my xp stations with a script. The computers start the service fine but I can not connect to them. The error is that the connection is refused. Though group policy I have opened port 5900 in the firewall, which didnt help. I have now disabled the Win XP firewall altogether. Still having the same results. On win7 and win 8 stations everything is working fine with the same setup.


Any ideas?
ShawnIT
 
Posts: 2
Joined: 2014-01-14 02:04

Re: Using 1.0.9.6 on Win XP SP3 Not Connecting

Postby Bonji » 2014-01-16 15:35

Do you have additional firewall software on the XP computer?

Are you sure the service is listening on the XP computer? (verified with "netstat -a")

Can you telnet to port 5900 from another computer to the XP computer?
If no firewall is blocking the connection, and the uVNC server is listening properly, you should get a message in the telnet client similar to "RFB 003.008".
If you're unable to connect with a telnet client, then either the uVNC server is not configured properly or something (firewall/antivirus) on the XP client is blocking the communication.
-Ben
Bonji
100
100
 
Posts: 325
Joined: 2008-05-13 14:54

Re: Using 1.0.9.6 on Win XP SP3 Not Connecting

Postby ShawnIT » 2014-01-18 02:27

I double checked our antivirus and the firewall feature isn't installed there.

I confirmed that the service is running and listening.

End the end I'm not sure what the issue sis but I have noticed when I go into services and try to restart the service is freezes on stopping on everyone of my xp stations. I have to force stop the service cmd.
ShawnIT
 
Posts: 2
Joined: 2014-01-14 02:04

Re: Using 1.0.9.6 on Win XP SP3 Not Connecting

Postby Bonji » 2014-01-20 19:01

It sounds like the uVNC service is not running properly. I would ensure the service is not running and that there are no instances of winvnc.exe running on the computer, and then try starting winvnc.exe manually.

Ensure this instance of uVNC can be connected to, and that the admin properties are viewable/settable.

If this works, then I would uninstall uVNC as a service (winvnc.exe -uninstall) and re-install it (winvnc.exe -install). If it doesn't work, then you either have a bad executable file or the configuration needs further modification. You can delete the ultravnc.ini file to ensure the configuration is clean the next time the application starts.
-Ben
Bonji
100
100
 
Posts: 325
Joined: 2008-05-13 14:54


Return to 1.0.9.6 (stable)

Who is online

Users browsing this forum: icioman and 2 guests