I disabled one of the APs that is in the basement. I first moved everything that was on that AP to the other AP in the basement. Everything worked perfectly for about 4 days, then the old symptom returned.
Regards, Jim
Old Problem Unsolved
Re: Old Problem Unsolved
Idea, as I sad before, need to double check your Ip, from your main computer. "One able to always connect" run ipconfig and note the IP of that computer. Then when you move to your laptop and you see it won't connect, then run ipconfig on that computer and see if the 2 IPs are in the same range. My guess is there is an issue with the way your AP is handling your IP handouts.
Be Safe.
Re: Old Problem Unsolved
Hi Revo,
My router (Edge Router X) has no wifi, it is ethernet only. I have it set up to have the same IP for each device. So, every device has the same IP address when it goes online. The range for the entire network is 192.168.1.xxx. xxx is 99 to 140. I don't see how IP addresses can get mixed up, but I will follow your suggestion next time I have the failure.
Best regards, Jim
My router (Edge Router X) has no wifi, it is ethernet only. I have it set up to have the same IP for each device. So, every device has the same IP address when it goes online. The range for the entire network is 192.168.1.xxx. xxx is 99 to 140. I don't see how IP addresses can get mixed up, but I will follow your suggestion next time I have the failure.
Best regards, Jim
Re: Old Problem Unsolved
Another failure! And interesting details. I have an older laptop in my office at the front of the house. And I have an AP in that office. I use my current laptop near the rear of my house. And there is another AP in the basement close to the laptop. Just now, the current laptop had the failure occur. I rushed to the office and fired up the older laptop. Everything is normal! No loss of camera views on ASP!
So, the problem seems to be the AP in the basement. Any suggestions about what to do next?
Best regards, Jim
So, the problem seems to be the AP in the basement. Any suggestions about what to do next?
Best regards, Jim
Re: Old Problem Unsolved
Have any Tannerite LOL Just kidding..
Honestly it is hard to know what is wrong.. I know there are some systems out there that are setup not to share local network connection only give access to the internet. I would have to guess that you might have your AP setup to give access to your internet but don't share local IP.. If you are able to access each of the AP by going to the IP address for the AP there might be something within each device that with allow or restrict local access.. In one of my older systems this was called AP Isolation and in the GUI of the devices I could enable or disable this feature. If enabled it would make it so when you connect to the AP lets say in the basement you would be able to access the internet still but nothing else on the local network.
Some other things that it could have been. IP address conflict, Firewall settings, Network configuration issue, Like lets say you have your network settings in your laptop setup with the wrong settings, Could be a Profile issue, if your windows network profile was setup for Public and not Private that might restrict your local network access.. Last thing I can think of. Maybe you have setup your system with Vlan and when you connect to the AP it is connected to a Vlan that don't share the local access
Without knowing your system it is really hard to say why something won't work right. These all the things I can think of right now. Something may come up later but there is loads of things to look at for now.. Sorry couldn't be more help.
Honestly it is hard to know what is wrong.. I know there are some systems out there that are setup not to share local network connection only give access to the internet. I would have to guess that you might have your AP setup to give access to your internet but don't share local IP.. If you are able to access each of the AP by going to the IP address for the AP there might be something within each device that with allow or restrict local access.. In one of my older systems this was called AP Isolation and in the GUI of the devices I could enable or disable this feature. If enabled it would make it so when you connect to the AP lets say in the basement you would be able to access the internet still but nothing else on the local network.
Some other things that it could have been. IP address conflict, Firewall settings, Network configuration issue, Like lets say you have your network settings in your laptop setup with the wrong settings, Could be a Profile issue, if your windows network profile was setup for Public and not Private that might restrict your local network access.. Last thing I can think of. Maybe you have setup your system with Vlan and when you connect to the AP it is connected to a Vlan that don't share the local access
Without knowing your system it is really hard to say why something won't work right. These all the things I can think of right now. Something may come up later but there is loads of things to look at for now.. Sorry couldn't be more help.
Be Safe.
Re: Old Problem Unsolved
Thanks Revo,
Another tidbit, I just took my current laptop into the office, fired it up and yes, all cameras visible! Took it back to rear house location, and no cameras visible. Computer IP address correct.
Best regards, Jim
Another tidbit, I just took my current laptop into the office, fired it up and yes, all cameras visible! Took it back to rear house location, and no cameras visible. Computer IP address correct.
Best regards, Jim
Re: Old Problem Unsolved
OK, So with that said then there is another one of the few things that I listed as the issue it might be.. Not always would the restriction be caused by IP range change it could be that the AP it self has a setting that is keeping anything connected to it Isolated..
So lets say that your office Ip as 10.0.0.123, and when you went to the back of the house and turned on the laptop it was able to get 10.0.0.143 a few things could be setup in the main router or the AP and again without knowing what models of router or AP you are using it would be hard to know where to point for a look.. It could be in the system it is setup that anything that connects to the AP no matter the IP is restricted from accessing LOCAL LAN..
So lets say that your office Ip as 10.0.0.123, and when you went to the back of the house and turned on the laptop it was able to get 10.0.0.143 a few things could be setup in the main router or the AP and again without knowing what models of router or AP you are using it would be hard to know where to point for a look.. It could be in the system it is setup that anything that connects to the AP no matter the IP is restricted from accessing LOCAL LAN..
Be Safe.
Re: Old Problem Unsolved
Access points can be a nightmare on a good day! Multiple APs or mesh can be even worse.., obviously.
The first thing I would do is get your phone off your local network (at home) and see if you connect to everything via your service provider and ASP. My guess is you will via P2P, which clearly indicates a problem with your LAN/Wi-Fi as Revo has elaborated upon already.
Time to review everything beginning at the demarc point of your service provider to the last AP and everything in between. Start with the basic LAN configuration/architecture not even including the camera network. Check everything very closely for port and/or protocol restrictions in general. You should have a fairly clean setup with a router/DHCP server handling your basic devices with fundamental safeguards in place..., essentially no UPnP and no other fancy firewall stuff or utility security boxes in the way..., at least for now.
Carefully review your dhcp configuration and method of address assignments. Next carefully review your Wi-Fi setup for conformity to normal practices and coherence in the network scheme. If it's too complicated trying to be fancy, simplify it.
Ensure the APs are in the correct mode for their purposes..., after doing a signal analysis to determine if they're even necessary, especially multiples that are possibly stepping on each other. The design of the Wi-Fi segment of the network needs to make network sense, not just provide lots of signal everywhere.
How about some details about the actual network set up. Ideally, (and technically), APs are wired extensions of the network for providing Wi-Fi to otherwise difficult to cover areas. They are typically simple extensions of the existing Wi-Fi architecture using the same SSIDs, frequencies and IP address structure as the main Wi-Fi source, just extended by ethernet to the AP locations before being re-broadcast.
A mesh Wi-Fi system is a different animal and most would steer clear of mesh for IP camera networks precisely for the reasons you are here.
Access Point is also a rather loosely used term and tossed around freely to describe anything that spits out or repeats a wi-fi signal given very little specific detail of the technology involved. All access points are not created equal.
We could help you much more effectively by knowing your network topology.
Bottom line, the APs should be doing nothing but extending wired connections from your central switch/router/WiFi source to areas requiring adequate coverage. They should have a static IP address. They should have zero affect on the IP address aspect of any devices using them. Zero. They should essentially be invisible to any devices behind them as a static point of Wi-Fi access to the network and nothing else..., ideally just to the camera network only.
If the whole thing is a mesh setup with APs relying on one another for connectivity and reliability and anything in the room can hop on, it becomes a whole other bag o' snakes requiring much more detailed consideration and a greater understanding of how Wi-Fi works in such a situation.
If it happens to be a combination of both with (heaven forbid) wi-fi hops among multiple APs, all bets are off and consideration should strongly be given to starting all over from scratch in an attempt to establish as much ethernet connectivity as possible to the locations requiring APs.
Many believe Wi-Fi is the devil when it comes to IP camera installations..., mainly because they simply aren't experienced enough to know any better. They threw a bunch of access points at a home IP camera network that ended up working like shit and that was that for them. Hard to un-ring the bell once people have that experience ingrained in their heads.
I'll take wire any day over Wi-Fi, but also know that Wi-Fi can be as reliable as the electricity that's powering it and do some magical things when properly understood and implemented.
But it's not magic without a magician. Ya gotta know how it works to keep from actually sawing the lady in half for real[/i
Go over your layout again from end to end. You may find a simple explanation that gets it all straightened out. Otherwise, ask more questions.
Good luck!
The first thing I would do is get your phone off your local network (at home) and see if you connect to everything via your service provider and ASP. My guess is you will via P2P, which clearly indicates a problem with your LAN/Wi-Fi as Revo has elaborated upon already.
Time to review everything beginning at the demarc point of your service provider to the last AP and everything in between. Start with the basic LAN configuration/architecture not even including the camera network. Check everything very closely for port and/or protocol restrictions in general. You should have a fairly clean setup with a router/DHCP server handling your basic devices with fundamental safeguards in place..., essentially no UPnP and no other fancy firewall stuff or utility security boxes in the way..., at least for now.
Carefully review your dhcp configuration and method of address assignments. Next carefully review your Wi-Fi setup for conformity to normal practices and coherence in the network scheme. If it's too complicated trying to be fancy, simplify it.
Ensure the APs are in the correct mode for their purposes..., after doing a signal analysis to determine if they're even necessary, especially multiples that are possibly stepping on each other. The design of the Wi-Fi segment of the network needs to make network sense, not just provide lots of signal everywhere.
How about some details about the actual network set up. Ideally, (and technically), APs are wired extensions of the network for providing Wi-Fi to otherwise difficult to cover areas. They are typically simple extensions of the existing Wi-Fi architecture using the same SSIDs, frequencies and IP address structure as the main Wi-Fi source, just extended by ethernet to the AP locations before being re-broadcast.
A mesh Wi-Fi system is a different animal and most would steer clear of mesh for IP camera networks precisely for the reasons you are here.
Access Point is also a rather loosely used term and tossed around freely to describe anything that spits out or repeats a wi-fi signal given very little specific detail of the technology involved. All access points are not created equal.
We could help you much more effectively by knowing your network topology.
Bottom line, the APs should be doing nothing but extending wired connections from your central switch/router/WiFi source to areas requiring adequate coverage. They should have a static IP address. They should have zero affect on the IP address aspect of any devices using them. Zero. They should essentially be invisible to any devices behind them as a static point of Wi-Fi access to the network and nothing else..., ideally just to the camera network only.
If the whole thing is a mesh setup with APs relying on one another for connectivity and reliability and anything in the room can hop on, it becomes a whole other bag o' snakes requiring much more detailed consideration and a greater understanding of how Wi-Fi works in such a situation.
If it happens to be a combination of both with (heaven forbid) wi-fi hops among multiple APs, all bets are off and consideration should strongly be given to starting all over from scratch in an attempt to establish as much ethernet connectivity as possible to the locations requiring APs.
Many believe Wi-Fi is the devil when it comes to IP camera installations..., mainly because they simply aren't experienced enough to know any better. They threw a bunch of access points at a home IP camera network that ended up working like shit and that was that for them. Hard to un-ring the bell once people have that experience ingrained in their heads.
I'll take wire any day over Wi-Fi, but also know that Wi-Fi can be as reliable as the electricity that's powering it and do some magical things when properly understood and implemented.
But it's not magic without a magician. Ya gotta know how it works to keep from actually sawing the lady in half for real[/i
Go over your layout again from end to end. You may find a simple explanation that gets it all straightened out. Otherwise, ask more questions.
Good luck!
Re: Old Problem Unsolved
Are you able to ping the NVR from your current laptop when it's at the rear of the house?
Re: Old Problem Unsolved
Yes, I can ping the NVR. I have reviewed the network multiple times. I can't find anything that looks weird. I have found that when I get the failure, I can just change the AP and the failure goes away. I don't have run back and forth between front of house to back of house, or switch laptops.
As far as the network details, pretty simple. One router (Edge router, wired only) connected to the Cable Modem. All devices on the network are set up with static IP by the router. Four Netgear switches. three APs (One Dlink and two Netgear) and 22 total devices.
I think I will give up on chasing the problem and just switch APs as necessary.
Thanks for all of the help'
Best regards, Jim
As far as the network details, pretty simple. One router (Edge router, wired only) connected to the Cable Modem. All devices on the network are set up with static IP by the router. Four Netgear switches. three APs (One Dlink and two Netgear) and 22 total devices.
I think I will give up on chasing the problem and just switch APs as necessary.
Thanks for all of the help'
Best regards, Jim