Hello together,
first of all: The Dude is a great tool, but I think there’s a lack of documentation and support opportunities, at least for the stable version 2.2 (I know I know, it’s free, but there’s still the possibility for Mikrotik to earn additional money by offering commercial support for customers just using dude)!
Now the problem (I’ve read some similar topics, but no one answered the questions inside them):
We run The Dude 2.2 for a customer as service on a remote machine (Microsoft Windows Server 2003 R2 SP2 Standard x64 Edition with Intel Xeon CPU 5140 2,33 GHz and 4 GB RAM) connected with two Gigabit Ethernet IF, both with fixed IPs, one connected to the Internet (via Firewall, of course), the other one connected to the Management Network of the network which is monitored by The Dude. Several Dude clients access the server via both interfaces without problems. Firewall on the internet IF is configured accordingly.
As I’ve read some Dude administration tasks (Panels, Policy stuff etc.) are possible only via login to the local server. Thus I logon to the Monitoring Server via Remote Desktop, start the Dude client and try to connect via the local mode. The result is the client trying all the time to connect and showing the error “Error: Connection to local server failed”.
Trying the same in remote login mode via the both fixed IPs of the server and the localhost (127.0.0.1) IP works, but, of course, that’s still a remote and not a local connection, the administration problems remain. 
Does anyone know a solution for this problem?
Thanx
Gernot
