![]() ![]() Beyond that, the most common error is this, which appears when you try to VNC to localhost:5900: Most 6.44 connections I tested while writing this works fine. We're blocked out of almost every untrusted computer running a mikrotik version greater than 6.44. This worked for the first month I worked here, but since late August things have started falling apart. ![]() I have attached a dummy example image of our tunnel setup. By doing this we are able to connect to the remote computer via localhost:5900. Our method was simple: we use PuTTY to set up a tunnel to the computer we want to control via Mikrotik's IP, and mirror the VNC port on the target computer to a port on our own. TightVNC is especially crucial with the computers we use with advertisement screens, as store employees aren't trained to fix those issues.Įverything was fine two months ago, but as Mikrotik has started updating itself to 6.47, 6.49 and so on we've noticed that we can no longer access any of the untrusted computers on the network managed by Mikrotik. ![]() Every machine my departement sends out (I am in IT) we put TightVNC on so that we can access it fairly quickly should the need arise. Here's our situation: We have a bunch of stores, and each store has a Mikrotik router managing the network, which is divided into Trusted and Untrusted networks, fairly standard. I give up! After weeks of pondering and testing we are at out wits end so I turn to you kind sages of the forum for help. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |