Could someone please post the step-by-step instructions for setting up and monitoring remote dude agents and locations through TCP 2210? I have been able to locate a remote Dude server and I can see it's health, however I cannot seem to generate a remote network map or see the health of any other snmp enabled computers on the remote network. Ideally I would like to setup my dude monitoring to look like the example screenshots I've seen on your website.

There is no such step-by-step guide. We all just have to kind of figure it out ourselves...

Anyone?

Could someone please post the step-by-step instructions for setting up and monitoring remote dude agents and locations through TCP 2210? I have been able to locate a remote Dude server and I can see it's health, however I cannot seem to generate a remote network map or see the health of any other snmp enabled computers on the remote network. Ideally I would like to setup my dude monitoring to look like the example screenshots I've seen on your website.

What do you mean by see it's health? Cannot seem to generate a network map?
I can assure you that it is possible to do all you are requesting. I am sure it is something simple you will be able to get by once you get the 'system'.

Are you trying to 'discover' the network? Does any map display when you remotely connect to The Dude? If you remotely control the PC that The Dude is running on, or operate it from the console of the PC, and run the local client, are you able to operate as expected?

I will try to help if you could give me a little more background info. I cant determine how far along you are in your development. BTW, what version are you running?

Znet

Locally from my server (Call it server A), I produce a nice looking network map (Network A) and I see all of my computers, printers and the one dd-wrt router I have. I port forwarded 2210 from the router to server A running the dude. As a test, I then RDP to one of my other networks (Network B) and install the dude there on a server (Server B), I would like to use as my NOC Control center, I stop the local dude server on server B, and then create a network connection to the dude agent, server A on Network A. This works, and I get to see network A from Network B. The problem comes in when I try to add another network to veiw on the same screen. I would like to be able to Have network B and Network A on the same screen along with a few other networks without using the wormhole view.. at least not yet.. I have about 170 servers and about 400 desktops altogether I'm trying to monitor in about 40 locations so the map won't be so big that it can't all be on one screen. I've also got this working through a VPN to one remote location but the overhead is too much for that ammount of networks i would ultimatley like to monitor. The pictures I see in the examples of what the dude can do looks exactly like what i'm trying to do. I can see that there may be an order in which things are created but After I get that first network connected I'm lost when I try to add more. Which is created first? a network? Then a submap? or am I already creating a submap? this is what I mean by a step by step, given my scenario of 2 or more networks on the same screen, I'm looking for the order in which I create things to make that happen.
Thanks for taking the time to help!
I hope this was clear, I've been trying to get this working for weeks.

I'm also trying to fathom exactly how the 'agent' function works and what it can (and cannot) do. For the sake of discussion let's assume I have a dude server on my main "local" network and one at another site "remote" network.

I've worked out the following so far:

1) I can add the remote network's dude server as an 'agent' in my local dude settings (Settings > Agents). Once this is done, I can (manually) add devices on the remote network *individually* to any of my *local* maps (or submaps) and set the remote dude server as the 'agent' to do the polling. If a remote device goes down, my *local* dude reports it (i.e. device on my *local* map goes red). It appears though that I have to add *each* remote device I want to monitor to my *local* map *separately* (and set the 'agent' it uses to the remote dude server).

2a) Completely separately, I can also add the remote dude server itself as a device on my local map. If, in the device settings, I set it to monitor the 'dude' service then, as expected, if the dude service *itself* on the remote dude server stops then it alerts on my local map. Ergo, I know if the remote dude server is alive or not, which is good.
2b) Also, if I 'tick' the 'Dude Server' box in the general settings of the device I can right-click on the remote dude server on my local map, select 'dude' and my dude client (on my local PC) will connect *separately* (in a new window) to the remote dude server and show me it's own maps, config etc etc. However, this is of course completely separate from my connection to my local dude server, even though I can see both (in different windows) on my screen at the same time.

But...

What I *really* want to do is to be able to set up the remote dude server (i.e. all the remote network devices on a map on the remote dude server, so that it can locally monitor and admin it's own network as a standalone dude installation) and also *automatically* have the entire map (or submaps) propagate back to my local dude server (as local submaps). I.E: I want to put a 'submap' icon on my local dude map which represents the live status of a map (or submap) on the *remote* server. Then, when I 'open' that map it then automatically opens the map as it appears *right now* on the remote dude server.

Basically, I want to create all the actual maps and devices just *once* (on the dude server in the relevant network) and have them propagate to a main dude server. I don't want to have to create devices and maps twice (such as once on the remote server for local usage, then again on my own local dude server). If I modify the map on the remote server, I want the local server to automatically pick up the change within it's own local map structure (where the remote server is a submap of the local server). I want to do this because I want/need the remote dude server(s) to be able to report on (just) their own local network(s).

[ Does that all make sense ? ]

Is it possible for dude to do this? If so, I can't find how to do it (no docs!. If not (and we just have the functionality outlined in 1/2a/2b above) can it be considered for a future feature?

(Otherwise, am liking the latest beta... !!

S.

I'm not sure if you figured out what you need to do, but it is quite simple. I setup a central dude server that runs as a service on a old 533mhz box running XP Pro(Fileserver). I then make sure the machines that I use to monitor the servers are not running dude locally and only connect securely to the dude server(Fileserver) to view the maps. I have scanned my local Cable broadband subnet to see how many users on are at peek times.

It's nothing to put an image behind these...I just need to draft the layout of my home and a few neighbors who are vlanned to me and it looks all nice a pretty.

Let me know if what I have is similar to what you are trying to do. The only added a few links and the static network to my local home network map...dude discovered everything else; once I set the subnet to discover.

I can do a howto...I'm far from an expert with this software, but I do have a decent grasp on it's functionality.