NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
EruvWeather, TheEther, guys, this is driving me nuts...
As it stands NOW my wife's PC continues to have NET VIEW work properly, and has since I did a clean install of her X64 W10 Pro Ver. 1709. On the other hand mine will only work IF I reboot the Router and her PC is not on. Once her's comes on, it no longer works, and will never work again until I reboot the router.
I opened the POWERSHELL on both PC's and ran "get-smbserverconfiguration" and compared results.
Interesting, on mine EnableSMB1Protocol is set to True, but on her's, it is set to False?
Checking Features installed I have SMB1 Server checked where her's has Client checked?
Odd, what do you have?
I've set mine to Client now but need to re-boot. Will update when I come back on.
EDIT:
FIXED IT!!!!
GET-SMBSERVERCONFIGURATION now matches her's and it WORKS as expected!!!
C:\>net view
Server Name Remark
---------------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500 Laraine's XPS8500
\\READYSHARE readyshare
The command completed successfully.
I don't KNOW how my SMB1 features were set or when, or even why.
Suspect at this point a change happened during one of MS's Updates?
Searching the web I found this page, https://community.spiceworks.com/topic/1995592-disabling-smb1-stops-domain-authentication marked SOLVED.... in it:
-------------
Did you try just disabling smbv1 and not actually removing the windowsfeature?
edit: by running this command in an elevated powershell prompt:
Set-SmbServerConfiguration -EnableSMB1Protocol $false
---------------------
Wonder if I did that it would have fixed it as well?
EruvWeathergive this a try... might just work!
This sounds very much like a Windows issue.
Your PC knows nothing about the firmware on your router. There aren't any drivers either.
Any drivers are related to the network hardware on your PC, wifi and Ethernet.
.... I'm on Windows 10, version 1709, which was installed on 10/18/2017, which could very well have been the last time it worked OK? Either that or a firmware problem but I don't know which firmware it started with?
That build has been out there for some time. If it were causing major issues we would have heard about it here. That is, though, a clue worth pursuing. Maybe there was something in the update that messed up your local network stuff.
I assume that you have been through the process of restarting your whole network in the recommended way.
Be sure to restart your network in this sequence:
You might like to reset the router too. It may not help, but there are times when it can magically restore sanity. You won't lose anything, especially if you save a backup of your configuration. But be careful about restoring that backup. It may bring back problems.
You say nothing about the modem involved in this saga. Remember, that is also an important part of the network and has to be properly configured to work with a router.
michaelkenward wrote:This sounds very much like a Windows issue.
That is what I thought too... tried everything I know, and like I said there is virtually no help for error 1231.
michaelkenward wrote:
Your PC knows nothing about the firmware on your router. There aren't any drivers either.
Agreed, but then how do you explain rebooting the router cures it for a short time or just enabling or disabling UPnP makes it work without doing anything on W10, not even a restart of the PC. Just wait for the Router to come up. That and the fact that while the router appears to be on the network but not showing in NET VIEW or EXPLORER++ the SAMBA server still works but not the DLNA server on the Router?
michaelkenward wrote:Any drivers are related to the network hardware on your PC, wifi and Ethernet.
.... I'm on Windows 10, version 1709, which was installed on 10/18/2017, which could very well have been the last time it worked OK? Either that or a firmware problem but I don't know which firmware it started with?
That build has been out there for some time. If it were causing major issues we would have heard about it here. That is, though, a clue worth pursuing. Maybe there was something in the update that messed up your local network stuff.
I assume that you have been through the process of restarting your whole network in the recommended way.
Be sure to restart your network in this sequence:
- Turn off and unplug the modem.
- Turn off the modem router and computers.
- Plug in the modem and turn it on. Wait 2 minutes.
- Turn on the modem router and wait 2 minutes.
- Turn on the computers.
You might like to reset the router too. It may not help, but there are times when it can magically restore sanity. You won't lose anything, especially if you save a backup of your configuration. But be careful about restoring that backup. It may bring back problems.
Yes, did all that, many times. That is how I discovered the problem could be cured with rebooting the router only. Matter of fact, it is still working fine now:
=========
C:\Users\ispal_000>net view
Server Name Remark
--------------------------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
\\READYSHARE readyshare
The command completed successfully.
=============
Compared to my original post you'll see my wife's PC was turned on and picked up fine as well. It seems the UPnP must be enabled as well for the NET VIEW command to work? I know when I was troubleshooting and I was trying to determine what might have an effect on NET VIEW in terms of settings. NET VIEW wasn't working and I did TURN OFF UPnP and NET VIEW started to work. However with it OFF even rebooting the router didn't make NET VIEW work. Once I enabled UPnP again (without the router reboot) NEW VIEW started to work again? Could it have something to do with W10 and SM1/3? Don't think so, otherwise I'd have discovered this problem with others on the web. W10 1509 had this problem (1231 error) and that was while in Beta. Nothing since.
michaelkenward wrote:You say nothing about the modem involved in this saga. Remember, that is also an important part of the network and has to be properly configured to work with a router.
I did have a modem replaced about a month ago too. I did the normal 'bring up process' and all seemed to work fine. Like I said, I can't tell for sure when this started. I first noticed it when I tried to use a DLNA Client on my iPad and it did see the R7000 but never could see anything below that, like the shares. Then discovered the SAMBA client worked though? Next I did the NET VIEW on the PC and discovered the problem with it. Not touching ANYTHING else I rebooted the router and the iPad DLNA client and NET VIEW on the PC worked fine. I can't even think of how this could be a W10, modem, or even iPad problem (when I first discovered this I did reboot the iPad and that didn't help).
Might want to look here, https://community.netgear.com/t5/Nighthawk-WiFi-Routers/R7000-Rreadyshare-stopped-working/td-p/1459291/jump-to/first-unread-message, fairly similar problem. That one had the problem on both W7 and W10, so that also should suggest the problem is not in Windows but somehow caused by the router I'd think?
Agreed, but then how do you explain rebooting the router cures it for a short time or just enabling or disabling UPnP makes it work without doing anything on W10, not even a restart of the PC.
By doing this you are forcing the local network, your PC, to reestablish a network connection.
Sadly, this repair does not persist, because whatever is going on on your PC kicks in again.
That's just a theory, but one based on my own current grief with a local network that, on one PC only, suddenly drops its speed to a crawling pace. It all started when the LAN port on my motherboard died and I had to install a PCI LAN card. But you don't want to know about that!
See my response to TheEther and some more discovery I did.
See the last part though when I disconnected and reconnected the USB drive from the Router. Merely disconnecting it changed the error code that Windows produced. Reconnecting it 'repaired' NET VIEW. Yes, reconnecting it would allert the router there was an added share to handle, but that was INTERNAL to the router. At first the USB Drive is not really available as the disk was being read, but that was enough to make NET VIEW work again, and once the disk was read, a subsequent NET VIEW did add that share. All done with no change on either PC.
So let us assume 'something' I'm running would cause this to break? It isn't my wife's machine either, and that wasn't on the last time this happened. I can't trust letting the PC sit and 'things' happen all the time when connected to the Inet. Also I've had this happen when ALL PC's were off, just last night for instance. Before I shutdown this PC (only one on) I did a NET VIEW and the Router Share was seen. It WAS not when I booted this PC this morning, and the reason I opened this topic.
I am NOT discounting it could still be a W10 or some program doing something to damage the ability to see the LAN with NET VIEW, but again, since I know the SHARE names even when NET VIEW itself fails, NET VIEW \\SHARENAME works, so that too sort of rules out possibly a W10 problem, no?
I am at a loss how to CAPTURE the real culprit here? Surprised others (other than that one link I posted) are not experencing this too? Not many use USB drives? USB drive problem? It all worked fine before though?
TheEther, there are some things in my mind that rule out Windows... NOT one report of this on the latest Fall Update version, 1709. The other link I posted to a thread here that had both W10 and W7 doing it.
My first posting had shown only HARD WIRED stuff between my PC (IRV8700) and the Router (192.168.1.1) and the USB drive (READYSHARE). Later posting showing my Wife's PC coming on-line and that is WIRELESS. There are other devices that are wireless connected all the time though, like Amazon FireTV stick and Echo, iPad's, and when on, a SmartTV. Nothing else. All those were on when I ran NET VIEW.
Saw the FIRST link and I did change the SERVICES to AUTOMATIC with no change.
2nd link is for a BETA and almost 2 years old.
3rd one had a fairly recent response and claimed 1709 fixed the problem.
My thought right now lead me to the FIRMWARE. I really suspect 'over time' something drops or changes in the Router and it can't respond to the broadcast and W10 can't handle the 'error' or it sends back something W10 can't handle and posts the error.
Well, I just tried NET VIEW again:
C:\>net view
System error 1231 has occurred.
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
Nothing has changed on either PC... sometime between may last post 8:54AM and now it started to fail again. I'm sure if I reboot the router (or possibly disable UPnP) it will be working again.
It could very well be connected to the USB share too? It seems strange to me that when my iPad's program I use that has both a DLNA and SAMBA client if the DLNA client can't see the share other than the router itself, but the SAMBA client has no problem, it is somehow connected to what the Router is presenting to the LAN. That takes W10's PC out of the equation, no?
Thinking along the lines that it might be the USB share, I did the Safely Remove and once it was ran NET VIEW again, and got a COMPLETELY different error :
C:\>net view
System error 53 has occurred.
The network path was not found.
Weird??? Adding MORE questions... I pulled the USB cable and plugged it back in. Immediately ran NET VIEW (disk is active, probably rebuilding the DLNA catalog as the light shows drive being read, and got this:
C:\>net view
Server Name Remark
---------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
The command completed successfully.
Just removing the USB drive allowed NET VIEW to show me the REST of the LAN?
Ahh, waiting for the USB Drive light to stop flickering:
C:\>net view
Server Name Remark
----------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
\\READYSHARE readyshare
The command completed successfully.
At this point I'm 'declaring' it IS NOT W10, but something to do with the firmware, probably similar to WIFI being lost, but this has to do with the USB Drive, and it is causing responses back to the NEW VIEW command in Windows to be 'bad' and W10, if anything' doesn't know how to handle it and throws a useless error...
Now the REAL question is do OTHERS have this problem? I did 'report' this in the lastest firmware thread, even using JamesGL but never got an answer.
Again, NOTHING was changed in either PC or other attached device, and all done here on my W10 1709 release PC as I entered the NET VIEWS.
