1. Forum
  2. ILink
  3. IL NETWORKS

  • Why Windows won't speak t

    From Ky Moffet@454:1/1 to All on Tuesday, November 12, 2024 23:17:00
    This appears to be the problem:

    https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by-default-in-windows

    For the 2016 release of Win10 and before, networked PCs speak to each
    other with SMB1.x; now only with SMB2.x or later.

    Which means that new Win10/11 box cannot see the older box, and v.v. Or
    at least only intermittenently.

    If I'd wanted networking problems among mixed species of OS, I'd already
    be entirely on linux.....
    * RNET 2.10U: ILink: Techware BBS * Hollywood, Ca * www.techware2k.com

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com (454:1/1)
  • From Barry Martin@454:1/1 to Ky Moffet on Thursday, November 14, 2024 07:14:00


    Hi Ky!

    This appears to be the problem: https://learn.microsoft.com/en-us/windows-server/storage/file-serv er/troublesho
    t/smbv1-not-installed-by-default-in-windows
    For the 2016 release of Win10 and before, networked PCs speak to
    each other with SMB1.x; now only with SMB2.x or later.
    Which means that new Win10/11 box cannot see the older box, and
    v.v. Or at least only intermittenently.
    If I'd wanted networking problems among mixed species of OS, I'd
    already be entirely on linux.....

    You'll be glad to know even Linux (or at least Ubuntu) had this problem
    some years back. My old NAS would not talk to some of the new computers (probably with newer OS versions). Ended up I had to tell the mount
    line in fstab to use "vers=1.0".


    > <
    > BarryMartin3@MyMetronet.NET <
    > <


    ... I ate natural foods until I learned most people die of natural causes.
    --- MultiMail/Win32 v0.47
    * wcECHO 4.2 = ILink: The Safe BBS * Bettendorf, IA

    --- QScan/PCB v1.20a / 01-0462
    * Origin: ILink: CFBBS | cfbbs.no-ip.com (454:1/1)