The short answer is that you do not need 36920B, the full blown version of NS/3000.
Several years and several versions ago, HP bundled NS/VT with the FOS--what you call the *Thin* version.
You are correct that with HTTP, FTP, SMTP, Telnet, and NETBIOS (Samba), REMESH, Inetd, Berkley Sockets, and much more all available on MPE, the need for 36920B is very small indeed unless you are using a DSLINE to another HP3000. 
However, HP made the mistake of using services only available through NS/3000 to build selected FOS bundled products.
Among these is Java and multi-threading.
HP has provided NS/3000 free to our site because it solved the multi-threading (and Java) problems.

>>> Michael Anderson <[log in to unmask]> 07/19 5:03 PM >>>
This post is primarily a reply to Doug Becker's post, but the tail end of it has some questions that will probably be better answered from the collective list.

It has been awhile since I needed to justify the purchase of NS/3000, back in 1996 actually.  At that time HP had more than one flavor of NS/3000. Inbound NSVT was a component of all NS/3000 packages. I think what Doug is referring to (36920B) the full-blown NS/3000 package, and he is correct in saying that 36920B is not needed for inbound NSVT. I think he is correct because HP sales a less expensive version of NS/3000 that will support inbound NSVT. 

Correct me if I'm wrong. I think that you'll need at least the *Thin* version of NS/3000 if you want to be able to accept inbound NSVT connections on your M.P.E. box,.  Are you saying that I can order a new HP-e3000 from HP, and tell them not to put any of that NS/3000 software on it, and I'll be able to logon to that machine using NSVT.

I am also curious about you Java statement, because I recently ask myself what I would possibly need NS/3000 for in the future. With HTTP, FTP, SMTP, Telnet, and NETBIOS (Samba), REMESH, Inetd, Berkley Sockets, and much more all available on M.P.E., why would one want to have NS/3000?  I've noticed some performance issues with NSVT vs Telnet, with Telnet coming out ahead, and HP Advanced Telnet will even be better.  Why do I need NS/3000?

_________________________________
Michael Anderson
Student Services Programmer/Analyst
Spring Independent School District, Houston, Texas, 77090
281.586.1105

>>> Doug Becker <[log in to unmask]> 07/19 12:17 PM >>>
A point of order: On point 2) NSVT (VT-Mgr) NS/3000 is really not required as has been discussed earlier.
NS/VT will work without the purchase 36920B, NS3000/iX license, software, and documentation.

However, it is highly *DESIRABLE* to have NS/3000 for:

     1) Versions of Java prior to 1.2.2 to work properly;
     2) the fast native mode terminal I/O drivers;
     3) the multi-threading to behave.

<humor>
I have no association with www.sourgrapes.com whatsoever.
</humor>

>>> Michael Anderson <[log in to unmask]> 07/19 9:23 AM >>>
Michael,

Do you have a  VESOFT account on your machine? If so, do you have a background job running & logged on to the VESOFT account, maybe called ' BACKG,MANAGER.VESOFT '? 

If yes to both of the above questions, then it is probably VESOFT disconnecting you sessions. 

If no to either question then check the  HPTIMEOUT environment variable. A positive value indicates the number of minutes the CI waits until the session is logged off.  The initial value is zero, which means no timed reads. It is possible to write a CI script to be executed from a SYSTEM LOGON UDC that will set the HPTIMEOUT var at logon time. If the HPTIMEOUT var is being set you can search UDC files for the source. Another place to check would be SYSGEN>MISC>SE CITIMEOUT, but not as likely as a SYSTEM UDC setting. 

Connecting to MPE using Reflection you have a few options, which one are you using?

1. Serail connection, using of the old serial line (Same one used by the terminal) by plugging it into a COM port on the Win98 machines.

2. NSVT (VT-Mgr) NS/3000 is required.

3. Telnet, start Inetd on the MPE side to enable the Telnet listener.

Depending on which way you are connected you have various places to check for Network related errors that might cause random disconnects.


_________________________________
Michael Anderson
Student Services Programmer/Analyst
Spring Independent School District, Houston, Texas, 77090
281.586.1105

>>> Michael Adams <[log in to unmask]> 07/19 9:56 AM >>>
I'm VERY new to HP 3000 and Reflections. The company where I work used to
use terminals on serial connection, but now wants to use Win98 clients on
the Ethernet 100Mbps network to connect. The connection seems to work, but
SOME users get kicked out of the connection at seemingly random intervals,
while others can stay connected for hours with no problems. I'm sorry my
info is so sketchy at this point: I do not know what version of Reflections
we are using, and I was told that we are not using NS 3000 AT ALL. Any help
would be a lifesaver!!