I'm stumped.
I upgraded from 11b to the latest (RC18), and then I couldn't see my machine from other clients. Sooo, I uninstalled RC18, cleaned the registry, installed 11d (yup, D), but still the same problem.
I keep getting "Failed to connect to server" messages if I use the IP or netbios name of my machine WinXP laptop, but if I use "LOCALHOST", it works fine.
I've repeated this on my desktop Win2k box, with the same results. I can view OTHER servers on the network (except Win2k desktop), but I can't see the laptop locally, or from _any_ other clients on the network.
Using Telnet on my laptop (sb9), using
"telnet sb9 5900" or "telnet 192.168.0.110" comes up with
"Could not open a connection to host on port 5900",
BUT using "telnet localhost 5900" returns
"RFB 003.006" (then a pause, and "Connection to host lost"), which means the software WORKS, but isn't listening to the network.
Some funky stuff is going on here where I can PING and create shares on remote machines, but Winvnc server doesn't seem to be listening to IP or Netbios addresses.
---------
I remembered about "netstat -an", and I ran it on my workstation (192.168.0.11 / sb4). It shows the following:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1049 127.0.0.1:5900 TIME_WAIT
TCP 127.0.0.1:5800 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5900 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5900 127.0.0.1:1045 TIME_WAIT
TCP 192.168.0.11:139 0.0.0.0:0 LISTENING
TCP 192.168.0.11:1028 0.0.0.0:0 LISTENING
TCP 192.168.0.11:1028 192.168.0.172:139 ESTABLISHED
TCP 192.168.0.11:1043 192.168.0.187:139 TIME_WAIT
TCP 192.168.0.11:1044 192.168.0.171:139 TIME_WAIT
TCP 192.168.0.11:1047 192.168.0.187:139 TIME_WAIT
UDP 0.0.0.0:445 *:*
UDP 192.168.0.11:137 *:*
UDP 192.168.0.11:138 *:*
UDP 192.168.0.11:500 *:*
Hmmm. Ports 5800 and 5900 are only being "listened" on 127.0.0.1 - how do I make it listen on the default IP too?
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
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 server can be seen via LOCALHOST but not ip/netbios
-
- Posts: 3
- Joined: 2004-07-08 16:49
-
- Posts: 3
- Joined: 2004-07-08 16:49
Figured out localhost only winVNC problem
HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\
There's some registry settings in here that I found referenced at:http://www.cs.vu.nl/~eliens/documents/vnc/winvnc.html that show "advanced settings".
Didn't realize there were more registry settings, in particular:
LoopbackOnly
Which is apparent what IT does. So I searched for all instances of \ORL\ in the registry, deleted the "WinVNC3" groupings, and reinitialized winvnc.exe.
Back to normal!
Hope this helps somebody else...
There's some registry settings in here that I found referenced at:http://www.cs.vu.nl/~eliens/documents/vnc/winvnc.html that show "advanced settings".
Didn't realize there were more registry settings, in particular:
LoopbackOnly
Which is apparent what IT does. So I searched for all instances of \ORL\ in the registry, deleted the "WinVNC3" groupings, and reinitialized winvnc.exe.
Back to normal!
Hope this helps somebody else...