Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

WinVNC binds to the wrong interface

Post Reply
johnnyhostile
Posts: 2
Joined: 2011-06-09 15:57

WinVNC binds to the wrong interface

Post by johnnyhostile »

Regarding the problem mentioned in the following thread:

http://forum.ultravnc.info/viewtopic.php?p=84978#84978

My host OS is Windows 7 Professional x64

The server is UltraVNC Server 1.0.9.6.1

I get pretty much the same output in the logs that l2onin pasted in the last post in the above thread, and "netstat" does confirm that the server is bound to 0.0.0.0.

Below is the (truncated) output of netstat:

Code: Select all

c:\Program Files\UltraVNC>netstat -ant

Active Connections

  Proto  Local Address          Foreign Address        State           Offloa
tate

  TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING       InHost

  TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING       InHost
I've tried looking at the usage for winvnc.exe to see if there is a way to force it to bind to a different IP but there doesn't seem to be a way.

How can I make it so the server is listening on a real interface instead of 0.0.0.0 ?

TIA
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6863
Joined: 2004-04-23 10:21
Contact:

Re: WinVNC binds to the wrong interface

Post by Rudi De Vos »

Normal, 0.0.0.0 means all network cards
johnnyhostile
Posts: 2
Joined: 2011-06-09 15:57

Re: WinVNC binds to the wrong interface

Post by johnnyhostile »

Thanks Rudi, I was ignorant to that fact and searching for anything that stood out :)

At this point all I have to go on is the following log entry, which is produced when I run "vncviewer.exe -loglevel 10 -console". It's printed to the log after I hit cancel (the process never connects):

Code: Select all

vsocket.cpp : VSocket() m_pDSMPlugin = NULL 
vncsockconnect.cpp : accepted connection from 0.0.0.0
vncserver.cpp : AddClient() started
vncclient.cpp : vncClient() executing...
vncclient.cpp : TEST 4
vncserver.cpp : AddClient() done
vncclient.cpp : client connected : 1.0.0.0 (1)
vncclient.cpp : failed to set socket timeout(10038)
 --An operation was attempted on something that is not a socket.
vncclient.cpp : DSMPlugin Pointer to socket OK
vncserver.cpp : removing unauthorised client
 --An operation was attempted on something that is not a socket.
vncserver.cpp : RemoveClient() done
vncclient.cpp : ~vncClient() executing...
vncclient.cpp : deleting socket
vsocket.cpp : closing socket
Nothing here really stands out as a cause or even being related to a possible cause, except that we failed to set the socket timeout (not sure why, or even how this is set), and that the DSMPlugin is referenced when I do not have it enabled.
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6863
Joined: 2004-04-23 10:21
Contact:

Re: WinVNC binds to the wrong interface

Post by Rudi De Vos »

accept connect 0.0.0.0 <<<<<<<<<<<< something connect to the viewer
client connected 1.0.0.0

This is not normal, what ip addresses are you using.

you start the viewer
vncviewer -listen
server
winvnc -connect ip_address_viewer ?

First try
Run winvnc.exe
Run vncviewer.exe
Enter ip address of the serverPC in the viewer
Post Reply