forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Cannot Tunnel With Win2003 Terminal Server
- This topic is empty.
-
AuthorPosts
-
-
September 1, 2006 at 5:59 pm #9825bschonecMember
Windows 2003 Terminal Server R2 SP1
SqlYog 5.17
When I am an administrator on the computer I can connect via SSH tunnel to a MySQL server behind a SSH enabled server. When I demote myself (and my two other developers) to regular users, SQLyog bombs out with “Unable to start Plink 2:The system cannot find the file specified”. I click OK then get: SSH Error: FATAL ERROR: Network error: Connection Timed out.
These errors are instantaneous and there is no delay between the time I click “Connect” and the time I get error messages.
If I promote the same user to Administrator, the problem goes away. Bug in SQLyog or “Security Feature” of Win2003?
Brian
-
September 2, 2006 at 12:04 am #22203peterlaursenParticipant
“SQLyog bombs out with “Unable to start Plink 2:The system cannot find the file specified”
To my best belief this is not correct. It must be the OS that sends this message an not SQLyog. Alone the fact the the message is instantaneous tells that!
However, this “SSH Error: FATAL ERROR: Network error: Connection Timed out.” error message is a PLINK err. msg that SQLyog 'picks up' and sends to the screen.
And this look pretty weird actually! First the OS tells that plink cannot be started. But obviously it IS started – because if it was not it would not be able to issue an error message!
Isn't it possible to give READ and EXECUTE permission to all (also non-admin) users to plink.exe or the complete SQLyog installation folder? I must admit that I know almost nothing about the privilege system on Windows Server systems. But that could be the issue.
Please report any findings!
-
-
AuthorPosts
- You must be logged in to reply to this topic.