Hello andy... sorry to say but you need to do more to your router before this will work. the Address 192.169.x.x are reserved for local addresses (theese are not valid internet addresses and will not be routed throught the internet)
Included you'll find my standard answer: And the answer is that you'll need to configure your router. yes, the 2 PC's work, behind the router, you got a private network (with private addresses). So there it works, but no one on the internet would know where to send 192.168.x.x address too, since they are not allowed on the internet. I you can have changes made to the router, then I would suggest that you set up an SSH server on your pc, and have TCP port 22 on the router redirected to your pc. This will allow you to use vnc over an encrypted tunnel, which I think is required in in your case. But talking about this is worthless if you can't have changes made to the router... On Wed, 2003-03-05 at 04:23, andy wrote: > Here is my problem, > > I am military and trying to use the VNC program to help out with problems the > family may not be able to handle while I am away. My home computer has a > shared DSL connection between my computer and my son's computer through a > router set up. Before I left i made sure I could talk from one computer to > another and it seemed to work just fine. Now that I am away, I can't connect > to either computer. The IP address to me looks a little funny and may be > giving the problems but it did work from computer to computer. they are > 192.168.0.2 and the other compuer is 192.168.0.3...usually you have sets of > three on the numbers and the 0.2 or 0.3 may be confusing it or something. I > would appreceate any help anyone can offer. I have used the viewer program to > access other computers already but just can't access my own. > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list > Here we go again.... again... again.... Okay, your situation +------+a b+--------+c d+-----+ & PC1 +-------+ Router +--- Internet --+ RPC & +------+ +--------+ +-----+ a- Your private address, b- Router private address c- Router internet address d- RPC internet address Okay, Question 1: Is there anyway I can get from a PC in the Internet (RPC) to PC1 without going through Router? Answer: NO, the machines are wired that way! if you want to send packets to PC1 they are going to have to go through Router, so you are going to have to send them to router, so you are going to have to know Router's internet address. Alternatively you can hook up PC1 to the internet in a diferent way, (one where he doesn't go through another computer to get to the internet in other words gets his own internet address). Question 2: Can I get from the Internet to PC1 (Okay thru Router since I have too) with out doing anything to Router? Answer: NO. Router has to read the packages off the the internet connection, modify them, and send them on to PC1. To do this Router must be able to recognise which packets to route, and to send them to PC1. This has to be setup on Router. YOUR QUESTION: Is there a way to get a vncviewer (running on a machine in the internet called RPC) to show PC1's screen. ANSWER 0: Yes, there many ways to do this. ANSWER 1: start a vncviewer on RPC, connect to Router. Once on router, start a vncviewer connect to PC1. Use to your heart's content. This method is often overlooked. It's a little slower than messing with tunnels, ip NATing and Co. but you don't have to mess with tunnels, ip NATing and Co.8-) Additionally I've found that it is faster than one would expect. The reason being that the PC1<->Router connections is usually 10mbs or better while the Router<->RPC conneciton is 128Kbs or less. (In English, the PC1's screen is copied via a fast connection to Routers screen. From there it is copied via a slower connection to RPC. On RPC as you wait for the slow copy... you can barely notice that an additionaly copy was made.) YMMV. (Your milage may vary) advantages: no tunnels/ip natting & funky stuff like that. disadvantages: No security. A little sluggish. ANSWER 2: On RPC start a VNCViewer in "Listening mode". Then on PC1 use the "Add New Cient" function to connect to it. This works because Router is already setup to route PC1 traffic to the the internet. How do I know? Well PC1 is connected to the internet, so obviously, Router is setup to "Route" packes for PC1 out to the internet and back! The problem here is that PC1 must be the initiator. Which is okay for remote support since the user on PC1 can initiate the connection, but is a little more dificult when nobody is around PC1. Of course you could write an autoexec batch file and modify your bios to start your office pc at the bank in the middle of the night, when it is dark, between the watchmans rounds, But then Dective Dick Tracy (Starring Brad Pitt).... Upps, got carried away there... advantages: No changes to router(did I say that was impossible?) disadvantages: Still no security, Need insider help. ANSWER 3: Messing with Tunnles, NATing and Co. (Tell Router to "Route" the necesary packets to PC1, and back.) There are many many many many methods of doing this so to help you here you are going to have to tell us what hardware / software system Router is (ie. Linksys adsl router, Checkpoint firewall, window 98, Linux 2.2.12, MAC OSX, what ever) and weither or not you have permision to mess with Router. advantages: security, compression, SPEED! disadvantages: Messing with Tunnles Nating and Co. 8-) Hope this helps you (and others) to understand a little bit about what you are trying to deal with here... _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
