Filter
Top Products
16
The Terminal Server sees the service name as \\EMONSTER\HOME-SHARE, and not
\\emonster\buffy. If the user spike opens a session on the same Terminal Server and mounts
the home-share using the same procedure as buffy, Terminal Server will use the same service
name as buffy. If both users now access an identical filename on their respective shares using
an application that locks the files (like Word or PowerPoint) then the applications via Terminal
Server will try to lock the same file, and access will be denied to the second user – even though
they are opening different files that exist on their separate home directories. This behavior
appears to be application and locking dependant. Note that non-locking applications (like
Notepad) do not exhibit this behavior, and correctly read and write to the unique files.
The Samba [homes] feature allows the automatic mapping of users to home shares without the
unpredictable behavior described above:
[homes]
comment = user home share
The user connects to the home share using the user name, and Samba tconx makes an explicit
map to the share: