Re: [Samba] logon drive = Z: causes problems
I left "logon path" to default. This is the config I WAS using: logon script = %U.bat logon path = logon home = \\%L\%U logon drive = U: In most cases it worked OK but with over 1000 users I got too many reports of U drive missing and had to revert back to the old config. Thanks. --- Josh Kelley <[EMAIL PROTECTED]> wrote: > On 12/6/05, Brian Gewin <[EMAIL PROTECTED]> wrote: > > I've attempted many different solutions including the obvious "logon drive > > = U:" but that > proved > > to be very unreliable and caused the U drive to disappear entirely in some > > cases. > > Sorry if this is asking the obvious, but did you make sure that you > set "logon path" (either globally, in smb.conf, or per-user, using > pdbedit or a similar tool) when you set "logon drive"? When we had > logon drive but no logon path set, it caused similar problems with the > logon drive disappearing entirely. > > Josh Kelley > __ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] logon drive = Z: causes problems
"logon drive" defaults to Z:. This causes our XP clients to get Z mapped to their home directory. We already use U for that purpose so they end up getting both U and Z mapped to the same location. Users being users this causes great confusion and there have been times when they've deleted their entire Z drive thinking it was a duplicate copy of U. I've attempted many different solutions including the obvious "logon drive = U:" but that proved to be very unreliable and caused the U drive to disappear entirely in some cases. The only solution I can think of now is to write a batch file that compares the U drive to the Z drive and if they are indentical it will unmap the Z drive. I'm hoping there is a better way or that the Samba team would consider removing that option or providing the ability to disable it. I'd rather not tweak the source, we have way too many servers running different versions of Samba. Thanks. BG __ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Spanish characters & Win98
Here is an example of a foldername containing Spanish characters that I am having problems with on Win98 and Samba: "Thís is a tést Ñ". When copying this folder from a Win98 client to a Samba 2.2.4 share I get the error "You may not be able to access files created in the folder Thís is a tést Ñ". Works fine on Win2K and XP clients and all Windows servers. I suspect I will have to use a Samba Code Page other than the default 850 or create my own. Does anyone have a quick fix for this? Thanks. Brian Gewin The Nature Conservancy -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can't mount Samba share on Linux box, Windows clients
When I encountered weird messages when trying to mount Samba shares on a Linux box the solution was to make sure I had the location of smbmount and smbmnt in my path. On RedHat 6.2 the path is /usr/sbin. I have not seen your exact error before though. Hope that helps. Message: 12 Date: Wed, 27 Nov 2002 10:29:46 -0800 From: Baxter Shepperson <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [Samba] Can't mount Samba share on Linux box, Windows clients OK Hi all. I've got most of the Samba config dialed in yet I still cannot get printing or file sharing going from my main desktop (Debian Sarge). Here's what I tried: root@PlanetExpress:/home/bax# mount -t smbfs -o username=planetexpress,password=tigerlily //printserver/homes /mnt/Samba Unknown parameter encountered: "passdb backend" Ignoring unknown parameter "passdb backend" Any ideas? Printing from CUPS on my Linux box to the Samba box doesn't work either. I hope it's something small or stupid because the Windows clients are running just fine. I appreciate any ideas/comments/ridicule anyone might offer. Baxter Sgt USMC -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba