There are a few factors that could be causing this. The most obvious
one is if you are not running a Server OS on your share, it has a
limited number of connections. OS X allows for only 10 AFP connections
at once, OS X server allows unlimited. Same thing with Windows XP/Vista
they only allow 15 connections to SMB shares unless you are running
either an Open Source OS or a server OS for your share.
The other thing that could happen, and this happens to me on my network
sometimes, is that your server could be getting pounded with too many
clients and it will refuse connections. I know that both the javad and
mysqld processes eat up tons of resources and max out our server at
times when all of our 6,000+ clients are connecting. I had to stagger
out the check in times for all casper clients to remedy this, until we
get a bigger badder server in our back bone.
The other factor that I think are part of this is bandwidth. I know
that when I browse through a policy log I will see that all subnets will
have a small percentage of failures at time, and almost all the failures
are due to them not being able to mount the share or run the script, but
on the very same subnet there are tons of clients that successfully get
the policy so I know that the package and script are present and
working. This could also be due to our heavy laptop user base and users
can simply shut the lid and walk around with their laptop which also
kills the ssh session. I know when our bandwidth gets thin, it
sometimes times out the connections.
Thomas Larkin
TIS Department
KCKPS USD500
tlarki at kckps.org
cell: 913-449-7589
office: 913-627-0351
