Server 2003 Share access -- clients get 'read only' errors -- yet permissions appear correct. URGENT!

Hey all,

This is an urgent one, so max points available.

We just upgraded from a NT4 PDC to a 2003 AD based network. All the users had accounts in the AD previously, as iwe had two domains--one for logon, and the other for our Exchange. Now we've downed the NT box, brought up a 2003 file server to replace it, and have the users logging into the 2003 domain. All the data transferred cleanly, and we've replicated the share architecture on the new box, with one MAJOR problem:

Clients see the shares as read-only. Word won't write to the shares, and files such as PABs can't be used due to Outlook requiring write access to them .

I've used the effective permissions tool, which seems to show that DOMAIN USERS have full control. So does EVERYONE. Same thing with the NTFS permissions, and I've (tried to) push those permissions down from the root level of the drive containing the shares.

It's possibly of note that most of the client boxes are Windows 98. Do they need the DS client installed? I figured that if they could log on to the domain, that's good enough.

The users here are approaching revolt, and I'm getting panicky.

Any ideas? Anything I might have missed?


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

First check your *share* permissions. In NT4, when you created a new share, by default the Everyone group had Full access. In Server 2003, this has been changed; new shares will now have only Read permissions for the Everyone group by default.
Set the share permissions to Full for Everyone, and you should be fine again.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Permission sets are in the security tab, your Share level should allow everyone.  Check to make sure that there is not a user group that the individuals belong to that may have inherant deny access on the share.  This is common from an upgrade.  You could try logging in as the user on a windows 2000 box and test the share.  If it doesn't work then, it is certainly an inheritted permission problem.
Here's some information about the DS client; but since you seem to have read access to the shares, that shouldn't be the issue here, so you don't really need it (shouldn't do harm to install it, either).

Active Directory Client Extensions for Windows 95/98 and Windows NT 4.0

How to enable Windows 98/ME/NT clients to logon to Windows 2003 based Domains

How to install the Active Directory client extension

How Windows 98 Active Directory Client Extension uses Active Directory site information

Oh, and you have a WINS server that your clients are using, don't you?
HOW TO: Install WINS in Windows Server 2003
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.