NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
I really don't know when it started? I could always see the Router in NEW VIEW or using my Windows Explorer replacement Explorer++? Now I can't always do that?
When I run NET VIEW this is the result:
==================
C:\>net view
System error 1231 has occurred.
The network location cannot be reached. For information about network troubleshoting, see Windows Help.
==================
Googling that doesn't find anything useful, 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?
I've downgraded the firmware all the way back to V1.0.9.4, and all releases in between. Same problem exists?
I do KNOW the names of the PC and Router on the LAN, so individual NET VIEWS work fine? For instance:
==============
C:\>net view \\irv8700
Shared resources at \\irv8700
Irv's 8700
Share name Type Used as Comment
-------------------------------------------------------------------------------
C_8700 Disk
K_8700 Disk
L_disk Disk
Users Disk
The command completed successfully.
C:\>net view \\192.168.1.1
Shared resources at \\192.168.1.1
readyshare
Share name Type Used as Comment
-------------------------------------------------------------------------------
USB_Storage Disk read:admin;write:admin
The command completed successfully.
C:\>net view \\readyshare
Shared resources at \\readyshare
readyshare
Share name Type Used as Comment
-------------------------------------------------------------------------------
USB_Storage Disk read:admin;write:admin
The command completed successfully.
===========================
On occasions, rebooting the router fixes the problem for a short time. Same goes for turning on or off UPnP?
I just REBOOTED the router and that didn't help. Had UPnP off, so I turned it on, that 'fixed' it:
==============
C:\>net view
Server Name Remark
-------------------------------------------------------------------------------
\\IRV8700 Irv's 8700
\\READYSHARE readyshare
The command completed successfully.
============
However I know in a short period of time the READYSHARE will disappear and I'll be back to the 1231 error.
I do use the Router with a USB drive to share movies. My iPad's Media Server programs work fine, until something happens and they can't see the shared DLNA server. The Samba Server will always work though? Annoying in that if I want to use the DLNA client I must reboot the router.
Anyone else see this? It seems to be UPnP is required to make NEW VIEW work right now, but in the past turning it off make it work too? Still it fixed the problem only for a short time?
Any suggestions? Other than this I've NOT had a problem with any of the V1.0.9.xx firmware releases?
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!
I am having the exact same issue on my Windows 10 system. Latest R7000 firmware. My Windows 7 system has no issues, nor does another Win10 system on my network.
The Win10 system in question can reach the other computer in the network listing in Explorer, but readyshare only by manually entering the \\readyshare address in the address bar.
I am also getting the 1231 error when running net view at the command prompt.
I noticed the behavior when upgrading from 1.0.7.12 to 1.0.9.14 and now .18.
Have not tried toggling UPnP.
Seems cosmetic at one level, since I can reach the other systems and network printers -- and even readyshare after a delay in explorer, but the network listing in explorer does not include readyshare or the printers. The only culprit left from my own digging on this issue is the router ... and it is quite frustrating.
Interesting...
EruvWeather wrote:I am having the exact same issue on my Windows 10 system. Latest R7000 firmware. My Windows 7 system has no issues, nor does another Win10 system on my network.
The Win10 system in question can reach the other computer in the network listing in Explorer, but readyshare only by manually entering the \\readyshare address in the address bar.
I am also getting the 1231 error when running net view at the command prompt.
I noticed the behavior when upgrading from 1.0.7.12 to 1.0.9.14 and now .18.
What is the difference between the W10 PC that works and the one that doesn't? At they the same? Same W10 version, same edition (Pro/Home)?
Although both rebooting the router and changing things like UPnP's state will make my W10 Home 1709 version work, it is only temporary.
EruvWeather, I am at a TOTAL loss here...
Before my wife got up I rebooted the router. Of course NET VIEW worked after that just fine. I went and had breakfast and for over an hour my PC say idle, and even the display and hard disk went to 'sleep'. Woke it up and ran NET VIEW:
C:\>net view
Server Name Remark
---------------------------------------
\\IRV8700 Irv's 8700
\\LARAINE-XPS8500
\\READYSHARE readyshare
The command completed successfully.
Still working, good. Since my wife's PC is now on I went to it since it is a W10 PRO. Surprise, it gets a 1231 error from NET VIEW!!!
This is all very confusing to me? We both have the same W10 release, 1709, and even similar h/w but one is HOME edition and the other PRO? I know you have similar results, one W10 PC works, the other doesn't?
I almost suspect some sort of 'connection' needs to be made between the router and PC when the router comes up or reboots? Once up and another PC comes on-line it will not work for that PC maybe? Might explain why when it was working fine one night before I shutdown it failed the next morning?
The PC must talk to the Router when it starts, if nothing else, to get its IP Address and Internet access. Hmm, this could be a large clue! Both of these PC's have a router assigned/reserved IP Address. Wonder if that could have something to do with it? On the one that fails for you, it is a reserved IP Address and the other isn't?
I wouldn't expect to see the actual words "NET VIEW" in a packet capture. It's just a Windows command. You certainly don't see "PING" in a ping packet, which is just an ICMP echo request.
224.0.0.252 is the address used for LLMNR (Link Local Multicast Name Resolution). It was designed by Microsoft and is very similar to mDNS. I found an interesting read on the controversy between LLMNR and mDNS. It seems that LLMNR has "lost" the battle with mDNS, but I guess Windows is still using it.
No idea what's going on with the ARP for 192.168.1.9. Perhaps there was a device at that address in the past.
As to why NET VIEW might be returning immediately with no traffic, it's likely that Windows is just returning cached results. You might consider re-running Wireshark and just capture everything. There could be some important exchanges going on via broadcast that might be filtered out with a "host 192.168.1.30" filter. You can always filter after a capture.
