LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   General (https://www.linuxquestions.org/questions/general-10/)
-   -   FreeDOS + MS Client (SMB/CIFS) read only access (https://www.linuxquestions.org/questions/general-10/freedos-ms-client-smb-cifs-read-only-access-948969/)

czezz 06-07-2012 02:25 AM

FreeDOS + MS Client (SMB/CIFS) read only access
 
I have installed FreeDOS 1.1 and MS Client 3.0.
Now I can easily access shared folder on my Windows XP (folder is set up with full access to everyone and to specific user).

However, if I connect from my DOS machine I have READ-ONLY access :(
But I have full RW access if I connect to this share form another Windows machine or Linux box.
What did I forget to set up on Dos machine ? There must be something wrong with it.

http://imageshack.us/photo/my-images...apturegce.png/

wpeckham 06-07-2012 11:37 AM

Danger!!
 
Given the restriction on FreeDOS (or any DOS without NTFS or 32-bit FS support) would you really want it able to write to a XP shared filesystem? Have you tried to share a FAT16 partition to see if that behaves the same?

HAve you posted the question on the FreeDOS forums? (I would think it more appropriate there.)

czezz 06-07-2012 11:58 AM

Hello and thanks for reply.
I have just did a quick test with FAT16 partition and it failed this same :(.

However, I have found this: http://www.veder.com/nwdsk/
This creates bootable FreeDOS img/floppy with MS Client. When I run this it just works. I have full access to shared folder on WinXP.
With my installation of DOS still not :(

Any clue what is wrong ???
ps. I have alrdy posted on FreeDOS mailing list.

Doc CPU 06-07-2012 03:21 PM

Hi there,

Quote:

Originally Posted by wpeckham (Post 4697989)
Given the restriction on FreeDOS (or any DOS without NTFS or 32-bit FS support) would you really want it able to write to a XP shared filesystem? Have you tried to share a FAT16 partition to see if that behaves the same?

your concern is meaningless, as Windows Shares (like Samba shares) do not expose the actual file system. Thus it doesn't matter if the client connecting to that share is another Windows PC, a Samba client on a Linux PC, a DOS client or an Android phone with a suitable app. They just "see" a network share, but nothing specific.
So there's no point in wanting to deny write access to a "primitive" client.

This is totally different with USB mass storage devices: They're mounted as low-level file systems, and the host system has to support that file system all on its own.

[X] Doc CPU

czezz 06-07-2012 06:18 PM

I have simply reinstalled MS Client and it works. No idea what was wrong.


All times are GMT -5. The time now is 12:20 AM.