Inexplicable network failure

Dear knowledgeable folks.

My daughter's machine is set up to manage shares via password (not
managed via workgroup) and has several SMB shares available. All
permissions are set correctly for the shares to be accessed by other
computers.

Every other computer on the network, when accessed, gives either a
password prompt, where password shares are enabled, or immediate
anonymous access where it does not require passwords.

Her computer, named RAVEN, flat out denies access. Not even a password
prompt. It just tells you that you don't have access to that computer, as
if it is offline.

I've done advanced troubleshooting, like checking secpol.msc, especially
the "Network access: Do not allow anonymous enumeration of SAM accounts
and shares." Everything in local security is set to the defaults on her
system.

It used to allow anonymous access to the shares with no password.

I checked, and she is on a private network; it doesn't show as public.
Same subnet. Same workgroup. I tried reinstalling "Client for MS
networks" and "File and Printer Sharing for Microsoft Networks" and
rebound them to the adapter. No dice.

It is a wireless adapter: Wireless n, running on the 5Ghz spectrum. I
haven't tried the 2.4Ghz spectrum.

The only other symptom is that the network browser in explorer on her
system only shows her computer, RAVEN. It does not show the other
computers on the network. If I type in a hard URI "\\STARLING" into the
explorer address box, it brings up the shares on the other server, but
STARLING does not appear in explorer. STARLING is the master browser.
"nbtstat -a STARLING" executed on RAVEN shows the MSBROWSE line. Wireless
printers and the access points do show up enumerated, however.

All systems are running the latest update of Win 10 Creators edition. I
don't know when her system stopped working with networking. It used to
work, and then one day it didn't.

Any ideas what might fix it?

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

On Sun, 23 Jul 2017 09:58:23 -0500, in alt.comp.os.windows-10, Zaghadka
wrote:

All systems are running the latest update of Win 10 Creators edition. I
don't know when her system stopped working with networking. It used to
work, and then one day it didn't.

Any ideas what might fix it?

One last data point. Although I can tick the radio button for "Turn off
password protected sharing," RAVEN will not retain the setting. It always
goes back to "on."

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

On Sun, 23 Jul 2017 09:58:23 -0500, in alt.comp.os.windows-10, Zaghadka
wrote:

All systems are running the latest update of Win 10 Creators edition. I
don't know when her system stopped working with networking. It used to
work, and then one day it didn't.

Any ideas what might fix it?

I tried manually changing the two keys in the registry that govern
password protected sharing, and the settings were retained on reboot, but
the radio button still indicates "turn on password protected sharing"
despite the fact that it is turned off in the registry.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

In article ,
, Zaghadka says...

Dear knowledgeable folks.

My daughter's machine is set up to manage shares via password (not
managed via workgroup) and has several SMB shares available. All
permissions are set correctly for the shares to be accessed by other
computers.

Every other computer on the network, when accessed, gives either a
password prompt, where password shares are enabled, or immediate
anonymous access where it does not require passwords.

Her computer, named RAVEN, flat out denies access. Not even a password
prompt. It just tells you that you don't have access to that computer, as
if it is offline.

I've done advanced troubleshooting, like checking secpol.msc, especially
the "Network access: Do not allow anonymous enumeration of SAM accounts
and shares." Everything in local security is set to the defaults on her
system.

It used to allow anonymous access to the shares with no password.

I checked, and she is on a private network; it doesn't show as public.
Same subnet. Same workgroup. I tried reinstalling "Client for MS
networks" and "File and Printer Sharing for Microsoft Networks" and
rebound them to the adapter. No dice.

It is a wireless adapter: Wireless n, running on the 5Ghz spectrum. I
haven't tried the 2.4Ghz spectrum.

The only other symptom is that the network browser in explorer on her
system only shows her computer, RAVEN. It does not show the other
computers on the network. If I type in a hard URI "\\STARLING" into the
explorer address box, it brings up the shares on the other server, but
STARLING does not appear in explorer. STARLING is the master browser.
"nbtstat -a STARLING" executed on RAVEN shows the MSBROWSE line. Wireless
printers and the access points do show up enumerated, however.

All systems are running the latest update of Win 10 Creators edition. I
don't know when her system stopped working with networking. It used to
work, and then one day it didn't.

Any ideas what might fix it?

If you're running W10, about V1607 or better, check out their 'network
reset' option. (One way to get it, click Start and just start typing
'network reset'.)

