Hi James: Comments below:
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of James IWD > Sent: Friday, February 22, 2008 11:50 PM > To: [email protected] > Subject: Re: Ports and stuff > > > Thanks John > > Ive tried it again going back through everything and Ive used > the default > port of 5900. For security I wanted to use 1650 (randomly picked as > something I would remember) but it only works on 5900 even > though setting it > within the NAT tables the same as 5900. If you want to choose a random port, use something like 59734 for the first PC, 59735 for the second etc. You have less chance ot clashing with a well known port number that way. When you do this you of course MUST change the VNC server port on the PC in question. Example, for PC2, you need to change the port VNC is listening on to 59734. You also need to check that your PAT entries in your router are set. > Anyway, it works > again localy but > correct me if Im being stupid. I want to test it externally. > I would just > simply type my external IP into the connection string ie > a.b.c.d:5900 and > that would enable me to remote to my local machine but via my > ISP...is that > right??? No, its not right. Well, not exactly...you "should" be able to do that but its unlikely your ISP routers will allow it since thae packet trying to enter the network as the same source IP as the destination. Most routers will flag and drop this as this is something crackers do when they are fiddling with systems. The easiest way to test this is to take a PC you are not using in this network, find some free dialup ISP in your area and connect to the internet. Make sure the PC's firewall is off. Now, try and connect and see if it works. > It seems logical but I might be missing something. It is logical, but see above. > If it is right > then why Im I getting still a connection refused. See above. > > > My D-Link Config; > > Name Private IP Protocol > Schedule > VNCServer 192.168.0.151 TCP 5900/5900 always > > My Voyager Config; > > NAT Rule - Detail > NAT Rule Information > Rule ID: 1 > Rule Flavor: Virtual Server > IF Name: ALL > Protocol: ANY > Local Address From: 192.168.0.151 > Local Address To: 192.168.0.151 > Global Address From: 0.0.0.0 > Global Address To: 0.0.0.0 > Destination Port From: 5900 > Destination Port To: 5900 > Local Port: 5900 > > > PS: I only need to remote onto 1 pc 192.168.0.151 so > the other 2 on > the network are disallowed for remote desktop anyway. That should work. Test it like I told you but replace the TCP 5900/5900 with 59734/59734 and you should be sweet. Also ensure you test the VNC server BEHIND the firewall that it is on 59734. Always start testing from where you know stuff works and then work your way out ONE step at a time. Never try and adjust 2 different things at once as you won't know which one didn't work properly if it fails. If you adjust one thing only, its easier to check stuff. Cheers, John > > Thanks > James > > > > ----- Original Message ----- > From: "John Serink" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[email protected]> > Sent: Friday, February 22, 2008 7:00 AM > Subject: Re: Ports and stuff > > > > Hi james: > > > > You need to put a pat entry into your router to forward any > connection > > on > > 5900 to the internal ip of the xp machine. If you. Want to > connect to > > several differnt machines behind the router, you need to > assign each one a > > static ip (do not use dhcp) and set the vnc server on the > first to 5900, > > vnc server on the second to 5901, etc. In the router you > then put in PAT > > entries for 5900 to the first pc, 5901 for ther seconf etc. > > Now, from the internert, if you real ip is say a.b.c.d, the > to connect to > > the first pc you vnc to a.b.c.d::5900, to connect to the second, > > a.b.c.d::5901, etc. > > > > Getthe idea? > > > > Cheers, > > John > > > > ----- Original Message ----- > > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > To: [email protected] <[email protected]> > > Sent: Fri Feb 22 18:26:33 2008 > > Subject: Ports and stuff > > > > Hi list > > > > Im not getting any further forward with remote desktop or this > > realVNC. > > Both > > just refuse connection from the host when I try to connect with the > > client. I > > can ping my machine's external IP address but I cant seem > to get it to > > connect > > at all "Connection Refused". > > > > I have a voyager 205 modem connected via Ethernet cable to my D-Link > > DI-624 > > wireless router. On the other side of that I have a small 3 > workstation > > network which Ive setup to share files between myself and > my fathers pc > > using > > the centre one as a kind of server (not build with server > os just windows > > xp > > pro) This is the one Im trying to remote onto while outside > the network > > (ie > > around my girlfriends). > > > > Ive tried to set the d-link and the voyager 205 to have a > DMZ for this > > central > > computers internal IP but still cant see it on the outside. > Ive allowed > > port > > the ports through and still nothing. I did find something > interesting, > > when I > > turned off Zone Alarm (free edition) the request took > longer as if it got > > further but still no luck. > > > > If I wanted to talk to a computer on the outside and I > write it into > > my > > NAT > > table on the voyager 205 I thought that that pc would be allowed to > > communicate. That didnt work either. Internally everything > is fine I can > > use > > Windows Remote Desktop Connection as well as RealVNC no > problem although > > the > > speed is pathetic on RealVNC compared to WinRDC. > > > > These are all windows XP pc's and my girlfriend has Vista (Which is > > really > > bad > > by the way, cant move the mouse without it asking if the > mouse is ok to > > move!) > > Any suggestions or help on this. Im not sure whats up but I > cant seem to > > find > > a good website that will scan my ports and check whats > going on from the > > outside. > > > > Cheers > > James > > _______________________________________________ > > VNC-List mailing list > > [email protected] > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list > > _______________________________________________ > > VNC-List mailing list > > [email protected] > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list > > > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
