John Aldrich wrote: >Ahh, you should have mentioned the wireless connection earlier. There have >been a LOT of problems with wireless routers discussed on this list. If you >plug a network cable between the router and the laptop, I think you'll find >that resolves the issue. Maybe check with DLink to see if they will explain >how to fix the problem, but it *definitely* appears to be a problem with the >wireless portion of your router. I think if you scan the archives of this >list for "wireless" you'll find that a LOT of people are in the same boat... >unable to connect over the wireless connection. > John > >-----Original Message----- >From: Simen Lxland [mailto:[EMAIL PROTECTED] >Sent: Wednesday, October 12, 2005 9:38 AM >To: John Aldrich >Cc: vnc-list@realvnc.com >Subject: Re: RealVNC questions about ports and display number > > >OK, done that. But still can't connect to pc2, always get timeout..... >What does eccactly timeout mean? > >I have on pc2 on vncserver properties set up accect connections on >port 5900/5800 (same for pc1) -> is this right? > >Pc2 is by the way a laptob connecting wirelessly to the Dlink router - >does this mean anything? > >I also have other config alternatives at the Dlink router, example I >have an option to specify applications, here is the info text: > >Special Applications >Some applications require multiple connections, such as Internet >gaming, video conferencing, Internet telephony and others. These >applications have difficulties working through NAT (Network Address >Translation). If you need to run applications that require multiple >connections, specify the port normally associated with an application >in the "Trigger Port" field, select the protocol type as TCP >(Transmission Control Protocol) or UDP (User Datagram Protocol), then >enter the public ports associated with the trigger port to open them >for inbound traffic. At the bottom of the screen, there are already >defined well-known special applications. To use them, click on the >edit icon and enable the service. >Name - This is the name referencing the special application. >Trigger Port - This is the port used to trigger the application. It >can be either a single port or a range of ports. >Trigger Type - This is the protocol used to trigger the special application. >Public Port - This is the port number on the WAN side that will be >used to access the application. You may define a single port or a >range of ports. You can use a comma to add multiple ports or port >ranges. >Public Type - This is the protocol used for the special application. > >Another option is Filters > >Filters are used to deny or allow LAN computers from accessing the >Internet. Within the local area network, the unit can be setup to deny >Internet access to computers using the assigned IP or MAC addresses. >The unit can also block users from accessing restricted web sites. > >Is it necessary to have anything on these options? >On 12/10/05, John Aldrich <[EMAIL PROTECTED]> wrote: > > >>Simen: >>You *definitely* need to make sure your router is configured to send port >>"public" 5901 to PC2's "private" 5900. You have to use either :1 or ::5901 >>to access port 5901, because you can't have two machines listening on the >>same IP at the same port number. You already have port 5900 forwarded to >>PC#1's port 5900. >> John >> >>-----Original Message----- >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>Behalf Of Simen Lxland >>Sent: Wednesday, October 12, 2005 7:01 AM >>To: James Weatherall >>Cc: vnc-list@realvnc.com >>Subject: Re: RealVNC questions about ports and display number >> >> >>I'm not sure I undestand what you mean? Shal I in the viewer put >>xxx.redirectme.net::5901? this doesn't work, I'll get connect error >>10060, also when i try in the viewer with ::5091. Why do I need to use >>5901? and is this in the viewer or do I have to do anything by the >>port forwarding and on the vnc-server accept connections? >> >>On 12/10/05, James Weatherall <[EMAIL PROTECTED]> wrote: >> >> >>>Simen, >>> >>>xxx.redirectme.net::5091 should be xxx.redirectme.net::5901. What is >>> >>> >the > > >>>error you get when you "still can't connect"? Still error 10060, or >>>something else? >>> >>>Regards, >>> >>>Wez @ RealVNC Ltd. >>> >>> >>> >>> >>>>-----Original Message----- >>>>From: [EMAIL PROTECTED] >>>>[mailto:[EMAIL PROTECTED] On Behalf Of Simen Lxland >>>>Sent: 12 October 2005 10:40 >>>>To: James Weatherall >>>>Cc: vnc-list@realvnc.com >>>>Subject: Re: RealVNC questions about ports and display number >>>> >>>>Sorry, mispelled. I surely write xxx.redirectme.net:1 or >>>>xxx.redirectme.net::5091, but still can't connect........ >>>> >>>>On 12/10/05, James Weatherall <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>>Simen, >>>>> >>>>>You are entering a URL into VNC Viewer. You need to enter just >>>>>xxx.redirectme.net:1 into VNC Viewer, without the http: prefix. >>>>> >>>>>Regards, >>>>> >>>>>Wez @ RealVNC Ltd. >>>>> >>>>> >>>>> >>>>> >>>>>>-----Original Message----- >>>>>>From: [EMAIL PROTECTED] >>>>>>[mailto:[EMAIL PROTECTED] On Behalf Of Simen Lxland >>>>>>Sent: 12 October 2005 08:19 >>>>>>To: James Weatherall >>>>>>Cc: vnc-list@realvnc.com >>>>>>Subject: Re: RealVNC questions about ports and display number >>>>>> >>>>>>I still can't connect to pc2 from work. When I try out >>>>>> >>>>>> >>>>the vncviewer >>>> >>>> >>>>>>with http://xxx.redriectme.net:1 or >>>>>> >>>>>> >>>>http://xxx.redirectme.net::5091 i >>>> >>>> >>>>>>get error mesage "unable to connect to host: connectin timed out >>>>>>(10060)". >>>>>> >>>>>>Any idea what is wrong? >>>>>> >>>>>>I still get on pc2 this: >>>>>> >>>>>>81.191.xxx.yyy is accepting connections on Display 0 (TCP >>>>>> >>>>>> >>>>port 5900). >>>> >>>> >>>>>>81.191.xxx.yyy is accepting connections on Display 1 (TCP >>>>>> >>>>>> >>>>port 5901). >>>> >>>> >>>>>>For now to control pc2 i use vnc to pc1 and from there winxp >>>>>>remotedesktop, not a ideal solution because of lagging >>>>>> >>>>>> >>>>etc...... Maybe >>>> >>>> >>>>>>I'll try logmein.com for pc2 if I don't solve this issue. >>>>>> >>>>>> >>>>>> >>>>>>On 11/10/05, Simen Lxland <[EMAIL PROTECTED]> wrote: >>>>>> >>>>>> >>>>>>>I finally think I've sorted it out..... >>>>>>> >>>>>>>I uninstalled and reinstalled the vnc enterprise on my >>>>>>> >>>>>>> >>>>>>problem machine >>>>>> >>>>>> >>>>>>>(pc2). Then i checked on both machines (pc1,pc2) using >>>>>>>http://www.gotomyvnc.com/ with this result. >>>>>>> >>>>>>>I will check tomorrow if I can connect on both pc's from work >>>>>>> >>>>>>>Checking you out at IP address "81.191.xxx.yyy"... >>>>>>> >>>>>>>81.191.xxx.yyy is accepting connections on Display 0 (TCP >>>>>>> >>>>>>> >>>>>>port 5900). >>>>>> >>>>>> >>>>>>>81.191.xxx.yyy is accepting connections on Display 1 (TCP >>>>>>> >>>>>>> >>>>>>port 5901). >>>>>> >>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 2. >>>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 3. >>>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 4. >>>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 5. >>>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 6. >>>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 7. >>>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 8. >>>>>>> >>>>>>>81.191.xxx.yyy is not responding on Display 9. >>>>>>> >>>>>>>Scan of "81.191.xxx.yyy" is complete. >>>>>>> >>>>>>>Hit 'reload' or 'refresh' in your browser to scan again. >>>>>>> >>>>>>>On 11/10/05, Simen Lxland <[EMAIL PROTECTED]> wrote: >>>>>>> >>>>>>> >>>>>>>>Check out >>>>>>>> >>>>>>>> >>>>>>http://www.portforward.com/english/routers/port_forwarding/Dli >>>>>>nk/DI-614+/VNC.htm >>>>>> >>>>>> >>>>>>>>I have here configured as private 5900 and public 5900 >>>>>>>> >>>>>>>> >>>>>>(this works) on >>>>>> >>>>>> >>>>>>>>the machine having xxx.100 ip. At the other machine I >>>>>>>> >>>>>>>> >>>>>>have for private >>>>>> >>>>>> >>>>>>>>5900 and the public 5901, this I can't connect to. >>>>>>>> >>>>>>>>I guess it is right, but still I have problems. >>>>>>>> >>>>>>>>As stated both servers connections are set up with 5900, >>>>>>>> >>>>>>>> >>>>>>is this also right? >>>>>> >>>>>> >>>>>>>>On 11/10/05, James Weatherall <[EMAIL PROTECTED]> wrote: >>>>>>>> >>>>>>>> >>>>>>>>>Simen, >>>>>>>>> >>>>>>>>>Have you looked at http://www.portforward.com for >>>>>>>>> >>>>>>>>> >>>>>>details on how to >>>>>> >>>>>> >>>>>>>>>configure your router? >>>>>>>>> >>>>>>>>>The rules below look wrong, since the VNC1 rules say >>>>>>>>> >>>>>>>>> >>>>>>"TCP,5900-5901", which >>>>>> >>>>>> >>>>>>>>>suggests that they are attempting to forward a range of >>>>>>>>> >>>>>>>>> >>>>>>ports, and one that >>>>>> >>>>>> >>>>>>>>>clashes with earlier rules. The first set of rules >>>>>>>>> >>>>>>>>> >>>>>>also look wrong, since >>>>>> >>>>>> >>>>>>>>>they appear to try to forward *from* port 5900 to both >>>>>>>>> >>>>>>>>> >>>>>>port 5900 and 5901. >>>>>> >>>>>> >>>>>>>>>It may be, however, that this is just the way that you >>>>>>>>> >>>>>>>>> >>>>>>router chooses to >>>>>> >>>>>> >>>>>>>>>express them... >>>>>>>>> >>>>>>>>>Regards, >>>>>>>>> >>>>>>>>>Wez @ RealVNC Ltd. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>-----Original Message----- >>>>>>>>>>From: [EMAIL PROTECTED] >>>>>>>>>>[mailto:[EMAIL PROTECTED] On Behalf Of >>>>>>>>>> >>>>>>>>>> >>>>Simen Lxland >>>> >>>> >>>>>>>>>>Sent: 11 October 2005 17:21 >>>>>>>>>>To: James Weatherall >>>>>>>>>>Cc: vnc-list@realvnc.com >>>>>>>>>>Subject: Re: RealVNC questions about ports and >>>>>>>>>> >>>>>>>>>> >>>>display number >>>> >>>> >>>>>>>>>>Here is my config of my Dlink DI-624+ router: >>>>>>>>>> >>>>>>>>>>VNC TCP 192.168.0.100 TCP >>>>>>>>>> >>>>>>>>>> >>>>5900/5900 always >>>> >>>> >>>>>>>>>>VNC1 TCP 192.168.0.101 TCP >>>>>>>>>> >>>>>>>>>> >>>>5900/5901 always >>>> >>>> >>>>>>>>>>VNC TCP Internett 192.168.0.100 TCP >>>>>>>>>> >>>>>>>>>> >>>>5800/5800 always >>>> >>>> >>>>>>>>>>VNC1 TCP Internett 192.168.0.101 TCP >>>>>>>>>> >>>>>>>>>> >>>>5800/5801 always >>>> >>>> >>>>>>>>>>Allow VNC TCP WAN,* LAN,192.168.0.100 >>>>>>>>>>TCP,5900 >>>>>>>>>>Allow VNC1 TCP WAN,* LAN,192.168.0.101 >>>>>>>>>>TCP,5900-5901 >>>>>>>>>>Allow VNC TCP Internett WAN,* LAN,192.168.0.100 >>>>>>>>>>TCP,5800 >>>>>>>>>>Allow VNC1 TCP Internett WAN,* LAN,192.168.0.101 >>>>>>>>>>TCP,5800-5801 >>>>>>>>>> >>>>>>>>>>I can control remotely ip 192.168.0.100, but not xxxx.101 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>On 11/10/05, James Weatherall <[EMAIL PROTECTED]> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>Simen, >>>>>>>>>>> >>>>>>>>>>>By default, the VNC Viewer for Java is served on port >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>5800+<display number> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>i.e. port 5800 for display zero, port 5801 for >>>>>>>>>>> >>>>>>>>>>> >>>>>>display one, etc. >>>>>> >>>>>> >>>>>>>>>>>With your existing configuration of ports 5900 and 5901 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>through your router, >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>you can use a native VNC Viewer and tell it to >>>>>>>>>>> >>>>>>>>>>> >>>>connect to >>>> >>>> >>>>>>>>>>>xxx1.redirectme.net:0 or xxx1.redirectme.net:1 >>>>>>>>>>> >>>>>>>>>>> >>>>to connect >>>> >>>> >>>>>>>>>>to your servers. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>To use the VNC Viewer for Java, you'll need to >>>>>>>>>>> >>>>>>>>>>> >>>>additionally >>>> >>>> >>>>>>>>>>forward ports >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>5800 and 5801, and ensure that the server to be accessed >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>via ports 5801 & >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>5901 is actually configured to use those ports, >>>>>>>>>>> >>>>>>>>>>> >>>>so that the >>>> >>>> >>>>>>>>>>Java applet will >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>connect using the correct value. >>>>>>>>>>> >>>>>>>>>>>I'm not entirely clear why you're using two >>>>>>>>>>> >>>>>>>>>>> >>>>separate no-ip >>>> >>>> >>>>>>>>>>DNS names, since >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>both computers seem to be behind a single router - both >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>names will refer to >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>the same IP address, so the second name is effectively >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>redundant, surely? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>Regards, >>>>>>>>>>> >>>>>>>>>>>Wez @ RealVNC Ltd. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>-----Original Message----- >>>>>>>>>>>>From: [EMAIL PROTECTED] >>>>>>>>>>>>[mailto:[EMAIL PROTECTED] On Behalf Of >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>Simen Lxland >>>>>> >>>>>> >>>>>>>>>>>>Sent: 11 October 2005 10:54 >>>>>>>>>>>>To: vnc-list@realvnc.com >>>>>>>>>>>>Subject: RealVNC questions about ports and >>>>>>>>>>>> >>>>>>>>>>>> >>>>display number >>>> >>>> >>>>>>>>>>>>I have two pc's on my LAN and are trying to connect to >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>them from work. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>I have set up both with static DCHP-adresses, I have >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>mapped the port >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>forwarding (5900 for pc1 and 5901 for pc two) in >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>my router (Dlink >>>>>> >>>>>> >>>>>>>>>>>>DI-624+) and made sure the firewall in the router is >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>accepting these >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>ports. I use ZoneAlarm on both pc's. I have set >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>up VNC-server as a >>>>>> >>>>>> >>>>>>>>>>>>service on both pc's. I use No-ip client on both, >>>>>>>>>>>>http://xxx.redirectme.net on pc1 and >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>http://xxx1.redirectme.net on >>>>>> >>>>>> >>>>>>>>>>>>pc2. >>>>>>>>>>>> >>>>>>>>>>>>I manage to connect to pc one with the >>>>>>>>>>>> >>>>>>>>>>>> >>>>vnc-viewer at my >>>> >>>> >>>>>>>>>>work. But when >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>I try to connect to pc two i get timeout..... >>>>>>>>>>>> >>>>>>>>>>>>I try this url to connect to: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>http://xxx1.redirectme.net:5091 and >>>>>> >>>>>> >>>>>>>>>>>>http://xxx1.redirectme.net:1 - is this right or wrong? >>>>>>>>>>>> >>>>>>>>>>>>What do i have to do to get this to work- seems a bit >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>strange to me >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>why i can connect to pc1 but not to pc2...... >>>>>>>>>>>> >>>>>>>>>>>>Regards >>>>>>>>>>>> >>>>>>>>>>>>Qtip >>>>>>>>>>>>_______________________________________________ >>>>>>>>>>>>VNC-List mailing list >>>>>>>>>>>>VNC-List@realvnc.com >>>>>>>>>>>>To remove yourself from the list visit: >>>>>>>>>>>>http://www.realvnc.com/mailman/listinfo/vnc-list >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>_______________________________________________ >>>>>>>>>>VNC-List mailing list >>>>>>>>>>VNC-List@realvnc.com >>>>>>>>>>To remove yourself from the list visit: >>>>>>>>>>http://www.realvnc.com/mailman/listinfo/vnc-list >>>>>>>>>> >>>>>>>>>> >>>>>>_______________________________________________ >>>>>>VNC-List mailing list >>>>>>VNC-List@realvnc.com >>>>>>To remove yourself from the list visit: >>>>>>http://www.realvnc.com/mailman/listinfo/vnc-list >>>>>> >>>>>> >>>>_______________________________________________ >>>>VNC-List mailing list >>>>VNC-List@realvnc.com >>>>To remove yourself from the list visit: >>>>http://www.realvnc.com/mailman/listinfo/vnc-list >>>> >>>> >>_______________________________________________ >>VNC-List mailing list >>VNC-List@realvnc.com >>To remove yourself from the list visit: >>http://www.realvnc.com/mailman/listinfo/vnc-list >> >> >_______________________________________________ >VNC-List mailing list >VNC-List@realvnc.com >To remove yourself from the list visit: >http://www.realvnc.com/mailman/listinfo/vnc-list > > > It is the HOSTING Server side of the connection with answering that appears to be the problem I have a laptop that can connect as a viewer over wireless but every wireless computer I have tried CANNOT use wireless to answer an incoming RealVNC connection
Steve _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
