does xp need to write to shared drives?

[dave]

Our server is linux, and I recently changed permissions on all root
folders for a shared networked drive from 0771 (read/write/list for
everyone) to 0555 (read/list for everyone), this was to prevent users
creating new files/subfolders within these folders. However now, when
they access this drive from WinXP, it takes forever to list the
contents (the torch icon is swaying around for nearly a minute). Trying
it from Win98 or linux, its fine.

Does anyone know why this should slow down XP from viewing the
contents?


Thanks in advance
Dave.

 

[Malke]

Our server is linux, and I recently changed permissions on all root
folders for a shared networked drive from 0771 (read/write/list for
everyone) to 0555 (read/list for everyone), this was to prevent users
creating new files/subfolders within these folders. However now, when
they access this drive from WinXP, it takes forever to list the
contents (the torch icon is swaying around for nearly a minute). Trying
it from Win98 or linux, its fine.

Does anyone know why this should slow down XP from viewing the
contents?

Did you map the drive in Windows? Create a shortcut to it? In either case,
delete it and then reboot. Then create it again and see if that helps.

Malke

 

[dave]

Did you map the drive in Windows? Create a shortcut to it? In either case,
delete it and then reboot. Then create it again and see if that helps.

Malke
--
MS-MVP Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

Hi Malke,

The drive gets deleted and mapped again when they logon to the domain
in a logon script. At the same time there are 2 other drives that get
mapped too, but these ones are fine.

 

[Malke]

The drive gets deleted and mapped again when they logon to the domain
in a logon script. At the same time there are 2 other drives that get
mapped too, but these ones are fine.

There must be a problem with the permissions then, because that's the only
thing you changed. I allow read/write to my Windows boxen here so I can't
check the permissions for you. Are the folders sub-directories? Perhaps the
parent directory's permissions aren't quite right.

I understand what you want to do and it is completely possible - that's the
way I set up some of the directories on the SUSE server at my kid's school.
I've got folders where the kids can only read/copy for homework handouts.
But I don't use a script or map drives because it causes a problem when the
network resource isn't available. I just make a shortcut to the Samba
server on their desktops. How many computers are we talking about here? Is
there a reason to script/map the drive?

Other than those thoughts, I'm afraid I don't have any definitive answers
for you.

Malke

 

[dave]

There must be a problem with the permissions then, because that's the only
thing you changed. I allow read/write to my Windows boxen here so I can't
check the permissions for you. Are the folders sub-directories? Perhaps the
parent directory's permissions aren't quite right.

I understand what you want to do and it is completely possible - that's the
way I set up some of the directories on the SUSE server at my kid's school.
I've got folders where the kids can only read/copy for homework handouts.
But I don't use a script or map drives because it causes a problem when the
network resource isn't available. I just make a shortcut to the Samba
server on their desktops. How many computers are we talking about here? Is
there a reason to script/map the drive?

Other than those thoughts, I'm afraid I don't have any definitive answers
for you.

Malke
--
MS-MVP Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"

Hi Malke, I have disconnected the drive, and tried setting up a
shortcut, but its still the same.
The reason i have a logon script is because some users require
different shares, and sometimes use different workstations. Below is
the layout of the drive in question before and after with relevant
permissions showing:

Before:
---NetworkDrive <--- 2771 # all known users read/write/execute
|--folder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute

After:
---NetworkDrive <--- 2771 # all known users read/write/execute
|--folder1 <--- 2551 # all known users read/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2551 # all known users read/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2551 # all known users read/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute

Thanks
Dave.

 

[Malke]

Hi Malke, I have disconnected the drive, and tried setting up a
shortcut, but its still the same.
The reason i have a logon script is because some users require
different shares, and sometimes use different workstations. Below is
the layout of the drive in question before and after with relevant
permissions showing:

Before:
---NetworkDrive <--- 2771 # all known users read/write/execute
|--folder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute

After:
---NetworkDrive <--- 2771 # all known users read/write/execute
|--folder1 <--- 2551 # all known users read/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2551 # all known users read/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|--folder1 <--- 2551 # all known users read/execute
|-subfolder1 <--- 2771 # all known users read/write/execute
|-subfolder1 <--- 2771 # all known users read/write/execute

Dave, I'm a little confused by this. Normally you don't assign permissions
to a drive - you assign permissions to partitions and/or directories.
Obviously I can't run over to school and give you my Samba permissions, but
I think I'd try moving the folders where you want only read/execute out
from the parent folders. I'm not an expert with permissions, but the way I
do it on the school server is something like this (and please understand
I'm doing this from an imperfect memory):

/mnt/windows
/mnt/windows/teachers [directory where only teachers and root can
read/write/execute]

/mnt/windows/students [directory where everyone can read/write/execute]

/mnt/windows/handouts [directory where teachers and root can
read/write/execute but students can only read (and maybe execute; I don't
remember - it's for them to get their homework assignments and handouts so
they can copy the files to their laptops)]

So this way there is only one icon on the kids' desktops to the Samba
server. They click on it and can see the various folders but can only go
into the ones where we've allowed it. For us, it doesn't matter that they
can see the 5 or 6 shared directories because they can only get into the
ones we allow.

I'm really sorry that I can't just look at your permissions and say "oh,
that's it". Maybe you should try posting in a newsgroup for your distro and
one of the experts there will get it immediately.

Malke