WinVNC - not listenning ( need Help for this)

[webmaster]

The problema is : i cant see the IP ......this is the only mensagem i see
WinVNC - not listenning

what is wrong

[mod=494,1151105847]moved from General Help to New to UltraVNC - beginner questions[/mod]

[redge]

[topic=6429][/topic]
[topic=6763][/topic]

[ianmcphedran]

I get exactly the same fault, when I hover the cursor over the server icon a message appears "winvnc not listening". Clicking on the icon gives the Default local system properties screen with the "accept socket connections" box not ticked. If I tick it and the apply box and close the window, nothing changes,and opening the local system properties screen shows the box not ticked!
This is on my desktop machine (xphome+sp2) linked to a wireless router.
I am trying to replicate its screen on my laptop (xphome+sp2) and have tried connecting them by wireles net and wired lan with no difference.
Can anyone suggest a remedy?

[redge]

you have use a non standard port and winvnc won't tick "accept socket connections"

winvnc ... admin properties
checkbox port = auto and then you able to activate "accept socket connections"

[ianmcphedran]

Thanks for your reply. I cannot select 'auto' until I tick 'accept sockets'.
'Auto' is feint until then. 'Apply , ok' is still not effective and on next opening the panel 'accept sockes' is unticked again!.

[redge]

sorry for confusion
tick "accept socket connections"
then "auto"... OK

then stop winvnc and restart it again.

(winvnc cannot allow connexion on busy port)

[ianmcphedran]

Sorry Redge but that still doesn't work either. I stopped it by right clicking the tray icon (which says winvnc not listening) and restarted it from the Start list. It came up unticked and still had the 'not listening' message.
The program runs correctly on my laptop but not on this desktop system which is annoying since it is a program on the desktop that I want to run from the laptop.

[ianmcphedran]

Further to the above reply I should tell you that by running the Reader on the desktop and entering its own ip address I can control the laptop. The laptop is on my wireless LAN. As I say, I want to control the desktop from the laptop!!

[redge]

i'm sorry, you confusing service mode and user mode

better to close winvnc on systray
then start it again with this command from
Start... Run
net start winvnc

then...
Start... All Programs... UltraVNC .... UltraVNC Server (folder) ... Run Service helper

[ianmcphedran]

Sorry to report tat after doing all that on my desktop the situation is still the same. WinVNC not listening on that machine.

[redge]

I think you bypass some one or more steps,
I can't help more, sorry.

[ianmcphedran]

Thanks for trying.

[ianmcphedran]

The programmer who wrote the software put that message in (winvnc not listening) to cover some event or malfunction. Can anyone suggest a reason? If we knew for certain what the reason was we would have a better idea about what is going wrong. The ports referred to in the discussions above must be software ports but are they inWindows XP? I have no knowledge of the software so am at a loss to know what one can do about changing ports (to what?) or whether they are busy or not.
All I can do is to uninstall the ultravnc software and re-install it (for the fourth time) and check each step very carefully. I am not confident that success will result. Probably no one is reading this anyway, I just wanted to get it off my chest!

[redge]

check the port you want to use is not busy by other software.
http://www.sysinternals.com/Utilities/TcpView.html


fully close winvnc, then open regedit
check the value to 1 for branch of keys below:
[HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]

AutoPortSelect
SocketConnect
AllowProperties

exit regedit
restart computer

[ianmcphedran]

I ventured in to the registry with regedit and found the keys you mention.
Autoport select and Allow properties are at 0x000000 00 00 01 (1)
(I,m not sure about the number of zeros after the x) and SocketCnnect is
0x000000 00 00 00 00
I had one attempt to edit that value that scared the life out of me so I have chickened out in case I do something irreparable!
That appears to be the problem but I lack the moral fibre to edit the registry!

[redge]

don't worry,
create restore point with XP accessories... system tools
if not better, restore to your point you have backed.

[ianmcphedran]

I have managed to change the status of "socket connections" to 1.
I restarted the computer and it's just the same. I am running tcpview and see no processes on a port in the 5000 series such as those shown on the winvnc:default local system properties screen i.e "main 5998" and "http:5898". There is a 2869 which is listening and seems to be always there whilst other things come and go. I tried using that on main but to no effect. I really thought we had cracked it but unfortunately not.

[Hec]

I have this same problem.
This is the only message I see
WinVNC - not listening

I saw the forum about it but it seems that the problem was never solved.
I have the same symptoms explained in the forum. Every time the computer is restarted by one of the users The WinVNC runs automatically and sets to the status as Not Listening. I have to go on site and fix it by clicking on "accept socket connections” then "auto"... OK then the ports change to 5901 or 5902 then I have to do the port forwarding in my router for this new ports, then it works until some one has to restart the computer. Also Whay is it changing the ports on its own? Do I have to open all the ports in my router from 5000 to 5999 nad how wouls I guess to what port to connect?

I did not try any of the procedures listed in the forum because these seemed not to work for the other person.
Is this problem very common? What do you recommend I try first?

[Rudi De Vos]

When port 5900 is used by another application, winvnc switch to 5901 in automode.

WinVNC - not listening:
When a fix port is used and the listener fail... A network port can only be used by one application, you get this error.

The error has nothing to do with the router, it's pure PC stuff network stuff.

[YY]

What do you recommend I try first?

You can use TCPView to check which process/application is occuping the 5900

[XIUYAN1]

Very great~!
Keep up the great work~!
THANSK!