Hi all,
I am currently looking at ways to manage and monitor the Netview server from
remote locations over a WAN. As I see it, there are several options
available to me, but there are limitations as follows:
1. Web client - From the testing I have done, the web client does give a
nice overall view of the network, but lacks some functionality and ease of
use that the Netview console provides.
2. Netvew Client - This option provides all the functionality I need, except
as James Shanks has mentioned in the past, it is not designed to be run over
a WAN, as a lot of bandwidth is consumed with Client-Server gui updates.
Testing also confirms this is slow over a WAN.
3. Netview as an Attended MLM - This is probably my ideal option (from what
I have read), except that configuration from a Netview/UNIX box is required,
which I don't have access to.
With this feature, can I install an NT Attended MLM monitoring a clients
entire WAN reporting to a Netview/NT Central Manager, or do I require
individual NT Attended MLM's to manage each local subnet?
4. Windows Terminal Server? - I have been looking into installing Netview/NT
on NT 4.0 Terminal Server Edition. This gives excellent response times
compared to the Netview Client over a WAN. Unfortunately from my informal
testing, terminal server clients do not seem to recognise server daemon
status, saying that no daemons are running, when they are actually running.
Also there are a few problems with event and snmpcollect database locks from
clients, but overall the server seems to operate as it is supposed to. Has
anybody else tried this terminal server approach?
Does anybody else have any comments regarding remote Netview management?
Regards,
Matt Moore
|