Why is R/O property set on Network Shared Folders of XP clients and not w2k Clients ?

  • Thread starter Thread starter Al Dykes
  • Start date Start date
A

Al Dykes

I have seen ths a couple of times. XP machines show that folders are read only
and that it can't be changed. This hasn't caused me a problem on XP machines
until now.

I support a site that has an AD domain based on w2k server. It exists
to run a turnkey business aplication. (imho the company that wrote
this package knows the industry really well but is not real sharp in
the programming department.) In addition to an SQL server it publishes
a share that contains the application code. and some working temp
files. The file server is NTFS, of course.

The user has lots of w2k clients which work fine, but they've just
purchased a couple of XP machines and the application fails on these.
The app can't write correctly to the temp files on the server and the
vendor's tech support people admit to have seen this at another site.

On an XP client browsing to the network share permissions the RO check
is ON. Going to a w2k client the RO is OFF. From the server console
everyone had read-write, and now, full control.

Does this make sense to anyone ?

The application is written in foxpro (!) and I'm afraid the programers
can't do work-arounds very easily. I'd love to see a KB article that
I could show to my client and forward to these people.

Thanks
 
Hello,

XP and Windows 2003 default behavior for share permissions is different
than Windows 2000 and NT 4.0. The default share permissions are no longer
Everyone Full Control. I think this may be what you are seeing.

Dale Weiss MCSA MCSE CISSP
PSS Security

This posting is provided "AS IS" with no warranties, and confers no rights.
Any opinions or policies stated within are my own and do not necessarily
constitute those of my employer. Use of included script samples are subject
to the terms
specified at http://www.microsoft.com/info/cpyright.htm
 
Back
Top