LSoens schrieb:

Has anybody succeeded to connect OS/2 Samba to Windows 10 shares
and/or vice versa?

- When I connect EVFSGUI client to any Win10 share, I receive "Access denied", but no problem with Win7 Pro.
- Win 7 did connect to eCS shares (Samba 3.3.6 server), but Win 10
denies.
- Linux Mint 17.3 connects with eCS as well as with Win10, either
direction.

For now, this Linux man-in-the middle might be my workaround. Better
ideas welcome :-)

In the network settings you can turn off public folders, 128 bit
encryption and password protection.
Change at least the registry setting for LmCompatibilityLevel=1.


Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Has anybody succeeded to connect OS/2 Samba to Windows 10 shares
and/or vice versa?

- When I connect EVFSGUI client to any Win10 share, I receive "Access
denied", but no problem with Win7 Pro.
- Win 7 did connect to eCS shares (Samba 3.3.6 server), but Win 10
denies.
- Linux Mint 17.3 connects with eCS as well as with Win10, either
direction.

For now, this Linux man-in-the middle might be my workaround. Better
ideas welcome :-)

--
Wegen Unregelmäßigkeiten im Betrieb fährt die Bahn heute pünktlich.
Due to irregular service all trains go on schedule today.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

LSoens schrieb:

On Sun, 26 Jun 2016 12:14:34 UTC, Andreas Kohl <ak120@arcor.de> wrote:

In the network settings you can turn off public folders, 128 bit
encryption and password protection.
Change at least the registry setting for LmCompatibilityLevel=1.

Thanks for your suggestions, Andreas.
But still no luck. Btw, those settings are identical in my Win10 &
Win7 computers, but working with Win7. Win internal firewalls are off.

Which versions and editions of Windows OS were used?
Can you post here protocol bindings of used interfaces?
.. and the registry entries from LAN Manager sections, please.
For the samba side the smb.conf would be useful (but without useless
comments please!)

I suspect there is a built-in hidden feature in Win10: "If 'OS/2' then tackle;" ;-)

No, for what reason?

--
Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 26 Jun 2016 12:14:34 UTC, Andreas Kohl <ak120@arcor.de> wrote:

In the network settings you can turn off public folders, 128 bit
encryption and password protection.
Change at least the registry setting for LmCompatibilityLevel=1.

Thanks for your suggestions, Andreas.
But still no luck. Btw, those settings are identical in my Win10 &
Win7 computers, but working with Win7. Win internal firewalls are off.
I suspect there is a built-in hidden feature in Win10: "If 'OS/2' then
tackle;" ;-)

--
Wegen Unregelmäßigkeiten im Betrieb fährt die Bahn heute pünktlich.
Due to irregular service all trains go on schedule today.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 26 Jun 2016 19:32:45 UTC, Andreas Kohl <ak120@arcor.de> wrote:

Which versions and editions of Windows OS were used?
Can you post here protocol bindings of used interfaces?
.. and the registry entries from LAN Manager sections, please.
For the samba side the smb.conf would be useful (but without useless
comments please!)

Win7 Pro SP1 64bit
Win10 Pro v.1511 b.19586.420

Spent half yesterday and this morning comparing all settings on my Win computers: they look identical (except names). I wouldn't like
flooding this NG with numerous Win registry settings.

Please remember my original question: Has anybody here happened to get
a Samba connection between eCS and Win10. Or could not as well. Btw,
have you tried yourself?

For now, I can live with my workaround, since I don't need continuous
file sharing 24/7.
Thanks for your comments, anyway.

Regards, Lothar

--
Wegen Unregelmäßigkeiten im Betrieb fährt die Bahn heute pünktlich.
Due to irregular service all trains go on schedule today.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 27 Jun 2016 10:07:56 UTC, "LSoens" <nomail@nospam.invalid>
wrote:

On Sun, 26 Jun 2016 19:32:45 UTC, Andreas Kohl <ak120@arcor.de> wrote:

Which versions and editions of Windows OS were used?
Can you post here protocol bindings of used interfaces?
.. and the registry entries from LAN Manager sections, please.
For the samba side the smb.conf would be useful (but without useless comments please!)

Win7 Pro SP1 64bit
Win10 Pro v.1511 b.19586.420

Spent half yesterday and this morning comparing all settings on my Win computers: they look identical (except names). I wouldn't like
flooding this NG with numerous Win registry settings.

Please remember my original question: Has anybody here happened to get
a Samba connection between eCS and Win10. Or could not as well. Btw,
have you tried yourself?

For now, I can live with my workaround, since I don't need continuous
file sharing 24/7.
Thanks for your comments, anyway.

Regards, Lothar

I have win 10 (PRO 64) client using SAMBA in eCS as the server, but it
doesn't work the other way around. The eCS SAMBA client needs work
(for more than just this problem). The immediate problem is in the
user ID/password stuff, which you may be able to work around if you
mess with security settings in windows (I didn't bother). Search the
internet, Linux has the same problems with later versions of windows.

BTW, win 10 seems to have the same settings as win 7, but they added
new settings to do the same things, so you will need to find, and
change the new settings (which I didn't try, yet).

--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello,

LSoens schrieb:

Win7 Pro SP1 64bit
Win10 Pro v.1511 b.19586.420

So changing policies and registry settings seems for now the only way
without bying additional products.

Spent half yesterday and this morning comparing all settings on my Win computers: they look identical (except names). I wouldn't like
flooding this NG with numerous Win registry settings.

Only if something seems to look identically, it doesn't mean that it
behaves identically.
Windows Client OS editions only offer a very limited set of network
settings via GUI. The most important parts have to be changed manually
in the registry. For more than 2 clients it will be useful to save some
time with *.reg files.

This article is quite useful:
<https://support.microsoft.com/en-us/kb/2696547>

Please remember my original question: Has anybody here happened to get
a Samba connection between eCS and Win10. Or could not as well. Btw,
have you tried yourself?

I had similar issues using OS/2 Warp with Windows Server 2012 R2 and Samba-based storage. So I set up an VM in Hyper-V that provides gateway services for legacy clients. This way I would recommend when enough
dedicated network interfaces could be used.

--
Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 27 Jun 2016 17:51:05 UTC, Andreas Kohl <ak120@arcor.de> wrote:

Hello,

LSoens schrieb:

Win7 Pro SP1 64bit
Win10 Pro v.1511 b.19586.420

So changing policies and registry settings seems for now the only way
without bying additional products.

Spent half yesterday and this morning comparing all settings on my Win computers: they look identical (except names). I wouldn't like
flooding this NG with numerous Win registry settings.

Only if something seems to look identically, it doesn't mean that it
behaves identically.
Windows Client OS editions only offer a very limited set of network
settings via GUI. The most important parts have to be changed manually
in the registry. For more than 2 clients it will be useful to save some
time with *.reg files.

This article is quite useful: <https://support.microsoft.com/en-us/kb/2696547>

Please remember my original question: Has anybody here happened to get
a Samba connection between eCS and Win10. Or could not as well. Btw,
have you tried yourself?

I had similar issues using OS/2 Warp with Windows Server 2012 R2 and Samba-based storage. So I set up an VM in Hyper-V that provides gateway services for legacy clients. This way I would recommend when enough
dedicated network interfaces could be used.

--
Andreas

As a point of interest there has been a lot of complaints about win 10
not working with SMB/CIFS on several of the smass NAS forums. Win 10
does not appear to play well with third party software.

ivan
--

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 28 Jun 2016 11:30:36 UTC, "ivan" <ivanjt@free.fr> wrote:

As a point of interest there has been a lot of complaints about win 10
not working with SMB/CIFS on several of the smass NAS forums. Win 10
does not appear to play well with third party software.

The main reason seems to be that Win10-1511 appeared with SMB protocol
3.11, which is part of Samba 4.3.x. Some users reported that
dectivation of SMB3 in Win10 helped for their NAS.

This might also explain why my Win10 connects to my Linux-Mint 17.3 an
vice versa, but not to eCS (client nor server). But I suspect some
more restriction, sind my Linux does well with eCS-Samba.

Lothar

--
Wegen Unregelmäßigkeiten im Betrieb fährt die Bahn heute pünktlich.
Due to irregular service all trains go on schedule today.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)