Samba and Terminal Server issues

[MCCALL,DON (HP-USA,ex1)]

Hi Jay,
Well, I don't understand why MultipleUsersOnConnection  = 0 in the registry
of an NT 4.0 Terminal server doesn't do it for you.  I have tested this all
the way from SP3 - SP6, and it has ALWAYS worked for me;  With this value
set to 0, and a reboot of TS after I set it, 
then every ts client that comes to samba thru that TS gets it's own separate
instance of SMBD....  So you shouldn't give up on that parameter - it DOES
work.  Someone else on the list had a problem with it as well, and we went
over and over it; he eventually reset it again, and rebooted, and this time
it worked...  What can I say?

But for W2K Terminal Servers, Microsoft has removed the code that handles
this registry entry - effectively, this registry entry does not exist for
W2k, and they (M$) have so far been adament that there is no need for this
registry 'hack' anymore on Wk2, because they have increased a number of
limits that used to make this an issue for ts clients.  And they have not
been interested in addressing this for Samba.

Sorry I don't have better news.
Don

-----Original Message-----
From: Jay D. Anderson [mailto:jay.anderson at dw.deere.com]
Sent: Monday, April 23, 2001 11:32 AM
To: samba at lists.samba.org
Subject: Samba and Terminal Server issues


I am currently running Samba v2.0.7 on a Sun Ultra-2 dual cpu Solaris 8
server, serving a couple hundred PCs running NT4 and W2K, and about 160
users on four NT4 Terminal Servers with Citrix Metaframe.

I have 135 printers configured on the Samba server, and several shared
file systems.

In order to make Samba work with the Terminal Servers, I used the
registry entry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters]
"MultipleUsersOnConnection"=dword:00000000

However, even with this registry entry, printing to printers shared from
the Samba server would cause the spool service on the Terminal Servers
to hang up, and this problem could only be solved with a reboot of the
Terminal Server.  To fix this issue I put the "nt smb support = no"
parameter in the smb.conf file.  In my experience, the
MultipleUsersOnConnection value of zero didn't work to force a separate
connection for each user, only the "nt smb support = no" parameter would
do this.

The "nt smb support = no" creates problems of its own.  First, AutoCAD
on a Terminal Server has problems opening and saving files to Samba
shares when this parameter is set.  Several attempts must be made to get
past errors about the file only being available read only.

Another problem with using "nt smb support = no" involves W2K Terminal
Server.  Our Terminal Server users all have roaming profiles so we can
use load balancing across the servers.  However, roaming profiles will
not work with W2K Terminal Server from a Samba share when "nt smb
support = no" is set in the configuration.  A message appears on logon
saying the network profile cannot be loaded and a local version will be
used instead.  Without this parameter in the smb.conf file, the network
profile loads on logon and saves on logoff properly.

I recently upgraded to Samba 2.2.0 and tested whether the "nt smb
support = no" was still required, since there have been a few NT4 WTSE
service packs and Samba versions since I originally ran into problems.
The problems came right back without the configuration parameter.

I'm hoping the Samba team is aware of all these issues and that they
will be addressed in the future.  If anyone has input on workarounds for
these issues that I haven't listed, I would be very interested in
hearing them.

Thank you.

--
---------------------------------------------------------------------
Jay D. Anderson                         John Deere Davenport Works
Jay at Deere.com                           P.O. Box 4198
Phone: 563.388.4268 Fax: 563.388.4159   Davenport, Iowa 52808
http://www.dw.deere.com/~hz01930  http://jayanderson.cjb.net





-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba