Re: Network Question on Shares

Paul Ratcliffe wrote:
On Fri, 22 Feb 2008 03:17:18 GMT, PaulRS <prschmi@xxxxxxxxxxxx> wrote:

I am trying to share between OS/2 Box and a OpenSuSE 10.3 box

If I set up the share by the GUI (click on "connections" - "Drive d" -
start sharing) and go through the menus everything works fine and SUSE
sees the share.

If I use the command line (net share drive-d=d:\) OS/2 says that the drive-d was shared successfully. However, the folder will show up in SUSE, but when you click on it you get "Folder is non-existant"

Can anyone explain this???
ACLs probably.
Please explain ACLs??? Too cryptic for my level of understanding

Access Control Lists. Check using "net access" from the command line.
Also, sharing a root directory (C:\) is not the same as sharing a drive (C:)
using the GUI. Sharing the directory only allows access to that directory and
not any sub-directories.

If you share a directory that has subdirectories, the GUI gives a message, "This directory has subdirectories, do you wish to share them?" or something to that effect. If you answer yes, it creates an access control list giving access to all currently existing subdirectories and files. The problem with this is that any subsequently created subdirectories and any files in them files will not be added to the access control list and will be accessible only to users with administrative access. I am not certain about files added to existing directories. Also big drives with lots of directories and files overflow the capabilities of the access control database and cause all hell to break loose. Unless you really need to limit access only to certain subdirectories, sharing the drive is the way to go.

I forget any more of the detail now...

Connection information is stored in b:\ibmlan\lsuse.ini, sharing information is stored in b:\ibmlan\lsshare.ini, userid and access information is stored in b:\ibmlan\accounts\net.acc, where b is the boot drive. The connection and sharing information are in os2 ini files. When you make changes, any dead information is removed immediately, the files are never larger that they have to be. The user and access database is in a proprietary Microsoft lanman format which does not seem to be documented anywhere. Dead information stays around forever as in most Microsoft stuff and the files just keep getting bigger and bigger as you make changes. There is supposedly a net.acc compacting utility out there but it only runs on windows. Also on a booted system the net.acc file is locked so that you can only operate on it using the supplied commands which don't work right when the number of subdirectories and files gets too large.

There is a bug in the database manager that prevents deletion of the access information for a directory that has too many subdirectories and files and makes some directories and files unaccessible even though they are in the database. I don't know how many too many is but you can find out if you have the problem by going to the permissions tab of sharing and connecting and going through your shared drives one by one. (Note: it lists all the drives, not just the shared ones.) A drive that has never been shared will just display a blank panel. If the drive has been shared, it displays the word drive on parentheses. If a directory and its subdirectories has been shared it displays a long list of directory and file names; if it then says "More data Available," you will find that you no longer can change the access information. The only solution to this that I have found is to start over from scratch by doing the following:

Boot from a maintenance partition or the install disks.

Get rid of your shares: Delete or rename b:\ibmlan\lsshare.ini. It will be automatically recreated and you will be able to redefine your shares with no problem when you reboot.

Go back to square one on users and access permissions: Delete or rename b:\ibmlan\accounts\net.acc. Copy b:\ibmlan\install\net.acc to b:\ibmlan\accounts.

Reboot. Any automatic logon you have set up will not work because your userid and password are no longer valid. When the logon fails enter USERID and PASSWORD on the retry and you will be logged on as default administrator. Your connections should still exist. You will have only USERID and PASSWORD as administrator and GUEST with no password as your users. Recreate your usual userid and password as administrator. Shut down and reboot and test this to make sure that it works. Once you are sure your normal administrator id is working again, change userid to an ordinary user. Now recreate your shares making sure to share the drive(s) and not the root directory. It you check the permissions tab, the shared drives should now all be listed as drives.
.

Relevant Pages

  • Re: Results of my straw poll.
    ... Who says you need 7 CD drives for the VMS docs? ... Have you had good luck with CD sharing? ... drives on a PC to provide documents that students would access (in HTML ...
    (comp.os.vms)
  • Re: File and Printer Sharing - Missing Share
    ... ignorance of sharing drives vs sharing folders. ... had not turned off File and Printer Sharing, and assumed it was the D: ... there was a shared folder in each D: ...
    (microsoft.public.windowsxp.network_web)
  • Re: Peer to Peer sharing
    ... Windows XP by default created administrative shares for the root folders of the fixed drives of the computer. ... You can create your own shares to share your drives from the root of the drive, but Microsoft highly recommends that you share only the folders that you need to, rather than the entire drive. ... Windows Vista displays the properties for the drive with the Sharing tab selected. ...
    (microsoft.public.windows.vista.networking_sharing)
  • Re: Cant set permissions on drive
    ... Sharing and Security tabs are available on folders however. ... I have Simple File Sharing turned off on the XP boxes and I'm logged ... I have the Sharing/Security tabs avilable for the drives yet can't say ... How to set, view, change, or remove file and folder permissions in Windows XP ...
    (microsoft.public.windowsxp.general)
  • treeview node.ToString problem
    ... I've populated the treeview with the available drives and the first ... Then I'm using this code to get the selected node when the user ... Dim subDirectories() As String ...
    (microsoft.public.dotnet.general)