![]() ![]() **.**.13.36 is not responding on Display 9. **.**.13.36 is not responding on Display 8. ![]() **.**.13.36 is not responding on Display 7. **.**.13.36 is not responding on Display 6. **.**.13.36 is not responding on Display 5. **.**.13.36 is not responding on Display 4. **.**.13.36 is not responding on Display 3. **.**.13.36 is not responding on Display 2. **.**.13.36 is not responding on Display 1. **.**.13.36 is accepting connections on Display 0 (TCP port 5900). This port (and port 5800) are opened by the VNC system allowing remote multi-platform console access.Ĭhecking you out at IP address "**.**.13.36". I just went to shieldsup and probed port 5900 and it says: If anyone has any ideas where I might start troubleshooting this, they would be much appreciated. Also I don't know how my iPhone can connect over Edge but I can't ping the dnydns address even using a web-based ping test. What I don't understand is how the crappy iPhone can connect (albeit at an almost unusable refresh rate) but my PC in my office can't connect. When I went on to /help/ I also couldn't ping my dyndns domain name. I can't even ping the VNC server machine (using the dnydns domain name) from my office machine. However, I cannot connect using TightVNC viewer from my office XP SP2 PC. not on the same network as the VNC Server machine. I can also connect using Mocha VNC on my iPhone using the Edge connection i.e. connecting to my home wi-fi that both PC's also connect to. Using the TightVNC Viewer I can remote in from another PC (running Vista Home Premium) on the same network and using Mocha VNC via wi-fi I can remote in on my iPhone on the same network i.e. I've installed TightVNC Server on the home XP SP2 PC, setup a static IP address and DNYDNS and then forwarded the VNC server ports on my home router. Try with the IP address of the computer : ping - I've been trying to get remote access up and running so I can control my home PC from my work office.Try with the FQDN (Fully Qualified Domain Name) : ping.Please check the result of the following commands: Finally, NetBIOS name resolution between your admin computer and the remote machine must be perfect.Enter 10000 (10 seconds) then test again the remote control. This delay is the time between the request to start the "VNC Server / WinVNC" service on the remote host and the first connection attempt on this computer : " Tools" menu, " TightVNC Options", " General" tab. You can also try to increase the delay of synchonization with the WinVNC server (2000 milliseconds by default).For example enter the port 5901, then try again by lauching the remote control. Please try to enter another port number (right click on the remote host, Remote control, Configurer, Connection tab). This message could also appears if a software running at the moment on the remote host or on the administration computer uses the same port than the one used by VNC (default : 5900).Read more : Windows XP firewall - Windows Vista firewall - Windows 7 / 8 / 10 firewall On these both computers, please also accept the TCP port used by VNC. Please create an exception in the firewall of the administration computer in order to accept "vncviewer.exe" and also an exception in the firewall of the remote host in order to accept "winvnc.exe". This message could also appears when a firewall (the native Windows firewall or another one) blocks the VNC software or the port used by this sofware (default : 5900 ).If necessary you should kill this task, then relaunch the connection. So, before launching again a remote control, you may check in the services/process list that the "winvnc" task is not running at this tiime. Indeed, when you stop the remote control, the software take some time (a few seconds) for properly leaving the beforehand established communication between the two computers. This message could appears when you have launched again the remote control too quickly after having finished another one, on the same remote host.Simplify your VNC Installation and Remote Control with IDEAL Administration (installed in 2 minutes) Try IDEAL Administration during 30 days on your network for free! When I try to launch the remote control with TightVNC, I get the "Failed to connect to server" message, and I can't take the control of the remote host. How to configure the TightVNC remote control tool (screen sharing)? How to troubleshoot "Failed to connect to server" message? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |