Tony said in one message...

> If you do a NETCONTROL STATUS you should see the default of
> 360 as the maximum node names, is this on the right track or just a
> coincidence??

Tony -

I can't find exactly what you are refering to, but this is the summary
section from an NSCONTROL STATUS:

661     SERVER      MIN    MAX  ACTIVE RESERVED DEBUG  PIN JOBNUM STATUS
662
663     HPIPNS        0  32767       0        0  OFF
664     RASERVER      0    300       0        0  OFF
665     IASQLSVR      0  32767       0        0  OFF
666     NSSTATUS      0    300       0        0  OFF
667     LOOPBACK      0    300       0        0  OFF
668     VTSERVER      0    500     338        0  OFF

As you can see, we are well below the VTSERVER maximum.  Can you cut and
 paste the default of 360 that you are referring to?

---------------

In another response Tony says:

> Another thought is that the number of VT connections has
> been set to a number close to 360. Look in NMMGR at path >
NETXPORT.GPROT.TCP and check the # of connections.

We looked at that and increased it (TCP connections) from 512 to 640.  I
reset it with a NETCONTROL UPDATE=ALL;NET=LOOP and  NETCONTROL
UPDATE=ALL;NET=LAN1

And since that setting in NMMGR is before you get to the network
interfaces, I'm not sure if that is the right way to reset that setting.

We don't want to shut down NS services with all of the users on right
now.

We can leave it at the 640 and have the operators tonight take the LAN
down and back up.  Or is there some other *noninvasive* way of resetting
this with users on?

Other or more ideas?

/alan
[log in to unmask]