Matt,
I also uses PC Anywhere to get to my Netview Server.
Netview client over WAN is definately NOT an option.
Most of the client to Server traffic is Netbios over
TCP (SMB), it is nowhere close of being efficient. I
did some traffic analysis on the Client to Server
Traffic, I saw 3-5KB/sec updates, that raises you WAN
overhead on a T1 by about 4%. I am hopping two
routers to get to my Netview Server box over high
speed FDDI links. I think the the latency from the
hops will causes serious response time problem.
PCAnywhere is probably the best option for remotely
administer Netview. Not that I am a avid supporter of
PCAnywhere, it's an app that best suited for strictly
getting to the GUI, also probably most ban for the
buck.
Hope this helps
Xu He
--- "Clifford L. Crane" <Cliff_Crane@CARGILL.COM>
wrote:
> Another option to consider is pcAnywhere from
> Symantec. I use it via
> dial-up with good success. It has a muriad of
> security options so that
> your console is not left wide open to hackers also.
>
> cc
>
> -----Original Message-----
> From: MattM@DATACOM.CO.NZ
> [mailto:MattM@DATACOM.CO.NZ]
> Sent: Tuesday, July 13, 1999 11:53 PM
> To: NV-L@UCSBVM.UCSB.EDU
> Cc: MattM@DATACOM.CO.NZ
> Subject: Remote management of Netview/NT
>
>
> 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
>
> ATTACHMENT part 2 application/ms-tnef
name=WINMAIL.DAT
===
Xu He
Consulting Services Engineer
Network Solutions, Inc
http://www.netsol.com/consulting
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|