 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Permissions problem in Windows NT 4.0 Server</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 13:28:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: petroleumman</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/#comment-36656</link>
		<dc:creator>petroleumman</dc:creator>
		<pubDate>Mon, 30 Jan 2006 09:19:24 +0000</pubDate>
		<guid isPermaLink="false">#comment-36656</guid>
		<description><![CDATA[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&#039;ve had Win95 and 98 machines on an NT network in the past and had no issues with those OS&#039;s accessing files on an NTFS share. Unless your leaving some detail out, I&#039;m hard pressed to think a client side file system would have anything to do with your issue.

Good luck!]]></description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>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. </p>
<p>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. </p>
<p>I&#8217;ve had Win95 and 98 machines on an NT network in the past and had no issues with those OS&#8217;s accessing files on an NTFS share. Unless your leaving some detail out, I&#8217;m hard pressed to think a client side file system would have anything to do with your issue.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dwiebesick</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/#comment-36657</link>
		<dc:creator>dwiebesick</dc:creator>
		<pubDate>Fri, 27 Jan 2006 14:09:40 +0000</pubDate>
		<guid isPermaLink="false">#comment-36657</guid>
		<description><![CDATA[Sorry but my last post may be miss understood regarding Windows 98 and accessing NTFS security setting.

As written it is not correct.

dmw]]></description>
		<content:encoded><![CDATA[<p>Sorry but my last post may be miss understood regarding Windows 98 and accessing NTFS security setting.</p>
<p>As written it is not correct.</p>
<p>dmw</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dwiebesick</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/#comment-36658</link>
		<dc:creator>dwiebesick</dc:creator>
		<pubDate>Fri, 27 Jan 2006 14:01:15 +0000</pubDate>
		<guid isPermaLink="false">#comment-36658</guid>
		<description><![CDATA[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]]></description>
		<content:encoded><![CDATA[<p>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?</p>
<p>Windows 98 will use the Share Permissions and not the NTFS security settings.  For testing, try making the share permission full control for everyone.</p>
<p>Get back with more information.</p>
<p>Good luck<br />
dmw</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 150000</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/#comment-36659</link>
		<dc:creator>150000</dc:creator>
		<pubDate>Fri, 27 Jan 2006 11:55:45 +0000</pubDate>
		<guid isPermaLink="false">#comment-36659</guid>
		<description><![CDATA[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]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>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.</p>
<p>I mapped the drive, still I am facing the same problem.<br />
Win98 os is our project requirement.</p>
<p>Manjunath</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dwiebesick</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/#comment-36660</link>
		<dc:creator>dwiebesick</dc:creator>
		<pubDate>Thu, 26 Jan 2006 18:21:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-36660</guid>
		<description><![CDATA[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 &#039;problem&#039; 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:
http://support.microsoft.com/kb/555038/en-us

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]]></description>
		<content:encoded><![CDATA[<p>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 &#8216;problem&#8217; which is not a problem at all.</p>
<p>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.<br />
This link give more information regarding this:<br />
<a href="http://support.microsoft.com/kb/555038/en-us" rel="nofollow">http://support.microsoft.com/kb/555038/en-us</a></p>
<p>Anyway, W98 computer, when properly configured MOST CERTAINLY can connect and work within NT, Wk2, W2k3 enviroments. NTFS &#8211; FAT32 has nothing to do with network connections.</p>
<p>Get back to us with more information</p>
<p>dmw</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adifferentkindofkris</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/#comment-36661</link>
		<dc:creator>adifferentkindofkris</dc:creator>
		<pubDate>Thu, 26 Jan 2006 15:01:19 +0000</pubDate>
		<guid isPermaLink="false">#comment-36661</guid>
		<description><![CDATA[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]]></description>
		<content:encoded><![CDATA[<p>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.</p>
<p>An easier solution might just be to upgrade the Win 98 systems to 2000 or XP.</p>
<p>Good Luck,<br />
 &#8211; Kris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stephen09</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/permissions-problem-in-windows-nt-40-server/#comment-36662</link>
		<dc:creator>stephen09</dc:creator>
		<pubDate>Thu, 26 Jan 2006 11:53:03 +0000</pubDate>
		<guid isPermaLink="false">#comment-36662</guid>
		<description><![CDATA[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.]]></description>
		<content:encoded><![CDATA[<p>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.</p>
<p>I would also look into sharing the folder, as the sharing protocol may allow the Win98 computer to view the contents of the share.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.047 seconds using memcached
Object Caching 351/357 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 14:46:32 -->