Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-11 > #18483 > unrolled thread

using the shared folders on the lan

Back to article view | Back to alt.comp.os.windows-11

Contents

  using the shared folders on the lan knuttle <keith_nuttle@yahoo.com> - 2025-04-18 09:37 -0400
    Re: using the shared folders on the lan Graham J <nobody@nowhere.co.uk> - 2025-04-18 14:49 +0100
      Re: using the shared folders on the lan knuttle <keith_nuttle@yahoo.com> - 2025-04-18 11:18 -0400
        Re: using the shared folders on the lan Graham J <nobody@nowhere.co.uk> - 2025-04-18 16:40 +0100
    Re: using the shared folders on the lan Graham J <nobody@nowhere.co.uk> - 2025-04-18 15:26 +0100
      Re: using the shared folders on the lan Valerio Vanni <valerio.vanni@inwind.it> - 2025-04-18 17:54 +0200
        Re: using the shared folders on the lan SOLUTION knuttle <keith_nuttle@yahoo.com> - 2025-04-19 07:16 -0400
          Re: using the shared folders on the lan SOLUTION Andy Burns <usenet@andyburns.uk> - 2025-04-19 14:04 +0100
            Re: using the shared folders on the lan SOLUTION knuttle <keith_nuttle@yahoo.com> - 2025-04-19 13:02 -0400
              Re: using the shared folders on the lan SOLUTION MikeS <mikes@is.invalid> - 2025-04-19 19:11 +0100
    Re: using the shared folders on the lan Paul <nospam@needed.invalid> - 2025-04-18 22:26 -0400
      Re: using the shared folders on the lan Char Jackson <none@none.invalid> - 2025-04-22 20:34 -0500
    Re: using the shared folders on the lan Frank Slootweg <this@ddress.is.invalid> - 2025-04-19 11:34 +0000

#18483 — using the shared folders on the lan

I have been using folders that are shared on the LAN by several 
computers for years on Windows 10 computers.

Now I have upgraded to a new computer with Windows 11 Home.

Now when ever I try to map a network drive I get the message "Windows 
Can not access \\Laptop  (Laptop is the name of the other computer on 
the LAN.)

I have worked on this for a couple of days and can not find why all 
incoming and outgoing activity to LAN devices is blocked.

What am I missing?

[toc] | [next] | [standalone]

#18484

knuttle wrote:
> I have been using folders that are shared on the LAN by several 
> computers for years on Windows 10 computers.
> 
> Now I have upgraded to a new computer with Windows 11 Home.
> 
> Now when ever I try to map a network drive I get the message "Windows 
> Can not access \\Laptop  (Laptop is the name of the other computer on 
> the LAN.)
> 
> I have worked on this for a couple of days and can not find why all 
> incoming and outgoing activity to LAN devices is blocked.
> 
> What am I missing?

There was a really good checklist here several weeks ago - possibly from 
Java Jive.  See if you can find that and work through it ...

How many devices are on your LAN?  What are they, and what OS do they run?


-- 
Graham J

[toc] | [prev] | [next] | [standalone]

#18486

On 4/18/2025 9:49 AM, Graham J wrote:
> knuttle wrote:
>> I have been using folders that are shared on the LAN by several 
>> computers for years on Windows 10 computers.
>>
>> Now I have upgraded to a new computer with Windows 11 Home.
>>
>> Now when ever I try to map a network drive I get the message "Windows 
>> Can not access \\Laptop  (Laptop is the name of the other computer on 
>> the LAN.)
>>
>> I have worked on this for a couple of days and can not find why all 
>> incoming and outgoing activity to LAN devices is blocked.
>>
>> What am I missing?
> 
> There was a really good checklist here several weeks ago - possibly from 
> Java Jive.  See if you can find that and work through it ...
> 
> How many devices are on your LAN?  What are they, and what OS do they run?
> 
> 
They are all computers running the current version of windows 10

There is on printer that appears to be connected to the Windows 11 computer.

[toc] | [prev] | [next] | [standalone]

#18487

knuttle wrote:

[snip]

>> How many devices are on your LAN?  What are they, and what OS do they 
>> run?
>>
>>
> They are all computers running the current version of windows 10

Can all the W10 computers see each other?

> There is one printer that appears to be connected to the Windows 11 
> computer.

Do you mean by USB?  Or the printer is on the LAN and the W11 computer 
can print to it?


I suspect different versions of SMB.  See:

<https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server>

-- 
Graham J

[toc] | [prev] | [next] | [standalone]

#18485

knuttle wrote:
> I have been using folders that are shared on the LAN by several 
> computers for years on Windows 10 computers.
> 
> Now I have upgraded to a new computer with Windows 11 Home.
> 
> Now when ever I try to map a network drive I get the message "Windows 
> Can not access \\Laptop  (Laptop is the name of the other computer on 
> the LAN.)
> 
> I have worked on this for a couple of days and can not find why all 
> incoming and outgoing activity to LAN devices is blocked.

So here's a partial checklist:

1.  Do all the computers and other devices on the LAN get their IP 
addresses by DHCP from a router?  If not, why not?

2.  All Windows machines should have the same "Workgroup" name.

3.  Ensure all 3rd party antivirus has any firewall disabled - at least 
until you get the network to function.

4.  The windows network type should be "Work", not "Private" or 
"Public".  You may be able to get "private" to work later, once you have 
everything set up correctly.

5.  All windows machines should - at the very least - have the same 
username and password for their "Administrator" account.  Ideally they 
should have a separate "User" account with limited permissions for 
everyday use.  The folder(s) that you wish to have available over the 
LAN should have their sharing permissions set correctly.

6.  Test initially using ping from the command line.  Ping by IP address 
until you can confirm that name resolution is working correctly. 
Windows often fails to get this right so you may find it easier to stick 
with IP addresses.  If your router supports "binding" then use it.

7.  Windows explorer should be able to find your networked devices in 
its "Network" setting.  You may be prompted to enable this feature. 
Initially look for shares by IP address, thus: \\<IP>\sharename - you 
should be prompted for the username and password to give access to that 
share.  You may be prompted to save these credentials.  Don't try to get 
mapping working until you can see the network share easily and repeatably.

7.  There are different versions of the SMB protocol that Windows uses 
for file sharing.  Make sure you have the same (most modern) version on 
all your machines.

8.  Once you think you have it working, shut down everything.  Then 
restart the router first, and other computers once the router has its 
internet connection properly established.  Confirm that the networking 
behaves properly.  Be aware that if a machine "sleeps" its networking 
may not behave properly when it is "woken up".


-- 
Graham J

[toc] | [prev] | [next] | [standalone]

#18488

On Fri, 18 Apr 2025 15:26:47 +0100, Graham J <nobody@nowhere.co.uk>
wrote:

>> Now when ever I try to map a network drive I get the message "Windows 
>> Can not access \\Laptop  (Laptop is the name of the other computer on 
>> the LAN.)
>> 
>> I have worked on this for a couple of days and can not find why all 
>> incoming and outgoing activity to LAN devices is blocked.
>
>So here's a partial checklist:

>4.  The windows network type should be "Work", not "Private" or 
>"Public".  You may be able to get "private" to work later, once you have 
>everything set up correctly.

Network types are "private" and "public".

-- 
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.

[toc] | [prev] | [next] | [standalone]

#18496 — Re: using the shared folders on the lan SOLUTION

On 4/18/2025 11:54 AM, Valerio Vanni wrote:
> On Fri, 18 Apr 2025 15:26:47 +0100, Graham J <nobody@nowhere.co.uk>
> wrote:
> 
>>> Now when ever I try to map a network drive I get the message "Windows
>>> Can not access \\Laptop  (Laptop is the name of the other computer on
>>> the LAN.)
>>>
>>> I have worked on this for a couple of days and can not find why all
>>> incoming and outgoing activity to LAN devices is blocked.
>>
>> So here's a partial checklist:
> 
>> 4.  The windows network type should be "Work", not "Private" or
>> "Public".  You may be able to get "private" to work later, once you have
>> everything set up correctly.
> 
> Network types are "private" and "public".
> 
THANK YOU for all of your suggestions.


After working trying to get my new Windows 11 computer to access the 
Shared folders on the LAN, and the problem of staying connected to the 
LAN which developed later, I found that three instructions needed to be 
changed.  I found them after many internet searches.  Apparently Windows 
11 by default will not let what it considers insecure connection.  With 
the router connection to the LAN, and all three computers on the LAN are 
full protected, I feel that my personal system is secure.

After running these three lines and changing the word everything worked 
as I wanted; staying attached to the LAN and being able to use the LAN 
folders on the Window 11 computer

These are run from Terminal (admin).  Each should be copied as one line 
and paste in to the Terminal window.


reg add 
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ /f 
/v RequireSecuritySignature /t REG_DWORD /d 0

reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation /f /v 
AllowInsecureGuestAuth /t REG_DWORD /d 1

reg add 
HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation 
/f /v AllowInsecureGuestAuth /t REG_DWORD /d 1

[toc] | [prev] | [next] | [standalone]

#18503 — Re: using the shared folders on the lan SOLUTION

knuttle wrote:

> reg add 
> HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ / 
> f /v RequireSecuritySignature /t REG_DWORD /d 0
> 
> reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation /f /v 
> AllowInsecureGuestAuth /t REG_DWORD /d 1
> 
> reg add 
> HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation / 
> f /v AllowInsecureGuestAuth /t REG_DWORD /d 1


Never needed to add those reg keys, I suspect a lot depends on what you 
answered to the question that pops up when you first join a network

<https://www.itwriting.com/blog/wp-content/uploads/2013/10/image_thumb.png>

[toc] | [prev] | [next] | [standalone]

#18511 — Re: using the shared folders on the lan SOLUTION

On 4/19/2025 9:04 AM, Andy Burns wrote:
> knuttle wrote:
> 
>> reg add 
>> HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ / 
>> f /v RequireSecuritySignature /t REG_DWORD /d 0
>>
>> reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation / 
>> f /v AllowInsecureGuestAuth /t REG_DWORD /d 1
>>
>> reg add 
>> HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation / f /v AllowInsecureGuestAuth /t REG_DWORD /d 1
> 
> 
> Never needed to add those reg keys, I suspect a lot depends on what you 
> answered to the question that pops up when you first join a network
> 
> <https://www.itwriting.com/blog/wp-content/uploads/2013/10/image_thumb.png>
I checked that.  However those three statements are set by Windows 11 
Default, to prevent connecting to those items that Windows thinks are 
insecure, thus the need to change the to allow those connections.

I do know that I worked for several days trying everything suggested, 
but those lines solved the problem.

[toc] | [prev] | [next] | [standalone]

#18512 — Re: using the shared folders on the lan SOLUTION

On 19/04/2025 18:02, knuttle wrote:
> On 4/19/2025 9:04 AM, Andy Burns wrote:
>> knuttle wrote:
>>
>>> reg add 
>>> HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ 
>>> / f /v RequireSecuritySignature /t REG_DWORD /d 0
>>>
>>> reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation / 
>>> f /v AllowInsecureGuestAuth /t REG_DWORD /d 1
>>>
>>> reg add 
>>> HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation / f /v AllowInsecureGuestAuth /t REG_DWORD /d 1
>>
>>
>> Never needed to add those reg keys, I suspect a lot depends on what 
>> you answered to the question that pops up when you first join a network
>>
>> <https://www.itwriting.com/blog/wp-content/uploads/2013/10/image_thumb.png>
> I checked that.  However those three statements are set by Windows 11 
> Default, to prevent connecting to those items that Windows thinks are 
> insecure, thus the need to change the to allow those connections.
> 
> I do know that I worked for several days trying everything suggested, 
> but those lines solved the problem.

I have a home LAN with three Win 10 PCs to which I added a Win 11 two 
years ago. The existing arrangement for either way sharing between all 
machines needed nothing changed when I added Win 11 (with its default 
settings). All are using Windows Home on a "Private" LAN.

There is just one "secret" which I learned long ago moving from XP to 
10. I give full control of each shared folder or drive to the same user 
on every PC using Advanced sharing / Permissions.

[toc] | [prev] | [next] | [standalone]

#18495

On Fri, 4/18/2025 9:37 AM, knuttle wrote:
> I have been using folders that are shared on the LAN by several computers for years on Windows 10 computers.
> 
> Now I have upgraded to a new computer with Windows 11 Home.
> 
> Now when ever I try to map a network drive I get the message "Windows Can not access \\Laptop  (Laptop is the name of the other computer on the LAN.)
> 
> I have worked on this for a couple of days and can not find why all incoming and outgoing activity to LAN devices is blocked.
> 
> What am I missing?

Be aware, that the nameserver behavior and the Browse Master,
to this day are still flaky. I did an experiment here (just for you),
using three computers, to see how well a "non-domain" configuration
works, and my results were not-good. I tested from a W11 computer,
to a mix of W10 and W11 machines.

But as long as you use the built-in "ipconfig" on each computer,
and you use    \\192.168.1.3\shared
instead of     \\wallace\shared
it should work then.

Those strings are what you type in the File Explorer address bar.

Don't be discouraged, by opening File Explorer and not seeing
the icon for the share server. You can still make a connection,
using the number, despite what the icon situation looks like.

The IP address method of finding another machine,
should work for you, as long as the workgroup
setting is the same on all the "pseudo-domain" home machines.

I can use "nbtscan", to ask each potential address to respond.
Kinda like a ping.

   nbtscan 192.168.100.0/24        # Scans 256 addresses, looking for shares

and then you can have a list of ip address, without knowing
"which one is Wallace". But for your purposes, using the
built-in "ipconfig" command and discovering the IP address
of the various machines, would also give the same info if you
needed an IP address to reach a share you created on it.

We do that for Linux, where the record on the icon situation
is not all that good either.

   explorer \\wallace\shared
   explorer \\192.168.1.3\shared   # Works on Windows, when the other format logically does not work

   nemo smb://wallace/shared
   nemo smb://192.168.1.3/shared   # Works on Linux,   when the other format logically does not work

If you really want the icons to show up, you can try
starting your LAN with just the router powered. Then
boot up the Win7 machine and wait a few minutes until
the desktop settles. This will allow the win7 machine to become
the Browse Master. Then, when subsequent machines start, you
may discover that everyone has working network icons. That's
the only correlation I've seen, on the home LAN, is starting
the old OS first, might make for a better server of names.
Since this is normally too much work, to do a controlled
LAN bring-up, you can use IP address syntax instead.

  Paul

[toc] | [prev] | [next] | [standalone]

#18610

On Fri, 18 Apr 2025 22:26:10 -0400, Paul <nospam@needed.invalid> wrote:

>On Fri, 4/18/2025 9:37 AM, knuttle wrote:
>> I have been using folders that are shared on the LAN by several computers for years on Windows 10 computers.
>> 
>> Now I have upgraded to a new computer with Windows 11 Home.
>> 
>> Now when ever I try to map a network drive I get the message "Windows Can not access \\Laptop  (Laptop is the name of the other computer on the LAN.)
>> 
>> I have worked on this for a couple of days and can not find why all incoming and outgoing activity to LAN devices is blocked.
>> 
>> What am I missing?
>
>Be aware, that the nameserver behavior and the Browse Master,
>to this day are still flaky. I did an experiment here (just for you),
>using three computers, to see how well a "non-domain" configuration
>works, and my results were not-good. I tested from a W11 computer,
>to a mix of W10 and W11 machines.
>
>But as long as you use the built-in "ipconfig" on each computer,
>and you use    \\192.168.1.3\shared
>instead of     \\wallace\shared
>it should work then.
>
>Those strings are what you type in the File Explorer address bar.
>
>Don't be discouraged, by opening File Explorer and not seeing
>the icon for the share server. You can still make a connection,
>using the number, despite what the icon situation looks like.
>
>The IP address method of finding another machine,
>should work for you, as long as the workgroup
>setting is the same on all the "pseudo-domain" home machines.

One of the nice things about accessing a Windows computer by its IP
address is that the workgroup name is irrelevant. Or at least it was
irrelevant from Win 95 thru Win 10. I can't speak for Win 11.


>I can use "nbtscan", to ask each potential address to respond.
>Kinda like a ping.
>
>   nbtscan 192.168.100.0/24        # Scans 256 addresses, looking for shares
>
>and then you can have a list of ip address, without knowing
>"which one is Wallace". But for your purposes, using the
>built-in "ipconfig" command and discovering the IP address
>of the various machines, would also give the same info if you
>needed an IP address to reach a share you created on it.
>
>We do that for Linux, where the record on the icon situation
>is not all that good either.
>
>   explorer \\wallace\shared
>   explorer \\192.168.1.3\shared   # Works on Windows, when the other format logically does not work
>
>   nemo smb://wallace/shared
>   nemo smb://192.168.1.3/shared   # Works on Linux,   when the other format logically does not work
>
>If you really want the icons to show up, you can try
>starting your LAN with just the router powered. Then
>boot up the Win7 machine and wait a few minutes until
>the desktop settles. This will allow the win7 machine to become
>the Browse Master. Then, when subsequent machines start, you
>may discover that everyone has working network icons. That's
>the only correlation I've seen, on the home LAN, is starting
>the old OS first, might make for a better server of names.
>Since this is normally too much work, to do a controlled
>LAN bring-up, you can use IP address syntax instead.
>
>  Paul

[toc] | [prev] | [next] | [standalone]

#18497

knuttle <keith_nuttle@yahoo.com> wrote:
> I have been using folders that are shared on the LAN by several 
> computers for years on Windows 10 computers.
> 
> Now I have upgraded to a new computer with Windows 11 Home.
> 
> Now when ever I try to map a network drive I get the message "Windows 
> Can not access \\Laptop  (Laptop is the name of the other computer on 
> the LAN.)

  FWIW, I get this error when I don't specify the name of the share on
the remote host.

  I.e. if I do a 'Map Network Drive' in File Explorer and put only
'\\Laptop' in the 'Folder:' field, I get the error "Windows cannot
access \\Laptop".

  But if I specify '\\Laptop\c' in the field, the 'Map Network Drive'
operation succeeds (assuming no other issues, like the remote C: drive
not being shared).

> I have worked on this for a couple of days and can not find why all 
> incoming and outgoing activity to LAN devices is blocked.
> 
> What am I missing?

[toc] | [prev] | [standalone]

Back to top | Article view | alt.comp.os.windows-11

csiph-web