I got 3 users using win95 in the same workgroup. The problem here is only one of them cannot access files from server but still can login into it. I already put their name and set the access right in the User Manager for Domain. Those 3 users are using win95 but the data will be stored in NT server 4.0. Surprisingly from WinNT server i can access to this 3 pcs. Can u guys teach me on how to resolve it.

Have you setup the network properties in the 3 Win95 clients- as far as correct IP's,subnet masks and default gateways? Can you ping each of these machines IP's from each machine?

MAKE SURE THREE WIN95 AND NT4.0 IS UNDER THE SAME DOMAIN NAME. SETUP TCP/IP 100.100.100 1TO 3 ADDRESS in win95. NT SERVER 100.100.100. 4 AND SUBNET MASK. 255.255.255.0 IN NT and win95. SET UP USER ACCOUNT and PASSWORD in NT server....

Thanks to both of you. I've did all that process and steps but it's still doesn't work. Me and my techn plan to take out the network card and maybe gonna change to diff slot and resetup again. Hope it works

Actually its a permissions problem. NTFS cannot access a FAT/FAT32 drive over a network and vice versa. The way to do that is to give access to "Everyone". That is a quick way to bypass proper security permissions. NTFS can view NTFS etc. It is not a hardware problem so your NIC cards are fine. If you want the 95 machine to view the NT machine then create a FAT partition on the NT machine, unless you have admin priveleges and can change the permissions.

If you are getting the "ACCESS DENIED" MESSAGE when accessing windows 95 shares from NT 4.0 Microsoft has identified a problem you may experience when you attempt to connect to a share on a Windows 95-based computer from a Windows NT 4.0 workstation or server. The connection attempt may fail, giving you an "Access denied" error message. Microsoft says the problem is the result of an interoperability problem between Windows NT 4.0 with Service Pack 2 or Service Pack 3 installed and Windows 95. Windows NT 4.0 with Service Pack 2 or Service Pack 3 makes a connection using a null user name, which Windows 95 does not handle correctly. To fix the problem, download the updated file for Windows 95 and OSR1, and later versions of this file: VSERVER.VXD version 4.00.954 For Windows 95 OSR2 and OSR 2.x, and later versions of this file, you need the following updated file: VSERVER.VXD version 4.00.1112 dated 7/24/97 112,904 bytes These files are available in the support area of the Microsoft Web site.

It's permissions alright. I'd go with the ping thing - ping the server form each workstation to test the connection. You may also have the number of users under permissions and shares set to one. If you don't care about security, give everyone Administrator permission and see if they can connect. You can see files over a network from FAT32 to NTFS - otherwise I wouldn't be able to see my personal docs on my server.