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!
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 wrote:
Well, there's always Wireshark. At least, that's what I would do to see what's going on the wire.
I've never trusted ReadyShare. Too many reports of corrupted or flaky shares, and performance is basically terrible. Use a real NAS, like Synology or QNAP. Leave the router to do what it does best: route.
Yes, I was thinking of firing Wireshark up. Wasn't too sure what to look for? Since my PC is on a fixed 192.168.1.30 IP Address I guess I could filter for anything going in or out from that address.
Oh, I forgot to mention, it takes a good amount of time when I enter NET VIEW and get back the 1231 error... all other times, even the 53 error come back immediately. All the more reason I think the router isn't responding or possibly W10 TCP/IP is retry and/or timing out and throwing the error. Possible that it got an error but didn't have a message for it so threw the catch-all error?
My USB drive is 2.0 and connected to 2.0 port and has worked 'forever', although in the beginning I did have problems with bad DLNA catalog when I first got the router years ago. Worked with NG Support and eventually got it fixed. Everything worked fine until recently. Of course there could be a possibility of some disk corruption too I guess causing problems? When I get a chance I'll take it to the PC to be sure. I have already used NET USE to assign it a drive letter and ran CHKDSK on it and it was clean???
IrvSp wrote:
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?
USB drives are a constant source of frustration.
In particular, things that work with USB2 refuse to play ball when plugged into USB3.
No one has ever got to the bottom of that. But I don't think anyone has put as much effort into debugging as you have.
Given the frustrations with the latest firmware for the R7000 and wifi, you have good reason to point a finger in that direction. It is just the logic that fails me. But who said IT was a logical domain?
Well the PC's were sitting still for hours.
The NET VIEW now fails with the 1231 error again and I'm having FireFox 'hang' with the spinning dots for about a minute when I try to access the Router? All this after disabling and reconnecting the USB drive. I'll probably need to reboot the router soon.
Something is clearly wrong, but I can't get a finger on it.
Another noticeable problem. The WAN IP Address is get RENEWED about every 1 1/2 hours. Lease time is around 2 hours according to the status of the connection. I've been round and round with my ISP on this and they claim it isn't so. I'm not wondering if the lastes V1.0.9.xx flashes have this set internally? Many routers do allow one to set the lease time, but not the R7000? Can you check your lease times? Reason being that seems to be the time that I lose NET VIEW ability?
