Groups | Search | Server Info | Login | Register


Groups > comp.os.os2.networking.misc > #139

Re: OS/2 Samba <-> Windows 10 failure

From "Doug Bissett" <dougb007!SPAM@telus.net>
Newsgroups comp.os.os2.networking.misc
Subject Re: OS/2 Samba <-> Windows 10 failure
Date 2016-06-27 16:21 +0000
Organization Aioe.org NNTP Server
Message-ID <SKfw30zmCGmZ-pn2-JmsmTK4ic5KZ@blah.blah.com> (permalink)
References <INZNCBOtXuBC-pn2-dhb9oKqbrNdp@panda2> <nkoguv$vvj$1@news.albasani.net> <INZNCBOtXuBC-pn2-epEFodFckM6K@panda2> <nkpakj$hsp$1@news.albasani.net> <INZNCBOtXuBC-pn2-Kd71OsInLZZ2@panda2>

Show all headers | View raw


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)

Back to comp.os.os2.networking.misc | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

OS/2 Samba <-> Windows 10 failure "LSoens" <nomail@nospam.invalid> - 2016-06-26 11:37 +0000
  Re: OS/2 Samba <-> Windows 10 failure Andreas Kohl <ak120@arcor.de> - 2016-06-26 14:14 +0200
    Re: OS/2 Samba <-> Windows 10 failure "LSoens" <nomail@nospam.invalid> - 2016-06-26 18:01 +0000
      Re: OS/2 Samba <-> Windows 10 failure Andreas Kohl <ak120@arcor.de> - 2016-06-26 21:32 +0200
        Re: OS/2 Samba <-> Windows 10 failure "LSoens" <nomail@nospam.invalid> - 2016-06-27 10:07 +0000
          Re: OS/2 Samba <-> Windows 10 failure "Doug Bissett" <dougb007!SPAM@telus.net> - 2016-06-27 16:21 +0000
          Re: OS/2 Samba <-> Windows 10 failure Andreas Kohl <ak120@arcor.de> - 2016-06-27 19:51 +0200
            Re: OS/2 Samba <-> Windows 10 failure "ivan" <ivanjt@free.fr> - 2016-06-28 11:30 +0000
              Re: OS/2 Samba <-> Windows 10 failure "LSoens" <nomail@nospam.invalid> - 2016-07-22 09:35 +0000
  [SOLVED] Re: OS/2 Samba <-> Windows 10 failure "LSoens" <nomail@nospam.invalid> - 2016-07-25 09:26 +0000
    Re: [SOLVED] Re: OS/2 Samba <-> Windows 10 failure Paul Smedley <paul@smedley.id.au> - 2016-10-03 10:18 +1030
      Re: [SOLVED] Re: OS/2 Samba <-> Windows 10 failure "ivan" <ivanjt@free.fr> - 2016-10-03 00:12 +0000

csiph-web