Re: NV and MS Terminal Service...

2001-07-25 19:00:22
Subject: Re: NV and MS Terminal Service...
From: "James Shanks" <SHANKS AT us.tivoli DOT com>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 25 Jul 2001 19:00:22 -0400
Never been tested nor certified this way.  Even if you get it to work it is
not supported.

James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT

"Kevin Conway" <kconway AT US.IBM DOT COM>@tkg.com on 07/24/2001 12:45:17 PM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com

To:   nv-l AT tkg DOT com
Subject:  [NV-L] NV and MS Terminal Service...

Win 2k Server
NV 6.0.2
Win 2k Pro (laptop)

We have started trying access NV through the Windows Terminal Service and
have found a big problem.  NV is running great on the Win 2k Server box;
but, this changes immediately when we run it through the terminal.

Upon loading NV remotely, the "nv.log" file explodes; growing at
~2.5megs/second.  The errors that appear are as follows:

--- failed to connect to netmon's shared memory segment; error: the system
 cannot find the file specified.
--- OpenMutex failed: the system cannot find the file specified.

These two lines are then followed by an error about a pipe to the "trapd"
 thread, saying that the other end is non-existent.  This "pipe" error is
 then repeated a few thousand times per second.  Of course this fills the
 hard drive rather quickly and renders the server useless....

Any ideas?  NV not compatible with the terminal service? We are stumped....

Kevin Conway
I/T Spec. - Network Integ.
E-Mail: kconway AT us.ibm DOT com

NV-L List information and Archives: http://www.tkg.com/nv-l

<Prev in Thread] Current Thread [Next in Thread>