03/15/2010 (6:38 am)
Filed under: nappedeptrole.com edit
I am experiencing a unique problem and I want to make sure Outpost Pro v2.1 doesn't or couldn't have anything to do with it as it is driving me nuts. I have a small network and have Outpost Pro v2.1 on all the 5 pc's. Everything used to work fine but that means nothing as I usually download and update a hundred things a week so who knows what caused this behaviour... The problem is copying files through the network from an XP Pro box to a Win98SE box is having some issues with "Access Denied" or "Unable to read file" type errors. It seems that I can "push" the file from XP to Win98 but trying to "pull" the file from XP to WWin98 I get the errors. This happen with a backup utility and also through Network Neighborhood. The funny and confusing thing is after days of pulling my hair out, it seems that files downloaded from the internet using Firefox RC 1.0 give me the errors while the same file downloaded with Internet Explorer do not although both file are installable and seem identical. Very weird...
Anyone? Thanks in advance,
MoeDid you start with the basics?
1) Check which user has read permission to the shared folder AND the file (Check BOTH at the share level and the NTFS level - Security TAB)
2) Make sure the share name isn't longer than 12 chars (Win9x doesn't like that)
3) Note that the "Shared Documents" folder created by default by WinXP is for local users, not LAN users. Default permissions might not be suitable.
4) Unless you are allowing Guest users to log in (bad idea), make sure that the user that's logged on the Win98 box exists on the XP box, with the same password.
5) Did you try with all firewalls disabled (especially the WinXP SP2 one)?
Yes, I started with the basics and the problem wasn't there a few weeks ago and the only thing I changed was I did some Windows updates and then finally installed SP2. I used to use the shared folder from XP to hold downloaded files and then they could be accessed on my local network and this was done with a file sync and backup program. Depending on when I did it it may have copied just a few files, or hundreds, but it always copied them all. Then the last time I used it it had file access errors on 468 files so I knew something was up. I must admit we had a hurricane and I have been sidetracked with a roofing job so maybe I started doing something different than I was before and created my own monster, but the ONLY thing I could have done different (now that I think of it) is try to make it 1 step easier by downloading directly into the shared folder. I used to download files into a folder called TransfersNovember and then copy them to the shared folder for access to the rest of the local network. Then I thought it would be easier to just put the create the folder November in the shared folder to save a step. Maybe thats what started this....I will do some backwards testing and see if thats it. Otherwise I checked all the other steps you mentioned....
Thanks,
MoeManny, Well a couple of days seems to have gone by and the best I can figure is that XP Pro with SP2 kindly quarintines the files in the folder they are first put into. The reason I say that is even in a newly created shared folder, the files downloaded into it cannot be pulled into a Win98SE box as they get "access denied" errors, BUT if I copy them from the folder into yet another shared folder, the same files can and do get pulled into the Win98SE box just fine. I guess its a security thing....I can deal with it as long as I can replicate and somewhat understand why :)
MoeWell, I guess it was a combination of too much going on around here and too many updates :D I tried the ADS idea but it didn't help. I ended up moving the files from the "Shared Documents" folder which I believe is Simple File Sharing to a separate shared folder (although it seems I tried that a few days ago with no luck) and a quick test shows it works again. I may have created my own problem when I decided to use just the Shared Documents folder for all my file sharing, then started having problems, then installed SP2, then realized my backup program choking. And right before that I upgraded my AV software which had some memory leak issues so I reinstalled the old versions on all 5 pc's :eek: I can remember when I used to get work done with my computer and now I am always working on it :rolleyes:
Thanks for the idea though,
Moe
added: After more testing I have come to the conclusion its SP2 trying to protect me from myself as the behaviour is erratic and while sometimes it works, other times it does not. If I move the file that does not transfer through the net to yet another shared folder it works...Weird! Thanks MS :rolleyes:Your right, too much going on. Well, you know what they say happens. Give it a couple of days and maybe I'll come up with another crazy idea. Good luck with it!Just thinking out loud here. I wonder if this is due to Alternate Data Streams(ADS) added by some app in XP, which I gather may be Firefox. Ad-Aware checks and is capable of removing ADS from files. Easy to do -choose the location and use the scan for ADS option. Like I said, just thinking out loud - no guarantees.Manny, Well a couple of days seems to have gone by and the best I can figure is that XP Pro with SP2 kindly quarintines the files in the folder they are first put into. The reason I say that is even in a newly created shared folder, the files downloaded into it cannot be pulled into a Win98SE box as they get "access denied" errors, BUT if I copy them from the folder into yet another shared folder, the same files can and do get pulled into the Win98SE box just fine. I guess its a security thing....I can deal with it as long as I can replicate and somewhat understand why :)
Moe
Did you start with the basics?
1) Check which user has read permission to the shared folder AND the file (Check BOTH at the share level and the NTFS level - Security TAB)
2) Make sure the share name isn't longer than 12 chars (Win9x doesn't like that)
3) Note that the "Shared Documents" folder created by default by WinXP is for local users, not LAN users. Default permissions might not be suitable.
4) Unless you are allowing Guest users to log in (bad idea), make sure that the user that's logged on the Win98 box exists on the XP box, with the same password.
5) Did you try with all firewalls disabled (especially the WinXP SP2 one)?#If you have any other info about this subject , Please add it free.# |
|