Assume I have 2 computers inside one and the same LAN.
Ok, in this case I could connect them WITHOUT the help of NAT2NAT
tools. It works fine.
However I would like to test the NAT2NAT service + tools from these
two computers. So is it possible ?
In other words is it possible to establish a NAT2NAT connection
this way
Comp1 -> Router789 -> NH-service -> Router789 ->Comp2
or get the router confused when server and viewer are inside the SAME LAN ?
I am not sure about this because I setup such a scenario and both server
and viewer helper are still in status "Added to uvnc.com..."
even after 30 minutes.
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
NAT2NAT: Testing possible inside a LAN ?
-
Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
It's possible...
I test
Comp1 -> Router789 -> NH-service -> Router789 ->Comp1
Same computer for server and viewer
Keep in mind that the Nat2Nat test (11MAY) is current down, there were erros in the code that needed to be corrected. (The crazy thing is that the dbug version works ok, but the release versions had some error).
New version will be available in a few days.
-Will work also with symmetric nat routers. In case the direct connection is refused, the NH-service will act as gateway (all data need to pass the service).
-SC will be integrated in connectors.
To being able to include SC in the
nat connector without violating any license, SC needed to be rewritten.
A hell of a job, but needed to be able to continue. SC will not longer be called VNC, looking for a suitable name...
I test
Comp1 -> Router789 -> NH-service -> Router789 ->Comp1
Same computer for server and viewer
Keep in mind that the Nat2Nat test (11MAY) is current down, there were erros in the code that needed to be corrected. (The crazy thing is that the dbug version works ok, but the release versions had some error).
New version will be available in a few days.
-Will work also with symmetric nat routers. In case the direct connection is refused, the NH-service will act as gateway (all data need to pass the service).
-SC will be integrated in connectors.
To being able to include SC in the
nat connector without violating any license, SC needed to be rewritten.
A hell of a job, but needed to be able to continue. SC will not longer be called VNC, looking for a suitable name...
-
Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
There are multiple reasons
The new Nat2nat does
*does authentication
*does encryption
No need to dublicate the functions in server and viewer
There are to many options in vnc. Most "dummy" users just don't
see the tree in forrest and find it to complicate.
Nat2nat+viewer+server will have NO options. You just enter
user/passwd and get connected.
Winvnc is based on Realvnc3, the code is huge and some parts
are to complicate for the task. The exe are also to big for fast download.
I have bed someone that i could rewrite a vnc like connection software in
less then a week. The challenge....
Nat2nat and vnc have a different licening. Integrating Nat2nat in VNC
require that Nat2nat also would become GPL. A rewritten server and viewer is no longer bound to GPL.
If direct Nat2nat fails, the connectors now can use uvnc.com as data
gateway. The bandwidth of uvnc.com is limited, rewriting SC allow to
switch to a special encoder when bouncing is used....natural, when people can alter the code a simple connection could overload the server. Because all data between server and viewer is encrypted, the uvnc service can not check the encoder, so limitation need to be done by the connectors.
The new Nat2nat does
*does authentication
*does encryption
No need to dublicate the functions in server and viewer
There are to many options in vnc. Most "dummy" users just don't
see the tree in forrest and find it to complicate.
Nat2nat+viewer+server will have NO options. You just enter
user/passwd and get connected.
Winvnc is based on Realvnc3, the code is huge and some parts
are to complicate for the task. The exe are also to big for fast download.
I have bed someone that i could rewrite a vnc like connection software in
less then a week. The challenge....
Nat2nat and vnc have a different licening. Integrating Nat2nat in VNC
require that Nat2nat also would become GPL. A rewritten server and viewer is no longer bound to GPL.
If direct Nat2nat fails, the connectors now can use uvnc.com as data
gateway. The bandwidth of uvnc.com is limited, rewriting SC allow to
switch to a special encoder when bouncing is used....natural, when people can alter the code a simple connection could overload the server. Because all data between server and viewer is encrypted, the uvnc service can not check the encoder, so limitation need to be done by the connectors.