I just upgraded a server from an older version of samba to the newer 2.2.2. When I login from a win 98 machine with a username longer than 8 characters I get an error that Z:usern~93.bat could not be found. This is only a problem with 2.2.2. Is this a know issue, or did I miss a config option? Do I need to supply more information to help track this issue down? Thanks for the help.
hello, been there... it will just work if you set 'kernel oplocks = no' in your [global] section of smb.conf; at least it did for me... cheers, dragos On Monday 19 November 2001 06:33 pm, Ed Mann wrote:> I just upgraded a server from an older version of samba to the newer > 2.2.2. When I login from a win 98 machine with a username longer than 8 > characters I get an error that Z:usern~93.bat could not be found. This > is only a problem with 2.2.2. Is this a know issue, or did I miss a > config option? Do I need to supply more information to help track this > issue down? > > Thanks for the help.
----- Original Message ----- From: Ed Mann <ed.mann@cp-direct.com> To: samba <samba@lists.samba.org> Sent: Monday, November 19, 2001 8:33 PM Subject: Netlogon Long username> I just upgraded a server from an older version of samba to the newer > 2.2.2. When I login from a win 98 machine with a username longer than 8 > characters I get an error that Z:usern~93.bat could not be found. This > is only a problem with 2.2.2. Is this a know issue, or did I miss a > config option? Do I need to supply more information to help track this > issue down? >This is question I asked _several_ times here and in samba-technical. No replies. And, certanly, I don't want to turn off kernel oplocks.
I just found something funny with that one. I never had a problem have longer filenames and directory's with >8 characters in my netlogon share until.... I install E-Safe Dektop from Alladin. After the installation it would't process my logon.bat files anymore. (Mine are create on the fly according the username...) But when I close all the netlogon stuff I'm logged in but no shares are set correctly and lot's of other stuff then when I just logoff and logon again Everything is processed correctly! I don't have a single problem with long filesnames anymore!!!! I don't know what that happend but aparently windows/alladin is doing something funny with it!. I thought I just lett you know and in the mean time I need to find a solution (other then kernel oplocks = no). Ries