[Samba] NT 4 Issue (Summary)

2005-06-22 Thread Doug Hubbard

Thanks to Wolfgang Ratzka,
The issue is that NT 4 will not map to a subdirectory (and with a Mixed 
NT and 2000 network I can't use SUBST).

Guess I will end up setting up a bunch of shares.

Thanks for the help.
--

*
Doug Hubbard - IT Manager
TrackMaster, an Equibase Company
email [EMAIL PROTECTED] 
Website www.trackmaster.com 
*



VALIDATION CODE TJC


This message is intended only for the use of the Addressee and may contain 
information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended 
recipient, you are hereby notified that any dissemination of this communication 
is strictly prohibited. If you have received this communication in error, 
please erase all copies of the message and its attachments and notify us 
immediately.
Thank you!
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Re: [Samba] NT 4 Issue

2005-06-22 Thread Wolfgang Ratzka

Doug Hubbard schrieb:

The issue appears to be related to mapping subdirectories of the share 


Yes. NT4 as a client OS cannot do that. There are dirty tricks to work
around this limitation, you can do

SUBST F: \\doug-linux\LAN\VOL1

but there are weird side effects if you do so (e.g. subst'ed drive
mappings are not cleaned up automatically as you log off). So this
is not realy something one can recommend.

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


[Samba] NT 4 Issue

2005-06-22 Thread Doug Hubbard

Hello all,
I apologize if this has been asked elsewhere, but I could not find it.
I am migrating to a Samba PDC (from a Novell 3.11 LAN) and am trying to 
get the login scripts set up.
I have my 2000 machine able to connect, map drives and login fine, 
however I am also using NT4 boxes. The issue is that the drive mappings 
(via net use) fail with an error 53 (network name not found) when 
attempting to map from NT.


The issue appears to be related to mapping subdirectories of the share 
as I am able to map to the root of the share (both at the command prompt 
and in the login script), but when I try to map a drive to a 
subdirectory of the share (from either place) I get the error message.

As an example my share is LAN on server doug-linux (I know inventive names)
I can use the command net use F: \\doug-linux\LAN without issue
but the command net use F: \\doug-linux\LAN\VOL1 fails (and yes the VOL1 
directory exists).



I am able to browse through network neighborhood to the directories I am 
trying to map, so it doesn't appear to be permissions related (I am also 
logging in as the same user I do under 2000 and that machine maps 
without issue).


I know I can set up multiple shares on the server so that I can map to 
the root of each and get around this, but I wanted to see if there was a 
better fix (this would be a lot of shares and I would like to keep the 
setup as clean as possible).


I am running Samba 3.0926 on Suse Professional 9.1 and the clients in 
question are NT 4 with Service pack 6 on them.

--

*
Doug Hubbard - IT Manager
TrackMaster, an Equibase Company
email [EMAIL PROTECTED] 
Website www.trackmaster.com 
*
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba