Samba/smb.conf + Windows 10 ??

Hello everybody,

I am trying to connect to Samba Amiga Shares from my Win 10 pro machine. The whole thing is setup on the Amiga OS4 side, and already working with WinXP (via VMWare Player and on my other machine).

However Win 10 keeps telling me, when I connect a share, that I donnot have proper authentification. This is my smb.conf:


Any Idea? Thanx

@gerograph

This has been "updated" to not work with our outdated samba package since Win7.

Something to do with security/authentification, like you said.

Nothing that can be done about it, unless someone updates SAMBA

Perhaps this will help? http://www.techrepublic.com/article/g ... nd-samba-to-work/6353849/

@Raziel

as far as I know, this was just for using Windows Shares in AmigaOS not vica versa!

@MickJT
I'll read through, and report back...thanx

@MickJT

No, sorry that doesn't help. However, is there a possibility to define a "User" and a "password" inside smb.conf or/and Roadshow???

Anybody?

Don't think that it works after Windows XP.
You could use a Virtual machine on your Win10 machine runing Linux with Samba as a bridge to transfer files between the two OS's.

@Spectre660

Actually it does work if you don't mind finding the buried settings in Win10 along with messing with advanced samba materials and making somewhat of a mess with dcpromo stuff under Windows(a Windows NT 4/2000/XP/...) server legacy

I had to deal with this kind of crap some years ago...

I'll have to see about digging out an old config and messing with this junk again.

I've uploaded a new cURL to OS4Depot, and it now supports downloading from and uploading to SMB/CIFS servers.

Downloading examples:

curl -O smb://user:pass@1.2.3.4/folder/file.txt
curl -O -u "domain\username:passwd" smb://server.example.com/share/file.txt

Uploading examples:

curl -T file.txt smb://user:pass@1.2.3.4/folder/
curl -T file.txt -u "domain\username:passwd" smb://server.example.com/share/

It doesn't look like there's a way to list the files, yet.

Keep in mind if you use smb://user:pass@ip, then the file comment will contain the full URL including user and password.

@MickJT

Quote:Well, if nothing else, it can be done with smbclient:

smbclient \\host\share password -U user -c "cd mypath;dir;exit"

You can of course omit the password argument from the command line, then you will be prompted for it.

Best regards,

Niels

@nbache

I forgot that gerograph was trying to connect to Amiga smb shares from Windows, and not the other way around. Does smbfs & smbclient still work connecting to Windows? Checking..

Edit: Getting "Called name not present".

@MickJT

Okay, I tested my smbclient command with an SMB share on a Linux machine.

I don't know explicitly that it will work with Windows, although I'd expect so (at least with Pro/Ultimate etc.).

Best regards,

Niels

I discovered this v.recently, which shows how to disable SMB2/3 on Windows client PCs:
https://support.microsoft.com/en-us/kb/2696547

If you can force SMB1 (by disabling SMB2/3), then it might work on the Amiga?

I also wonder if it might allow SMBFS to work with Windows PCs...?

Thanx for all those advices!

@MickJT
Amiga HD Partitions need to be visible/usable inside Windows Explorer, like a normal Windows HD (drive letters/security are the only things which are NOT of a concern). We are NOT talking about Downloading a file once in a while.

@all
My Amiga MP3 and Image HD Partitions should be usable from Windows (AMIGA = SERVER).

Using a XP Setup inside a VM Environment (Win 10 Pro as host) works out of the box!

Using a different XP Machine also works

Setting up my Amiga as FTP Server could be a way to go, and will be my "fall back" option.

@ChrisH
Thanks for the link, I have to dig into that, but currently this will be on hold, as I am bussy until February

EDIT: I thought I'd gotten SMBFS working with my Windows 7 PC, after fixing a firewall issue. Sadly, although I can now see the files, any attempt to open them just returns garbage :( .

Disabling 128-bit encyption didn't help, nor did disabling SMB2 (using what I previously posted). I am assuming that just restarting the "Server" service is enough to force any SMB registry changes to take effect.

Anyone got any suggestions?

@ChrisH

Yeah, that looks like as far as we can get with our current software. I haven't been able to do any more anyway. What we need is an updated smbfs - the MorphOS version supports SMB2 and works fine with Windows 7 shares.

Anyone familiar enough with that sort of programming to do a port? I'd pay good money to see it!

@Daedalus
are the sources of the MorphOS version available?

@pvanni

Not that I've found. I don't know and it isn't obvious what sort of licence it's under, so it could possibly be a ground-up implementation that has been kept closed source, rather than being based on the open-sourced code of the SMB 1 version. Which is a shame...

@Daedalus
It might be worth emailing the authors of the MorphOS version? (I rather suspect I know what the answer will be, but you don't know for sure until you ask.)

I've had a look on my MorphOS installation before and couldn't find any specific developer or licencing documentation for SMBFS. It is listed as a "port" however so that would suggest it's based on some other code which may or may not stipulate source code availability.

Having a bit of a search now it seems it might not support SMB2 after all, but at least correctly negotiates SMB1 support when connecting to Windows so shares still work properly, and that's still a massive improvement over what we have. I might send them an email but I won't hold my breath for a helpful response.