T.R | Title | User | Personal Name | Date | Lines |
---|
4249.1 | | VMSNET::P_NUNEZ | | Mon Apr 07 1997 11:54 | 15 |
| Grant,
W/o exception, the net3101 error means you have no more sessions. To
confirm:
$ search/window pwrk$lmmcp_<node>.log repeat
(be sure to search the lmmcp log that was open at the time). Look for
a message about max clients being reached and "this message will not be
repeated."
They might have clients using more than one session. It's always a
good idea to pad it (and don't be too conservative)...
Paul
|
4249.2 | How does a client use more than 1 session? | OTOOA::GMACDONALD | Its badluck to be superstitious | Mon Apr 07 1997 13:13 | 7 |
| Paul, you're right. That's the problem. Their clients are all using
Windows 95. How does a client use more than one session? Is it based on
the number of network connections?
I'll have them increase the connection limit to about 210 or so.
Thanks. Grant.
|
4249.3 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Apr 07 1997 13:19 | 3 |
| netlogon could be a session
license checking is a session
...
|
4249.4 | Most common in a cluster | VMSNET::P_NUNEZ | | Mon Apr 07 1997 15:00 | 12 |
|
If it's a cluster, making connections using both the alias name and the
specific node name will result in two sessions. For example, say the
alias name is CLUSTER and the cluster nodenames are NODE1 and NODE2.
If I connect to \\CLUSTER\SHARE and get connected to NODE1 and then
turn around and connect to \\NODE1\ANYSHARE, I end up with 2 sessions.
There are other "clients" that can use a session as well - any $ NET
command or ADMIN/PATH session with use a session, for example. Account
replication I believes uses a "session", etc, etc...
Paul
|
4249.5 | | OTOOA::GMACDONALD | Its badluck to be superstitious | Mon Apr 07 1997 15:32 | 3 |
| It is a cluster and they are using the Alias and sometimes specific nodenames.
Thanks. Grant.
|