Windows 95 cannot open files on Windows 2008 file share

[hankhill]

Hello,

We have several Windows 95 computers that connect to a Windows 2003 DC. We have just implemented a Windows 2008 server (not a DC) as a file share server.

The Windows 95 clients can see the files in fileshare (They have Modify access), but can only open TXT files. All other files, Excel, Word, JPG, etc, cannot be opened. It gives an error that the file cannot be found or is read only when we attempt to open them. We are unable to copy these file types as well with the same error of "cannot find file".

The Windows 95 client can access another file share server (Windows 2003) and open all file types without a problem.

So I suspect there is some incompatibility or setting either on the client or the server that needs to be tweaked.

Thank you

 

[ICTCity]

Hi,

I'm quite sure there's a policy where you can allow "anonymous" autentication but this is only needed when you can't connect to windows server 2008. IN your case I think the problem is a compatibility, unlucky this OS (win 95) is no longer supported by microsoft so I can't even open a ticket. I just think there's not a solution because this is not a "policy" setting, but it looks like your client doesn't know how to handle the way windows server 2k8 gives shares to you.

 

[hankhill]

Hi ICTCity,

Thanks for the response, it is actually Windows 98 not 95, I made a typo. But, I imagine it falls under the same issue of an imcompatibility of passing credentials.

Regards

 

[ICTCity]

yes. But I don't think this is a credentials problem.

Try (just a test) to share a folder with FULL CONTROL in both, ntfs and share permissions. Try if changes something.

 

[hankhill]

I did a test and installed an eval copy of Win2k8 R2 64-bit on a Virtual Box and set up a test share folder with the same permissions as the problem 2008 server and the Windows 98 box was able to copy and open files without issue.

 

[ICTCity]

OK, it's the same scenario? Domain users? The file server is also the DC? Or you use the "old" DC?

Try to enable the security and folder auditing to determine why your user cannot access that folder. Other that, run a EFFECTIVE PERMISSIONS on that folder for that user. Maybe we can understand something more.