Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Failed to connect to server

Post Reply
Nuno18
Posts: 2
Joined: 2021-02-19 12:58

Failed to connect to server

Post by Nuno18 »

Hello everyone,

So, i have a problem, when I try to connect to a surface book 3.
The connection can't be established from my pc to a surface book 3, however, from the surface book to my pc, there is no problem at all.

I already tried to turn off Windows Firewall on the surface book, but it doesn't work either. I went and checked manually if the port was blocked just in case, but it's all good.

Both PCs are under Windows 10 Pro version 20H2.

Does anyone know the solution to this problem? Can it be a wrong configuration on the surface book?


Thanks in advance :)
kissson
20
20
Posts: 33
Joined: 2006-06-12 08:52

Re: Failed to connect to server

Post by kissson »

do 'netstat -aon' shows TCP 0.0.0.0:5900 ??
Nuno18
Posts: 2
Joined: 2021-02-19 12:58

Re: Failed to connect to server

Post by Nuno18 »

kissson wrote:do 'netstat -aon' shows TCP 0.0.0.0:5900 ??
Thanks for the response and sorry for the delay.

I executed that command and got the following (link to the screenshot):
https://i.imgur.com/lzxH58w.png
kissson
20
20
Posts: 33
Joined: 2006-06-12 08:52

Re: Failed to connect to server

Post by kissson »

I think it is working, try to connect to 127.0.0.1 on your uvnc server itself.
also check if you select allow loopback only(should not be allowed), check windows firewall on server incoming and client outgoing, allowed apps, allowed ports, allowed ip ranges, and the profile of your network that if the profile of your adapter is private, the allowed rules of the app or port also need to be with private profile enabled, also check switches / routers ACL, etc, try to open the http://<server ip>:port from anywhere see is there ERR_EMPTY_RESPONSE / ERR_INVALID_HTTP_RESPONSE, then it should be working
hope that it will help
Post Reply