samba - Feb 2002 - Outlook XP on NT 4.0 Terminal Server Edition & Samba

To start with, I'd like to praise the entire Samba Team, Samba 2.2.3.a
compiled and installed perfected. I wish all vendors could do that good of
job. Great documentation too!  KEEP UP THE GREAT WORK.

Now that the "cheese" is over with...

I posted a problem the other day concerning the funtionality between Outlook
XP .PST files and Samba 2.2.2 & 2.0.7 on Solaris 2.6

As it turns out, we were able to access the .PST file correctly from Outlook
XP loaded EXACLTY the same way on a stand-alone PC.  The .PST file was being
writting to a Samba server, two of them actually, 2.2.2 and 2.0.7.  At first
we chalked it up to be totally Outlook XP's fault (that would be easier to
do), but after installing Samba 2.2.3a on a Solaris 8 [10/01] workstation we
WERE able to read and write to the .PST files in our home directories
without any problems.

Though testing is not yet totally complete, it looks hopeful.  Unfortunately
we don't understand what the difference is which made the difference.  I
hope this information helps somewhat.

Conditions:
Accessing files on a Solaris 2.6 [Samba 2.07 & 2.2.2].  All works great,
UNTIL...
Accessing Outlook XP .PST files FROM a Windows NT 4.0 Terminal Server
Edition, Metaframe 1.8 server.  All OTHER functions "appear" to work
fine
however.  When "Sending/Receiving" email in Outlook XP, we get an
access
denied message, though we could delete email out of the personal folder.
Weird!

Loaded Samba 2.2.3a on Solaris 8 (Rel. 10/01) server, Outlook XP works fine.
(within Microsoft's standards)

I don't believe the smb.conf files are the cause of it, nor the unix
permissions.  At first we suspected the Delete permission in NT not being a
UNIX permission.  But, that's silly, isn't it?

Please advise if you need more info.

WHAT I REALLY NEED NOW
=====================
I'd like to double check with you guys to see if the following errors are a
problem.

I have had my fair share of outlook problems, even had microsoft tell me
"shit happens" when I had a 400mb pst file currupt on it's own. 
There
is a few other things that I've found can cause "stupid" problems
with
outlook.

1. Have you scanned the PST for errors?  I've had TONS AND TONS of
stupid little errors happen until I scanned the pst a few times and
fixed all the errors that crop up.  An outlook PST will get errors in it
if you look at it wrong...drop of a hat, bang, errors in pst.
2. You you deleted and re-created the OUTLOOK profile on the machine?
I've actually had the outlook profile get corrupted, causing weird
things like the program working for exactly 5 seconds and then closing.
You can't delete this by deleting the shared profile, you need to go
into outlook and delete the profile in there.
3.  In my experience in my company, I would NEVER put a PST on a network
share ever again.  I've had some people that would work find for years,
and others would just ALWAYS have problems with errors in the PST and
other things.  I only managed to clean up the problem by moving everyone
to the exchange storage. 

Probably not the answers you want, but I wanted to chime in after all
the headaches outlook has given me over the years.

-----Original Message-----
From: Scarff, Chris J Mr (GD) 513TH
[mailto:scarffc@MI513.gordon.army.mil] 
Sent: Tuesday, February 26, 2002 1:49 PM
To: 'samba@lists.samba.org'
Subject: [Samba] Outlook XP on NT 4.0 Terminal Server Edition & Samba


To start with, I'd like to praise the entire Samba Team, Samba 2.2.3.a
compiled and installed perfected. I wish all vendors could do that good
of job. Great documentation too!  KEEP UP THE GREAT WORK.

Now that the "cheese" is over with...

I posted a problem the other day concerning the funtionality between
Outlook XP .PST files and Samba 2.2.2 & 2.0.7 on Solaris 2.6

As it turns out, we were able to access the .PST file correctly from
Outlook XP loaded EXACLTY the same way on a stand-alone PC.  The .PST
file was being writting to a Samba server, two of them actually, 2.2.2
and 2.0.7.  At first we chalked it up to be totally Outlook XP's fault
(that would be easier to do), but after installing Samba 2.2.3a on a
Solaris 8 [10/01] workstation we WERE able to read and write to the .PST
files in our home directories without any problems.

Though testing is not yet totally complete, it looks hopeful.
Unfortunately we don't understand what the difference is which made the
difference.  I hope this information helps somewhat.

Conditions:
Accessing files on a Solaris 2.6 [Samba 2.07 & 2.2.2].  All works great,
UNTIL... Accessing Outlook XP .PST files FROM a Windows NT 4.0 Terminal
Server Edition, Metaframe 1.8 server.  All OTHER functions "appear" to
work fine however.  When "Sending/Receiving" email in Outlook XP, we
get
an access denied message, though we could delete email out of the
personal folder. Weird!

Loaded Samba 2.2.3a on Solaris 8 (Rel. 10/01) server, Outlook XP works
fine. (within Microsoft's standards)

I don't believe the smb.conf files are the cause of it, nor the unix
permissions.  At first we suspected the Delete permission in NT not
being a UNIX permission.  But, that's silly, isn't it?

Please advise if you need more info.

WHAT I REALLY NEED NOW
=====================
I'd like to double check with you guys to see if the following errors
are a problem.