Samba and OS4.1 Udate 6

[gerograph]

@Raziel
Well, I have got a complete SambaInstall here on WinXP/X1000 upd.6 (however, didn't fire AmiUpdate up for while though...). Samba Install was done via Samba4Idiots guide and I did not encounter any problems... up to now. Besides not beeing able to rename files on Amigashares via WinXP. Got the same FritzBox as Raziel plus HD, but I could not manage to connect via SMBFS to my FritzBox, I am using FTPMount for that...

[Raziel]

@Raziel
Well, I have got a complete SambaInstall here on WinXP/X1000 upd.6 (however, didn't fire AmiUpdate up for while though...). Samba Install was done via Samba4Idiots guide and I did not encounter any problems... up to now. Besides not beeing able to rename files on Amigashares via WinXP. Got the same FritzBox as Raziel plus HD, but I could not manage to connect via SMBFS to my FritzBox, I am using FTPMount for that...

I am not on my miggy right now, but you need to be precise in your smbfs line to be able to access the HD.

Could you post your line?

It should look like this in the share part //fritz.nas/name-of-your-hd/name-of-the-subdir-to-be-able-to-access
The Fritz.Box is pretty picky about up/lower case aswell (or was it smbfs)?

[Raziel]

@gerograph

This is my line and it works since a few revisions of the Fritz Firmware now

Code: Select all

run >NIL: smbfs:smbfs WORKGROUP="Workgroup" QUIET DEVICE=SMBFB: VOLUME=Fritz.NAS: SERVICE=//192.168.178.1/Name-of-your-FritzBox/Name-of-your-HD/any-subdir/

WORKGROUP: The name you have chosen in the FB Firmware (needed by smbfs)
DEVICE: Choose whatever you want, this can be accessed later like a device
VOLUME: Kind of the same as before, but the "name" of your device (I never tried if it is possible to add more "partitions" from the same "device")
Name-of-your-FritzBox: Fritz!OS 5.50 lets you name your FritzBox, if you leave it it's normally something like FritzBox-7390
Name-of-your-HD: In the USB sub menu of your FritzBox your attached HD has been named by your FritzBox, something like, Storage-150GB-01, the -01 part is the one that was added by the FritzBox, you need the exact name given to be able to access it

The "any-subdir" part is optional

[Christopher Follett]

Something very interesting, since discovering those mysterious files.
I no longer have access to my nas via putty. Inputting correct details gives me "Permission Denied".
Everything else is working as it should, the password file it cant access is the same used by samba, which works fine with same passwords.

Have I been hacked? I keep ssh turned off when Im not using it, so I find it hard to believe I have been hacked.
Just seems strange that since those files appeared I have lost the ability to login using my admin accounts. I can login via root though (which I have never ever used before until this problem).

[Spectre660]

I have those two files on a Windows XP shared partition with Samba.
I may have also used this partition from the Windows side with Amikit .

[Christopher Follett]

I have those two files on a Windows XP shared partition with Samba.
I may have also used this partition from the Windows side with Amikit .

Be nice to know the origin of these files, is it samba creating them?
Cause all this server wierdness started with those files.

[abalaban]

@Christopher

May I know your NAS's brand and model?

I have been searching for a while where on earth those files were coming from but never thought about SMBFS until now. I always blamed (without any evidence) the NAS firmware, more specifically the DLNA server software installed on it (which is an old version of TwonkyMedia).
This old version of the DLNA server may, some time, spend to much time reindexing the files to share, thus the next indexing iteration would start before the previous ended, this automatically slows both the new iteration and the old one. In the end indexing iteration would stack eating up almost all the PID numbers, at this step you have frozen any Linux system (i.e. no ID left to launch a new process thus you can't FTP, telnet, SSH etc, unless you were already connected.
For me, the only solution is to reboot the NAS and reconfigure the sharing options (i.e. only scan the directories where I put my media files to share, no the entire system, increase the delay between two indexing iteration and most importantly do not rely on the "automatic detection" old Linux kernel didn't have proper file/drawer notification system hence the "automatic detection" is always some sort of a hack...

[Christopher Follett]

Western Digital 1TB WhiteLight v2.

Funny you should mention Twonky as I disabled it about 6 months ago. So thats not even active.