Discussion Locked

This issue has me stumped!!

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok.. I will try to explain this. A user received a new Win98 laptop, which logs on to a W2K Domain using Client for Microsoft software. When he logs in he can see the network and see all the files in the folders but when he tries to save anything to network it says that the folder is marked as read-only, this happens to if he tries to rename through explorer. Everyone has Full Control to the share in which he is saving too. But the thing that is really confusing to me is that when the User logs into his old laptop he can save files fine. So my guess is that it is something to do with the laptop configuration on the new laptop.
The hardware is different configurations to the same model of laptop. And the software difference is the new laptop has Office 2000 and the old laptop had Office 97.
Does anyone have any ideas??? Anything will help and be appreciated. Thanks in advance.

9 replies

by mphoffar

Sounds like there's something there tht isn't recognizing him as part of the domain users group. Basically, not getting the security tokens when logging onto the domain.

You didn't mention this, but I would check log onto windows NT domain in Client for MS networks (if you alrady haven't done so) and then make sure you have user level access control set (as opposed to share level)

Good luck to you

Mark

by michelle_lovejoy

I had the user change the Access Control to User Level and the issues still occured. I agree that for some reason it is not getting the right security authenaction.

Also, do you add Win98 clients to Server Manager in W2K? I know in WNT 4.0 you only add NT Workstations or Servers.

by d_lairson

Have you enabled user profiles on the laptop? I had a somewhat similar problem the security token from Win98 was not being recognized correctly by the server because the Win98 machine was set up for no profiles. Enable Profiles, logoff the laptop, log on, and then try...
Hope this helps,
David

by michelle_lovejoy

This answer got me thinking. Somehow the Win98 clients on the old was holding the old security in. What happened was that there was an additonal share set up on the Server since the permission was 'Most Restrictive' Read-only was the default. The old laptop didn;t have any problems because it was holding the old info from the .pwl file in Windows. So if anyone ever experciences this strange similar problems try to delete the .pwl first.

(I was finally about to touch the Server to see that the share was set up wrong. Before I had some relay me the problem from a remote site).

Thanks for all your help.

This discussion is closed to new replies.