All, I have been using 3.0.24 with no problems, upgraded to 3.0.25rc1 and noticed my profile cant be "found"...it seems like it is using the hostname as part of the filename. I am running samba as a domain controller on Solaris 10 x86 with a windows XP client. For example: [global] workgroup = COOLBONES netbios name = CASANOVA [unix] comment = Unix Stuff path=/d0/unix It is looking for "/d0/unix/Casanova/..." Network neighborhood shows all shares, I can log in (except it saying it can't find my profile because of the above) Very strange....please let me know if you need further details.
Please attach a gzipped level 10 Samba debug log using the following smb.conf settings [global] log level = 10 log file = /var/log/samba/log.%m max log size = 0
Created attachment 2370 [details] Log file from login/net share session Debug information provided
Looks like the client needs a reboot. It's sending DFS pathnames but not setting the DFS bit in smb_flgs2. Jeremy.
Created attachment 2371 [details] Getting better....some DFS/share issues remain Thanks jra....the reboot helped with some shares, but not others. I am getting the same error on "apps", but not "unix", although perrmissions are the same and configs are the same: [apps] comment = Applications path=/d0/apps read only = No guest ok = No vfs object = recycle recycle:exclude = *.tmp,*.temp recycle:keeptree = yes recycle:repository = .trash recycle:touch = yes recycle:versions = yes [unix] comment = Unix Stuff path=/d0/unix read only = No guest ok = No vfs object = recycle recycle:exclude = *.tmp,*.temp recycle:keeptree = yes recycle:repository = .trash recycle:touch = yes recycle:versions = yes
Do you have these shares mounted as "reconnect" ? You might want to explicitly delete them using : net use * /d and then reboot - then re-attach to the shares. Or you can just turn on the dfs root parameter on the server :-). Jeremy.
Thanks Jeremey...you are fast and it seemed to help. I wonder why 3.0.24 never complained before...very strange...but I'll continue to watch it for the time being but looks stable for now. Thanks again!
Closing as a client issue, not a smbd bug. Jeremy.