Re: maximum number of sessions


I am interested in the maximum number of sessions not connections. You are
able to have multiple connections to a xp pro machine, each connection
from the same computer does not constitute another session. The maximum
number of sessions allowed on an XP machine is 10. That is not the maximum
number of connections. I.e I can have 15 mapped drives from one machine to
another and only 1 session is created, I can have 7 machines connecting
to the xp po machine each with 15 mapped drives and only 7 sessions will be
created. The problem occurs when we map drives from machines using both
ipadresses and host names, then two sessions are created per machine.

This is an academic discussion now, as I have changed all the mapping to use
an ipaddress, however I noticed when we use network neighbourhood to connect
from machine "A" to machine "B", machine "B" shows an additional session,
even though machine "A" already has mapped drives to machine "B".

In that case it may be better to map all the drives using host names rather
than ipaddresses as using network neighbourhood would then not create an
additional session.

I was really interested to know why mapping using host names and ipaddresses
creates 2 sessions. It may be that I need to post this query at a networking
type forum, what do u think.

Your comments would be appreciated.

Also can you point me in the direction of some NAS software distributions.


Douglas Taylor

"Richard G. Harper" <rgharper@xxxxxxxxx> wrote in message
NAS and SAN storage devices generally run one of the free Linux
distributions (heavily customized for the device in question, however) and
are configured as full-blown servers. If there are connection limits they
will be hardware bound, not software bound.

As for the other question - if you have one connection to \\server\share
and one to \\ser.ver.ip.addr\share that's two connections. If you have
one connection to \\server\share and one connection to
\\server\anothershare that's also two connections. That's just how it

Richard G. Harper [MVP Shell/User] rgharper@xxxxxxxxx
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ...
* HELP us help YOU ...

"Doug Taylor" <dtaylor@xxxxxxxxxx> wrote in message
Thanks for your response but it doesnt answer my question. I would still
like to know why mapping to an ip address creates an additional session
to mapping to netbios name when you are connecting from the same clinet
machine, and does each of these sessions contribute to the maximum of 10
concurrent sessions.

Can u explain why a NAS or SAN storage unit would help, as I thought they
still ran some sort of OS and therefore had access limitaions based on
licensing etc.


"Richard G. Harper" <rgharper@xxxxxxxxx> wrote in message
The answer is to deploy an actual server of some sort rather than try to
fiddle with running a client OS as a server. If all you need is a big
box that everyone can connect to (it doesn't need to run any services or
software) consider a NAS or SAN storage unit.

Richard G. Harper [MVP Shell/User] rgharper@xxxxxxxxx
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ...
* HELP us help YOU ...

"Doug Taylor" <dtaylor@xxxxxxxxxx> wrote in message

We have 6 pcs connecting to a 7 pc we call our server. The network is
to peer all the machines including the server are running windows xp
Since adding the seventh machine to the network we are unable to map
to the server from different machines intermittently. When mapping
from dos
using the "net use" command we are told that the maximum number of
connections has been reached. When I look at the server and run the
session command (or go through computer management sessions) we can
the ten connections, but it is showing multiple connections for the
computer. We disconnected the sessions and browsed to the server
network neighborhood (or run \\server) and Net session shows one
connection. If we then map a drive to the servers ip address we see
session being created.

Are these really two connections and are we really exceeding our limit
ten users?
Why does mapping a drive using the net use command and the ip address
net use v: \\\data create one session and on the same
using net use g: \\server\data create another session.
If we map any more drives future sessions are not created.

Any help would be appreciated.



Relevant Pages

  • RE: Terminal server exeeded the maximum number of allowed connections
    ... server, please perform the following steps to see whether other users are ... Remote Desktop connections yours? ... double-click RDP-Tcp in the Connections folder and click the Sessions tab. ... Microsoft CSS Online Newsgroup Support ...
  • ANNOUNCE: new module: Ingres::Utility::IIMonitor
    ... services of Ingres RDBMS through an object-oriented API. ... A very handy feature is the parsing of user and system sessions (SHOW ... # create a connection to an IIDBMS server ... # is the server listening to new connections? ...
  • Perplexed by SMTP Current Sessions queue
    ... Checked the current sessions queue and there were over 50 sessions all ... The connections were via our offsite Backup mail server. ...
  • RE: Multiple entries of the same user under "Current Sessions"
    ... FTP clients, or through the command-line? ... you may well see multiple entries in the 'current sessions' list that ... several sessions open simultaneously.) ... I will see 2 connections, ...
  • Re: Exchange 2003 SMTP Current Sessions
    ... Also, I was asking really about the SMTP sessions themselves, long before ... Use a RBL if you must, but pick the one you use with care. ... RBLs don't block spam, they block connections. ...