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!
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?
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?
IrvSp wrote:
....I'm having FireFox 'hang' with the spinning dots for about a minute when I try to access the Router?
Tried another browser?
I doubt very much if this is at all related to what is going on at your end, but today I have seen the same symptoms.
The web interface for my R7800 router also hangs in Firefox. Other browsers let me in.
Working FINE now? Both Firefox and IE get in OK?
BTW, under the ADVANCED TAB, on the INTERNET PORT select CONNECTION STATUS. What do you see for the LEASE? I see this:
| Lease Obtained | 0 days,1 Hours,34 Minutes |
| Lease Expires | 0 days,1 Hours,4 Minutes |
This is causing the router to be doing a DHCP request and TIME SYNC about every 1 and 1/2 hours.... Log has this:
[Time synchronized with NTP server] Sunday, Dec 31,2017 19:02:16
[Internet connected] IP address: 67.8.x.x, Sunday, Dec 31,2017 19:02:16
[Time synchronized with NTP server] Sunday, Dec 31,2017 17:32:06
[Internet connected] IP address: 67.8.x.x, Sunday, Dec 31,2017 17:32:06
[Time synchronized with NTP server] Sunday, Dec 31,2017 16:10:09
[Internet connected] IP address: 67.8.x.x, Sunday, Dec 31,2017 16:10:09
Never the same exact set period either, but around 1 and 1/2 hours. Most routers have a setting for getting a new lease. The R7000 does not. In another forum for my ISP someone else has hit this too, I've asked what router but didn't get an answer yet. Wondering is the firmware is causing it? Bad lease time in the code?
