Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
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
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- 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

"accepted connection from 168.255.224.0"

Post Reply
David4
8
8
Posts: 24
Joined: 2010-08-11 15:13

"accepted connection from 168.255.224.0"

Post by David4 »

When shutting down UltraVNC, in the log file there's this line. What does this mean? Further: "Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte." Which connection is meant there? No connection from myself, that's what I know.
Anyway, quite a lot of messages, which seem to tell nothing. (Starting winvnc.exe, shutting down without trying a connection before and then such a lot of loglines...?!)

Code: Select all

Sun Feb 16 00:42:17 2020
vncmenu.cpp : KillAuthClients() ID_CLOSE 
vncserver.cpp : KillAuthClients() done
vncmenu.cpp : vncMenu::Shutdown: Close menu - Disconnect all - Shutdown server
HideDesktop.cpp : Restorewallpaper 0
vncmenu.cpp : Reset 0 
vncmenu.cpp : vncMenu WM_CLOSE call - All cleanup done
Sun Feb 16 00:42:19 2020
vncmenu.cpp : quitting from WM_DESTROY
vncserver.cpp : KillAuthClients() done
 --Ungültiges Fensterhandle
vncmenu.cpp : vncmenu killed
HideDesktop.cpp : Restorewallpaper 0
 --Der angegebene Dienst ist kein installierter Dienst.
vncmenu.cpp : Reset 0 
winvnc.cpp : ################## Closing Imp Thread
 --Das System kann die angegebene Datei nicht finden.
winvnc.cpp : ################## SHUTING DOWN SERVER ####################
 --Es wurde versucht, einen Mutex freizugeben, der nicht im Besitz des Aufrufers war.
vncserver.cpp : shutting down server object1
vsocket.cpp : shutdown socket
vsocket.cpp : VSocket() m_pDSMPlugin = NULL 
 --Ein Blockierungsvorgang wurde durch einen Aufruf von WSACancelBlockingCall unterbrochen.
vncsockconnect.cpp : accepted connection from 168.255.224.0
vsocket.cpp : closing socket
vncsockconnect.cpp : quitting socket connection thread
 --Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist.
vsocket.cpp : closing socket
 --Eine Anforderung zum Senden oder Empfangen von Daten wurde verhindert, da der Socket nicht verbunden ist und (beim Senden über einen Datagrammsocket mit einem sendto-Aufruf) keine Adresse angegeben wurde.
vsocket.cpp : VSocket() m_pDSMPlugin = NULL 
 --Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist.
Sun Feb 16 00:42:20 2020
vsocket.cpp : closing socket
 --Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
vsocket.cpp : closing socket
vsocket.cpp : closing socket
 --Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist.
vsocket.cpp : closing socket
 --Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist.
vncserver.cpp : KillAuthClients() done
 --Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist.
vncserver.cpp : KillUnauthClients() done
vncserver.cpp : ~server m_pDSMPlugin = NULL 
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6867
Joined: 2004-04-23 10:21
Contact:

Re: "accepted connection from 168.255.224.0"

Post by Rudi De Vos »

VNC listen for new connections until a connection is made.
When you close VNC we do a local connect to the listening port to unlock the listening.

Logging is global and made to debug, if you just want to see the connectionshappen you can use the mslogon.log
168.255.224.0 ? is this the pc local address
David4
8
8
Posts: 24
Joined: 2010-08-11 15:13

Re: "accepted connection from 168.255.224.0"

Post by David4 »

Thank you, I didn't know, that this is a local address. It is not mentioned at https://en.wikipedia.org/wiki/Private_network or perhaps I'm blind.
David4
8
8
Posts: 24
Joined: 2010-08-11 15:13

Re: "accepted connection from 168.255.224.0"

Post by David4 »

Sorry, but I'd like to get more information.
1. My PC has only one IP-address and this is 192.*
2. I can find no info in the web, that 168.255.* is local address range
3. 168.255.224.0 seems to be regularly assigned. Whois returns:

Code: Select all

...
inetnum:     168.255/16
status:      assigned
aut-num:     N/A
owner:       Secretaria de Educacion Publica
ownerid:     MX-SEPU-LACNIC
responsible: Gloria Liliana Luna Fandiño
address:     Viaducto Col. Madalena Mixiuhca, 551, 
address:     15900 - México - CX
country:     MX
phone:       +52 55 36017215 []
owner-c:     GLF3
tech-c:      GLF3
abuse-c:     GLF3
inetrev:     168.255/16
nserver:     DNS1.SEP.GOB.MX  
nsstat:      20200217 AA
nslastaa:    20200217
nserver:     DNS2.SEP.GOB.MX  
nsstat:      20200217 AA
nslastaa:    20200217
created:     19941025
changed:     20140902

nic-hdl:     GLF3
person:      Marco Antonio San Juan Rivera
e-mail:      marco@SEP.GOB.MX
address:     Viaducto Col. Madalena Mixiuhca, 551, Magdalena Mixihuca
address:     15900 - México - CX
country:     MX
phone:       +52  5536013315 []
created:     20080619
changed:     20170107
Otherwise, a portscan of 168.255.*.* returns nothing... But I'm no specialist, that's why I'm asking.
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6867
Joined: 2004-04-23 10:21
Contact:

Re: "accepted connection from 168.255.224.0"

Post by Rudi De Vos »

Please check mslogon.log to see who accessed the system, it's not normal that a unknown ip get access.
m_pDSMPlugin = NULL
You are not using encryption, using the dsmplugin you can have a long password.

The default 8 char unencrypted vnc connection is only suitable for LAN, not when you are exposed to the internet.
Post Reply