It resets a lot of stuff!

It worked for me, where a month or two back, MS (from what I can work
out) put out some updates that stuffed up folks WiFi - and made 'em
crawl - almost unusable internet. The network reset fixed it (albiet
termporarily until the PC updated again). Nothing else I tried
worked... rollback driver, IP stack reset, etc. The (new) Windows 10
'Network reset' worked a charm.

--
Duncan.

On Mon, 24 Jul 2017 14:40:47 +1200 "Dave Doe" wrote in
article
click Start and just start typing
'network reset'.)

I tried this because I've been experiencing wifi issues recently.
Typing 'network reset' doesn't bring up anything like a network
reset :-(

En el artículo , Zaghadka
escribió:

Any ideas what might fix it?

It sounds as if the browser service is not running. Try this:

In an elevated command prompt:

net stop browser

then

net start browser

if that then works to browse for remote shares, check out services.msc
to see if the Browser service is enabled on startup.

I find myself wondering if the recent patch for the WannaCry worm (which
disables SMBv1) is in some way responsible for your issues.

--
(\_/)
(='.'=) "Between two evils, I always pick
(")_(") the one I never tried before." - Mae West

In article ,
, Jason says...

On Mon, 24 Jul 2017 14:40:47 +1200 "Dave Doe" wrote in
article
click Start and just start typing
'network reset'.)

I tried this because I've been experiencing wifi issues recently.
Typing 'network reset' doesn't bring up anything like a network
reset :-(

Jeez, gotta ask, what version of W10 is it running? (Settings, System,
About)

--
Duncan.

Jason wrote:
On Mon, 24 Jul 2017 14:40:47 +1200 "Dave Doe" wrote in
article
click Start and just start typing
'network reset'.)

I tried this because I've been experiencing wifi issues recently.
Typing 'network reset' doesn't bring up anything like a network
reset :-(

Control.exe
Troubleshooting
Search "network"

That gives "Network Adapter" as a suspect.

*******

And lines like this entered in Google, can dig up the usual suspects.

netsh int ip reset c:\resetlog.txt

Typically the stuff kicking around forums looks
like this, and some of the lines from here, can
help you find some networking threads. A networking
thread with 250 pages though, would be pretty daunting
to read from end to end.

netsh winsock reset
netsh int ip reset
netsh int ipv4 reset
netsh int ipv6 reset
ipconfig /renew
ipconfig /flushdns

And the netsh thing, is a pretty talented piece of work.
My log file is littered with stuff like this
(with no notes about why I'd want it particularly).

netsh wlan show drivers

netsh wlan show profiles
netsh wlan delete profile name="WirelessProfileName"

If you do a google search with

site:tenforums.com

and some of those keywords, you might dredge up
some more gems.

HTH,
Paul

On Mon, 24 Jul 2017 06:44:35 -0400, in alt.comp.os.windows-10, Paul
wrote:

Jason wrote:
On Mon, 24 Jul 2017 14:40:47 +1200 "Dave Doe" wrote in
article
click Start and just start typing
'network reset'.)

I tried this because I've been experiencing wifi issues recently.
Typing 'network reset' doesn't bring up anything like a network
reset :-(

Control.exe
Troubleshooting
Search "network"

That gives "Network Adapter" as a suspect.


The "Incoming Connections" troubleshooter looked to be the most
promising. It had me attempt to access the borked machine in the middle
of the troubleshooter. The access attempt failed.

Eventually it came back with a "not fixed" "Windows troubleshooter needs
more information" error message. It was unable to pinpoint what went
wrong, just that the request didn't go through. Since the machine is
effectively isolated from LAN traffic, that makes a lot of sense.

It also dumped a bunch of .etl logs that I don't know how to access. When
I clicked on the link in the troubleshooter, it opened the file locally
in IE, but all that appears on the page is a black "X" in the upper left
hand corner. Do you know how to read error logs in Windows 10?

There is a bunch of diagnostic information included with the
troubleshooter. It might be the contents of the .etl file. Should I post
it?

I had previously stopped SMB 2.0/3.0 on this machine because of a network
browsing issue where only SMB 1.0 would see the machines on the network.
Microsoft has since fixed that issue, and I turned it back on. I checked.
It's on.

I did some PowerShell:

Get-SmbConnection returns a null reply.
Get-SmbServerConfiguration shows SMB 1.0, 2.0 and 3.0 active.
Get-SmbClientConfiguration shows a bunch of data I don't understand.
Get-SmbShareAccess shows that the shares (two of them at least) are set
for Everyone, Full access, Allowed.

Basically, all the SMB diagnostics are showing that nothing is wrong at
all.

I'm beginning to wonder if this *is* related to the WannaCry patch. I
should open a ticket at the MS forums, but I suspect all they'll tell me
to do is do a system refresh, which I am unwilling to do at this time.

At this point, I have a workaround. I can always type in the hard URI of
the main server in my house to get access to the network servers on the
borked machine, even though the server doesn't show up in the browser,
and get to the network that way. The machines are in two rooms that are
close together, so I can get by with that until it is fixed.

WAN (Internet, Wifi, router gateway etc.) works fine. It's just the
LANManager/TCP-IP encapsulated NetBEUI stuff that's failing. Her Internet
got borked at one point and I had to uninstall/reinstall the Wifi card
drivers to resolve the issue. I suspect that's when this all went wrong,
but I can't be sure. I've tried unbinding, rebinding MS network
client/server and uninstalling/reinstalling MS client/server; it didn't
fix it.

Sucks.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

Zaghadka wrote:
On Mon, 24 Jul 2017 06:44:35 -0400, in alt.comp.os.windows-10, Paul
wrote:

Jason wrote:
On Mon, 24 Jul 2017 14:40:47 +1200 "Dave Doe" wrote in
article
click Start and just start typing
'network reset'.)
I tried this because I've been experiencing wifi issues recently.
Typing 'network reset' doesn't bring up anything like a network
reset :-(
Control.exe
Troubleshooting
Search "network"

That gives "Network Adapter" as a suspect.


The "Incoming Connections" troubleshooter looked to be the most
promising. It had me attempt to access the borked machine in the middle
of the troubleshooter. The access attempt failed.

Eventually it came back with a "not fixed" "Windows troubleshooter needs
more information" error message. It was unable to pinpoint what went
wrong, just that the request didn't go through. Since the machine is
effectively isolated from LAN traffic, that makes a lot of sense.

It also dumped a bunch of .etl logs that I don't know how to access. When
I clicked on the link in the troubleshooter, it opened the file locally
in IE, but all that appears on the page is a black "X" in the upper left
hand corner. Do you know how to read error logs in Windows 10?

There is a bunch of diagnostic information included with the
troubleshooter. It might be the contents of the .etl file. Should I post
it?

I had previously stopped SMB 2.0/3.0 on this machine because of a network
browsing issue where only SMB 1.0 would see the machines on the network.
Microsoft has since fixed that issue, and I turned it back on. I checked.
It's on.

I did some PowerShell:

Get-SmbConnection returns a null reply.
Get-SmbServerConfiguration shows SMB 1.0, 2.0 and 3.0 active.
Get-SmbClientConfiguration shows a bunch of data I don't understand.
Get-SmbShareAccess shows that the shares (two of them at least) are set
for Everyone, Full access, Allowed.

Basically, all the SMB diagnostics are showing that nothing is wrong at
all.

I'm beginning to wonder if this *is* related to the WannaCry patch. I
should open a ticket at the MS forums, but I suspect all they'll tell me
to do is do a system refresh, which I am unwilling to do at this time.

At this point, I have a workaround. I can always type in the hard URI of
the main server in my house to get access to the network servers on the
borked machine, even though the server doesn't show up in the browser,
and get to the network that way. The machines are in two rooms that are
close together, so I can get by with that until it is fixed.

WAN (Internet, Wifi, router gateway etc.) works fine. It's just the
LANManager/TCP-IP encapsulated NetBEUI stuff that's failing. Her Internet
got borked at one point and I had to uninstall/reinstall the Wifi card
drivers to resolve the issue. I suspect that's when this all went wrong,
but I can't be sure. I've tried unbinding, rebinding MS network
client/server and uninstalling/reinstalling MS client/server; it didn't
fix it.

Sucks.


Wireshark is the only other tool I could suggest
at this point. It shows Network Browser traffic with
different color packets. And it has an SMB dissector.
But the dissector doesn't break down what the bitfields
are. I have a WannaCrypt-patch-related problem here, and that's
about as close as I got to fixing it. The client machine is
the one with the problem, but it's the serving side that throws
up some sort of "needs more info" error, that stops file sharing.

Paul