Hi Joerg,
pst are a special kind of files, and its not not recommended hosting
them on network shares, see technet, cause they get corupted
But i know many people do it.
So keep clear that the psts are not growing very large ( under 1G is ok
) stop any vfs antivir at the pst shares,
play with lock parameters.
i have one costumer who is hosting his pst on network shares with samba
3.0.14 and there is no bug with it.
I dont have testet it with latest samba.
But i am nearly sure this is not a samba problem,
i recommend you install a kolab server which works nice to outlook.
pst where never thought to be hosted on networks.
For testing copy a working pst file to the place ( share ) where the not
working one is hosted and try to open it, if this works you know the pst
got corupted , there are a few tools by ms to reconstruct such files (
search technet ) but do it by copy them to a local client.
In your scenario you should have daily backups of the psts anyway
But i read a lot about problems with solaris samba , maybe the bug is
only in solaris samba, as workaournd switch back to former samba version
Best Regards
Jörg Nissen schrieb:
You should give us a look at your smb.conf. AFAIK from my very own
experience: 3.0.21c somehow behaves different from 3.0.20 with the same
smb.conf. Maybe you have to set some values which did not have to be set
before.
MfG
Jörg Nissen
----- Original Message ----- From: "WolverineJR" <[EMAIL PROTECTED]>
Newsgroups: mailing.unix.samba
Sent: Friday, March 10, 2006 9:40 AM
Subject: URGENT!!!!! Problem: outlook.pst with samba 3.0.21c!!!!!!!!
Hello Samba-Gurus!!
Following really really important problem:
Yesterday evening, we have upgraded our Solaris9-Samba-Fileserver from
Samba-Version 3.0.11 to 3.0.21c. All worked fine.
But today, we have following problem:
Some users, which outook.pst-file is situated on the samba-fileserver
in their home-share, cannot send or get mails via Outlook2000 und
Outlook2003.
When we try to change the path to the PST-file, we get the messages,
that the file cannot be accessed.
Here is a sample of the samba-log of one of the clients:
[2006/03/10 07:39:03, 2] smbd/dosmode.c:unix_mode(70)
unix_mode(outlook.pst) inheriting from .
[2006/03/10 07:39:03, 2] smbd/dosmode.c:unix_mode(78)
unix_mode(outlook.pst) inherit mode 40700
[2006/03/10 07:39:03, 2] smbd/open.c:open_file(350)
abm opened file outlook.pst read=Yes write=No (numopen=2)
[2006/03/10 07:39:03, 2] smbd/close.c:close_normal_file(308)
FRANKFURT+abm closed file outlook.pst (numopen=1)
[2006/03/10 07:39:03, 2] smbd/dosmode.c:unix_mode(70)
unix_mode(outlook.pst) inheriting from .
[2006/03/10 07:39:03, 2] smbd/dosmode.c:unix_mode(78)
unix_mode(outlook.pst) inherit mode 40700
[2006/03/10 07:39:03, 2] smbd/open.c:open_file(350)
abm opened file outlook.pst read=Yes write=No (numopen=2)
[2006/03/10 07:39:03, 2] smbd/close.c:close_normal_file(308)
FRANKFURT+abm closed file outlook.pst (numopen=1)
[2006/03/10 07:39:03, 2] smbd/dosmode.c:unix_mode(70)
What here stand out is, that samba try to open the outlook.pst - file
with READ=YES and WRITE=NO... this can not be right
Another thing is, that after the samba-upgrade, we don´t get the
absolut pathes from the opened files in samba. In SWAT we only get
something like: outlook/outlook.pst
Normally it should look like: /homes/xxx/outlook/outlook.pst
Does have anybody a solution or idea??
THIS IS REALLY IMPORTANT!!!!
THX!!!!
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
