• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How to get past a NAT?

NuclearFusi0n

Diamond Member
My sister is behind a NAT/router thingy that she has no control over. She is using Windows XP.
I am not behind a NAT. I have full access to the internet, and am using loonix, the OS for loons.

How can I get a VNC session so that I am viewing her computer? I know it's technically possible, but I don't know how to "reverse" the connection so it's her connecting to me even though I am the VNC client.

Any ideas?

NAT= :evil:
 
Originally posted by: NuclearFusi0n
My sister is behind a NAT/router thingy that she has no control over. She is using Windows XP.
I am not behind a NAT. I have full access to the internet, and am using loonix, the OS for loons.

How can I get a VNC session so that I am viewing her computer? I know it's technically possible, but I don't know how to "reverse" the connection so it's her connecting to me even though I am the VNC client.

Any ideas?

NAT= :evil:

Ask her network administrator. He/She will tell you all you need to know.
 
nats are not evil

she needs to have a mapping already setup in her nat when your connection trys to come in (which would require her to connect to you first and then you connect to her) the problem is these mappings time out on a regular basis (usually 1-5 minutes of inactivity) so either she has to constantly keep a connection to you or you have to adjust the routing table in the nat to always hit her box when a vnc request over the right protocol/port hits the NAT.

ps: linux sucks my ass.
 
# Add New Client - This allows outgoing connections to be made from the server to any "listening" viewer. The name or IP address of the target viewer machine can be entered in the dialog. The server will connect to the default listening viewer port, 5500. From version 3.3.5, a different port number can be specified by adding 😛ortnumber after the name or IP address. Connections created this way are treated as shared. See also the -connect option below.


hurray for VNC!
vncviewer -listen -bgr233 -compresslevel 7 -quality 3

😀
 
1) Ameesh is right, NAT != evil, NAT = necessary due to IPv4 sucking nuts.

2) Linux blows for a desktop OS.

3) NF, WTF are you doing using Linux when you obviously don't know squat about networking? Her VNC config has nothing to do with things compared to whether or not the NAT providing device will forward the port to her. Configure her VNC server to whichever port you like, but the router will cheerfully deny your connection attempts until you tell it not to.

- M4H
 
Back
Top