Groups | Search | Server Info | Login | Register


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

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

From Andreas Kohl <ak120@arcor.de>
Newsgroups comp.os.os2.networking.misc
Subject Re: OS/2 Samba <-> Windows 10 failure
Date 2016-06-27 19:51 +0200
Organization albasani.net
Message-ID <nkrp1v$ar2$1@news.albasani.net> (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


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

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