Well, to answer your question, I haven't tried removing the switch out of the equation just yet, I just cant to see how the switch is doing anything that could be causing this issue. Not everyone has the same equipment in thier house but I'm sure, that if you follow this proceedure you should be able to point your self in the direction of the offending device. I have had problem free operation since - and its been over 2 months. I'm still baffled as to why this was happening but in any case, after playing around with the network setting on the NVR, I basically had to turn off the internal DHCP, have the IP address for the cameras assigned manually, aswell as reserved an IP address for the NVR its self on my google nest and then also assigned that IP manually on the NVR. That basically pointed me in only one direction. The same was happening Visa Versa, a couple of my IP cameras where being issued IP address by my Google Nest WIfi.īasically once I was able to discover the device (in my case one of the IP cameras) and then use its ip to attain its MAC address, then using that to discover the manufacturer (in my case the offender was SWANN SECURITY). In my particular instance what was occuring was my SWANN Securitry NVR, which is meant to have a closed off private DHCP for my IP Security Cameras was occasionally issuing IP address to some of my devices. Follow its instructions to the letter, by that I mean install the Rogue DHCP server detection application, use it when the problem is occuring, discover the IP address, use that ip address to discover the MAC address and then use that MAC address to discover the Manufacturer of that device on I'll try to give everyone the manner in which I targetted the issue and hopefully this will assist some of you. As it turns out it was indeed a rogue dhcp server, blows my mind really. Ok, so for my particular sitation I have discovered the problem. PS: Assigning every single device in my network with a static IP address is not a solution, and VERY ANNOYING. So why is the Nest Router doing this from time to time? Like i said, this issue is random, and intermittant, which ever device it decides it wont issue an ip address to, is a device that would have been previously succesfully connnected to the network with flewless internet functionallity. TP-link ( in bridge mode) -> Nest Wifi Router -> Netgear Switch (dhcp disabled recieves ip from nest router) -> wired devices (PC, Printer, Laptops, NVR etc) All other devices in my house are wireless and theres about 20 or more, they range from TVs, phones, tablets, toys, xbox's etc. TP-Link Archer VR600v, Netgear Switch GS724Tv4, Nest Wifi x 3 ( 1xrouter 2xaps ) and are connected in the following order bellow Network Devices I have in my network bellow I have troubleshooted and done everything i possibly can to resolve this.įactory resets, restarts, restarts and connecting devices in sequence you name it, I even investigated an date a time issue that it could have possibly been. Having to do this is very frustrating all the time. The only thing that resolves this issue for me imediately is to assign a static IP address with the correct prefix 192.168.86._ and the correct gateway 192.168.86.1 on the DEVICE, and suprise suprise everything instantly connects to the internet. Its has happend to iPads, Samsung tablets, samsung phones, 2 different TCL google TVs etc ( having said that, The Xbox, PCs and Sony TV haven't had the issue yet. Having said that no previously connected device seems to be immune from the random issue. There are periods where there are no issues though, sometimes a few weeks can pass trouble free. The device is connected to the wifi but with no internet, soon as you go into the settings on the said device the issue is obvious. Nest Wifi intermintantly picks a device at random and wont issue the correct ip address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |