Is there some kind of error log that is generated when a connection is lost? to help diagnose issues. I can only connect within a LAN. Can't connect over IPSEC VPN or WAN.
Thanks
Mark
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
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
UVNC2ME error log
-
Rudi De Vos
- Admin & Developer
- Posts: 6867
- Joined: 2004-04-23 10:21
- Contact:
Re: UVNC2ME error log
Not any logging that wel helpto diag the initial connect issue.
Let's explain how uvnc2me makes a connection
----------------------------
server (local ip 10.10.10.1) <->nat router (offical ip 125.125.124.32)<->internet ( access server)
viewer (local ip 10.10.10.1) <->nat router (offical ip 125.125.100.32)<->internet ( access server)
The access server sees a connection from 125.125.124.32 on port X
The access server sees a connection from 125.125.100.32 on port Y
Now, the access server tell the server that the viewer has ip 125.125.100.32 on port Y
and the viewer that the server is on 125.125.124.32 on port X
After this, the server and viewer create an encrypted tunnel between them
----------------------------
Using a VPN, your pc get some other private VPN ip, isolated from the rest.
That's the goal of a VPN, make a secure connection so no routing is allowed.
Insite a VPN you need a simple vnc server/viewer. The viewer connect to the server ip, as both are in the same VPN
no access server is needed.
Using ipsec you also create an encrypted tunnel, access servers are not reachable
WAN should work.
Let's explain how uvnc2me makes a connection
----------------------------
server (local ip 10.10.10.1) <->nat router (offical ip 125.125.124.32)<->internet ( access server)
viewer (local ip 10.10.10.1) <->nat router (offical ip 125.125.100.32)<->internet ( access server)
The access server sees a connection from 125.125.124.32 on port X
The access server sees a connection from 125.125.100.32 on port Y
Now, the access server tell the server that the viewer has ip 125.125.100.32 on port Y
and the viewer that the server is on 125.125.124.32 on port X
After this, the server and viewer create an encrypted tunnel between them
----------------------------
Using a VPN, your pc get some other private VPN ip, isolated from the rest.
That's the goal of a VPN, make a secure connection so no routing is allowed.
Insite a VPN you need a simple vnc server/viewer. The viewer connect to the server ip, as both are in the same VPN
no access server is needed.
Using ipsec you also create an encrypted tunnel, access servers are not reachable
WAN should work.
Re: UVNC2ME error log
I assume if I have dual WAN's with load balancing that I would need to create a static route to the access servers to/from one of the WAN's, to make this work properly.
Mark
Mark
-
Rudi De Vos
- Admin & Developer
- Posts: 6867
- Joined: 2004-04-23 10:21
- Contact:
Re: UVNC2ME error log
You can download a server and host it in your own network.
uvnc2me send a request to both access servers
1) uvnc access server
2) your local access server
instance 1 is behind nat
instance 2 is behind nat by a customer
instance 3 is local, but behind a local nat
1-2, works because both can access uvnc access server
1-3, works because both can access your own server
3-2, fail Not a common access server. 2 can't connect to your access server and
dual natting is blocking server 3 to connect to uvnc access server
uvnc2me send a request to both access servers
1) uvnc access server
2) your local access server
instance 1 is behind nat
instance 2 is behind nat by a customer
instance 3 is local, but behind a local nat
1-2, works because both can access uvnc access server
1-3, works because both can access your own server
3-2, fail Not a common access server. 2 can't connect to your access server and
dual natting is blocking server 3 to connect to uvnc access server