Permissions problem in Windows NT 4.0 Server

Data analysis
Desktop management applications
Microsoft Access
Microsoft Office
Microsoft Operations Manager
Microsoft Systems Management Server
Microsoft Windows
Patch management
SQL Server
Systems management software
Hi, My file server is WinNT 4.0. In my network I have Windows 98, 2000, Xp as clients. My problem is, I have one folder named 'Project' on my file server. Team Members(TM) have only update access rights, Team leaders(TL) have 'Change' rights. When TM is accessing and updating from Windows 2000 or Xp pc, it is working fine. When the same user is updating from Windows 98 pc it is giving error message 'access denied' and some temp files are creating in the 'Project' folder. How can I solve this problem?? Reddy

Answer Wiki

Thanks. We'll let you know when a new response is added.

You don’t mention if you have a Domain controller or not, but the first thing I’d wonder about is the authentication being used for the Win98 clients. If they are logging in (drive mapping actually) to the file server as work group members, this may be the problem.

Try doing the drive mapping after configuring the Win98 clients to authenticate against a domain controller.

Another possibility is that the file systems permissions are not allowing use of the drive, even though the share-level permissions are.

The information you’ve provided isn’t enough to go on.

Please write back with more details of how the logon, sharing, file permissions, etc. are set up.


Discuss This Question: 7  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Stephen09
    I would also be concerned with the file system format on your computers. Win98 computers only support FAT16 or FAT32 while NT and above also support NTFS (which is the default). I believe that computers formatted with NTFS can see backwards to FAT32 or FAT16, but not the other way around because NTFS has integrated permissions and security. I would also look into sharing the folder, as the sharing protocol may allow the Win98 computer to view the contents of the share.
    15 pointsBadges:
  • Adifferentkindofkris
    I would agree with Stephen, 2000, XP, and Server 2k3 are all based off of WinNT and can use the NTFS file system and are backwards compatable with FAT 32 and FAT 16, however 95, 98 and ME(miserable edition) are DOS based and can not read NTFS, you need should check what the drive is partitioned as, and if it is NTFS you need to have the folder on a drive that is FAT 32 or FAT 16 in order for Win 98 to read it. Lowest common denominator wins when it comes to file structures. An easier solution might just be to upgrade the Win 98 systems to 2000 or XP. Good Luck, - Kris
    0 pointsBadges:
  • Dwiebesick
    Some people are confused regarding NTFS/FAT32 and networking. In a network, the server does not care what file system the client uses and the client does not care what file system the server uses. In networking, it is the protocols that take care of this 'problem' which is not a problem at all. Bob, as usual, is right on target, you need to provided additional information. Also, if your W98 systems are authenticating to a domain controller, I would look to see if the dsclient has been properly installed. This link give more information regarding this: Anyway, W98 computer, when properly configured MOST CERTAINLY can connect and work within NT, Wk2, W2k3 enviroments. NTFS - FAT32 has nothing to do with network connections. Get back to us with more information dmw
    2,235 pointsBadges:
  • 150000
    Hi, We are using BDC as our file server. I am not getting any problem with the authentication, I am logging properly without any errors. After logging from Win98 Pc, When I access the file server, I am able to access the files, though the users have modify rights, they are not able to update. I mapped the drive, still I am facing the same problem. Win98 os is our project requirement. Manjunath
    0 pointsBadges:
  • Dwiebesick
    What settings do you have for the share permissions? Are the users you want to have access to the files listed in the Group or User dialog box? What is different between you and the users regarding permissions/access authority? Windows 98 will use the Share Permissions and not the NTFS security settings. For testing, try making the share permission full control for everyone. Get back with more information. Good luck dmw
    2,235 pointsBadges:
  • Dwiebesick
    Sorry but my last post may be miss understood regarding Windows 98 and accessing NTFS security setting. As written it is not correct. dmw
    2,235 pointsBadges:
  • Petroleumman
    Hello, After reading all the posts to your problem, it sounds to me as you have a permissions conflict somewhere in the mix. Try starting from scratch and remove all permissions. Set your share permissions to allow full control to the domain users or authenticated users group. Next on the folder level (NTFS permissions) assign the TL group the modify permisson which will allow this group to do everything but delete subfolders and files, change permissions or take ownership, then assign the TM group List folder contents, read and write which will allow that group to update. Check the allow inheritence option if you want the permissions to flow down to all child objects i.e. files. Always keep in mind when it comes to Share vs. NTFS permissions, most restrictive wins. This said, keep it simple and use the NTFS permissions to restrict access and not the share. I've had Win95 and 98 machines on an NT network in the past and had no issues with those OS's accessing files on an NTFS share. Unless your leaving some detail out, I'm hard pressed to think a client side file system would have anything to do with your issue. Good luck!
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: