Ultra VNC Listening not working

[junique81]

I'm having an issue with my Ultra VNC viewer. currently it has a port number assigned to it (e.g. 6500)
the way we have it working is, it is tied in to our support website.

what is supposed to happen is, a client goes to our support website, and clicks on our name. Once they click on our name, they have to download and install "live support" then I should see a pop up message (Accept incoming SC connection) that I click on yes, and remote right into the client.

the problem is, when the client downloads and installs the "live support" application, I never get the pop-up indicating to me that someone wants to connect, and therefore I am unable to connect to client.

Has anyone out there had this problem? If so, what can I look at (settings,etc) to resolve this.

Thanks!

[Csimbi]

I just installed UVNC 1.2.0.6.
When I hover over the icon on the tray, it says not listening.
I stop the server and run the setting editor: accept sockets connection is unchecked!
I enable and set port number manually.
I click ok and start it again - settings are there.
I start the uvnc service.
When I hover over the icon on the tray, it says not listening.
I open admin properties via the tray icon's right click menu: accept sockets connection is unchecked!
So check it and enter port number manually.
When I hover over the icon on the tray, it says not listening.
I open admin properties via the tray icon's right click menu: accept sockets connection is unchecked!
I run the setting editor: accept sockets connection is checked!
Excuse my language, but WTF?

[Rudi De Vos]

If uvnc_service service is running, disable, it's faster to test in app mode.
-remove winvnc.ini and start winvnc
-set password
-activate winvnc log

If listener start, and this fail, the menu show the current status and "accept sockets connection is unchecked", this has nothing
todo with the saved value's. You can verify this in the ini file.

start a cmd with runas admin
netstat -bn
Check is no other software is using our listener port.

Check the winvnc log file, perhaps there is some error message indicating why the listener can start

[Csimbi]

I saw some weird messages in the log saying that sockets not being used correctly or something.
I had a look at the firewall rules and then I realized that WinVNC.exe was disabled on the firewall.
(I imported firewall rules from another PC.)

Thanks!