Would be nice if winbox had a vertual mode.
For example:
When ping from computer does not reach a distant MT Router, but local router can. (due to misconfiguration [booboos])
Could Winbox have a capability to comunicate with the remote router by accessing ssh on a local router to connect to the remote site.
This would save me a long drive or two.
Todd
In winbox click on telnet and you will see a ssh option, this will allow you to ssh to your remote router. It would be nice to be able to change the ssh port in that option.
you can do hat already
/sy ssh 192.168.25.2 user=user port=45345
have no problems at all using this…
Yes I know, but when using the winbox gui it is not possible to change the port
Just open New Terminal …
I normally use putty, but I will rephrase my comment. For those who are gui orientated, it might be nice if they could put the port they wish to connect to in the ssh option in winbox
If they are GUI oriented, why do they need SSH ? 
Just open New Terminal and SSH from there!
good point…but then by that definition there is no need for the telnet/ssh function (shortcut) in winbox.
I think in reflection Todd is really after a remote winbox as put forward in another thread.
Yes..
Often you can get a connection from within the router, but not from the PC you have connected to the router. It would be nice to have a relay of sorts so that winbox can connect to a remote router by accessing the immediate routers ssh and not a direct from PC ssh.
Why just dont fill menus accessable in terminal and HTTP to WINBOX
USERMAN example
What do you mean by ‘menus accessable in terminal and HTTP’ ?
I think Winbox is pretty easy tool for router configuration.
no USERMAN in Winbox only in HTTP
this would be extremly usefull… none of our CPE units have a routable IP address (it only provides local access to the tower for auto-upgrade purposes). we winbox into the tower and telnet into the customers’s CPE if we ever need to check something. the ability to proxy the winbox session would be very handy, as many issues could be handled by our level 1 staff if we had a simple to use gui for them to look at on the CPE side (command line is a little too much for some of the guys)…
Loads of ways around it already , if your CPEs have a web interface ,
SSH into the tower instead of winboxing , and just forward port 80 over it , then your staff can just put " localhost " in the webrowser .
If your CPE are Mikrotik boxes, just forward port 8291 over the tunnel as well , then you will have winbox and access to the graphs etc.
Just in case anyone doesn’t know how:
Download this :http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe
run it ,
put the ip of the tower where it says " Host Name " at the top
click on " Tunnels" on the left side
For web-based CPE
in the “Destination” box put the ip of the CPE:80 eg 10.1.2.3:80
in the "Source Port " box put 80
click open , login as your usual tower admin user/pass , then put
“localhost” in your webrowser and you should be able to login to the CPE.