West Wood MAX retreiver

[dgurzynski]

I'm wondering if there are any engineers out there who have been able to make the WW1 Max retriever software work properly in a shared network environment? I've been working with them about it and I'm hoping for some networking guru's out there that could give me a hand. Thanks.

[countrykev]

The WW1 Retriever brings all the downloaded spots to one folder, wherever you specify. Just setup a Windows share for that folder. Then map the computers that need to see it to that share either via a shortcut on the desktop, mapped drive, etc...

[dgurzynski]

So one might think. That is how I have it set up and what happens is the next time a feed comes down users don't have rights to the new file(s). They can't copy, open , or do anything with files that come in after I set rights/permissions. It did that when I tried using both simple file sharing and standard sharing. If I re-apply rights then it clears up until the next download.

The WW1 Retriever brings all the downloaded spots to one folder, wherever you specify. Just setup a Windows share for that folder. Then map the computers that need to see it to that share either via a shortcut on the desktop, mapped drive, etc...

[radiowave911]

What operating system? What are the permissions on the share? It sounds like the share is not allowing everyone read access.

[dgurzynski]

radiowave911

Thanks for the reply. The workstation is running windows XP Pro. It appears that I have proper rights on the share. When I created the share the users could get at everything. When the next download came, they couldn't get the new download so it looks like some odd inheritance problem. Since the WW software runs as a service my next step is to see what rights it's running under and try to match to the users. My ABC X-couriers has no such trouble at all but so far WW has tried but hasn't been able to figure this out. Any hints would be appreciated.

[BroadcastDoc]

I think you may be on to something. It's quite possible that the downloaded file is not inheriting the rights from the parent. I don't remember with XP whether you have granular control of the rights, but in server 2K3 you can go into advanced permissions and force inheritable permissions from the parent object. Make sure to do that on the container one level up from where the files are living.

[eadler]

Also note to make sure that your user accounts have passwords set. Windows does some odd things, especially with regards to sharing, when accounts have blank passwords.

[dgurzynski]

You know, that may be it. I really didn't want to give the user account a password considering 2 to 3 people will need it and I was trying to give them one less thing to remember. Although I have a share for ABC's download software and have no such problem with it at all. I'll give it a try.

Also note to make sure that your user accounts have passwords set. Windows does some odd things, especially with regards to sharing, when accounts have blank passwords.

[eadler]

"administrator:administrator" or "user:user" shouldn't be too hard of a credential to remember. It doesn't need to be a secure password, it just needs to be one. Heck, engrave it into the bezel of the monitor if you need to (or use a sticky note )

[dgurzynski]

Actually WW has a very good document on their website about 'Moving Folders'. This had all the info on creating the share, setting rights and most important, setting rights to the service. It seems good for now. Thanks everyone.