-
Turn off Norton on all three, reboot all three, and try again.
-
An excerpt from that Microsoft article I posted earlier is below.
With file sharing in Windows XP, you can configure five levels of permissions. Level 1 is the most private and secure setting, and Level 5 is the most public and changeable (non-secure) setting. You can configure Levels 1, 2, 4, and 5 by using the Simple File Sharing UI. To do this, right-click the folder, and then click Sharing and Security to open the Simple File Sharing UI. To configure Level 3, copy a file or folder into the Shared Documents folder under My Computer. This configuration does not change when you turn on or turn off Simple File Sharing.
What is in the Shared Documents folder when you have this problem?
-
Robert, I've pretty much given up on this issue but I thank you nonetheless.
I have tried both w/ NAV on & off but it makes no difference.
As far as permission is concern ... I've looked into that many times and have not seen anything that is suspecious.
The problem only occurs when the root directory is populated to a certain degree ... I've not spent the time to really make detail observations but it seems that when about 40% (or even as low as 30%) of the drive capacity is reached then I can't write to that root directory from a network computer any more ... only to its sub-directory is possible.
-
Are disk quotas set up on the Windows XP computer?
If they are, you may not neccessarily receive a warning when your quotas were reached depending on how that warning option was set.
-
-
-
None of them seems to apply to my situation.
-
Did you try the strategy from one of the Microsoft links which suggests the following to see the information about NetBIOS?
To determine whether NBT is enabled on a Windows-based computer, run a net config redirector or net config server command at a command prompt. The output shows bindings for the NetbiosSmb device (which is the "NetBIOS-less" transport) and for the NetBT_Tcpip device (which is the NBT transport). For example, the following sample output shows both the direct-hosted and the NBT transport bound to the adapter: Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{610E2A3A-16C7-4E66-A11D-A483A5468C10} (02004C4F4F50)
NetBT_Tcpip_{CAF8956D-99FB-46E3-B04B-D4BB1AE93982} (009027CED4C2)
NetBT_Tcpip is bound to each adapter individually; an instance of NetBT_Tcpip is shown for each network adapter that it is bound to. NetbiosSmb is a global device and is not bound on a per-adapter basis. This means that direct-hosted SMBs cannot be disabled in Windows without completely disabling File and Printer Sharing for Microsoft Networks.
Are you familiar with Browse Master settings?
Also, do you have at least one of the computers configured to assume a MASTER BROWSER role? See the following link.
http://support.microsoft.com/default...b;en-us;188001
--------------------------------------------------------------------------------
-
You may be able to use the tip in the following link to locate the name of the file responsible for generating that message.
http://discussions.virtualdr.com/sho...d.php?t=198604
-
Dude, this thread is a year old!
-
-
Haven't got the time to try that yet, Robert, being the holidays and all. Will do later and let you know.
-
Are you logging onto the client computers when you start them up?
What user name are you using? Do you have user profiles in use on the clients? Same user name being used as when writing to the root worked before?
