Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About rrehart01
rrehart01
Here to help
Member since Nov 13, 2018
Nov 28 2018
Community Record
14
Posts
0
Kudos
1
Solution
Badges
Nov 27 2018
4:57 PM
Is there a way to automatically have the Client VPN turn on when a mobile device (cell phone, laptop, etc.) leaves a geofencing area? I can't find any way to do so.
... View more
Labels:
- Labels:
-
Other
Nov 26 2018
8:19 AM
This may be a silly question, but I just setup a MR 33 AP for the first time a few weeks back. When I look at the 'clients' list, I see a bunch of invalid/Ghost MAC addresses. Can anyone tell me what these are? I don't seem to be able to get rid of them/block them. Device type comes up as either EQUIP'TRANS or Barracuda Networks. I do have a MX firewall and MS Switch at the site. Thanks.
... View more
Nov 16 2018
11:18 AM
Figured that one out. Now it says the port is open to the "ECweb configuration service", but still not able to access the camera
... View more
Nov 16 2018
10:59 AM
Additional information: I just did a port scan from outside the network to that port (2263) and got back a "closed" as opposed to a "Blocked". Any idea what that means?
... View more
Nov 16 2018
10:09 AM
Ok. I'll try to reboot after hours. Yes, I have verified the rules are being applied to the camera on the device page. Thanks.
... View more
Nov 16 2018
9:22 AM
Ok - I'm stumpped. I have a camera inside my network that is using dynamic dns (no-ip) so it can be accessed from the internet - specifically on port 2263 (TCP/UDP). My network looks like this: Internet router --> MX64 -->core Switch -->Access switch-->Camera. The camera is accessible from inside the LAN by IP:2263, so I know the LAN is not an issue. Forwarding rules look like this (the other forwarding rules work just fine): When I try to ping the camera from external of the network via DNS, the packets stop after the internet router (I see the attempt to connect to the LAN). so the firewall has to be the issue. I only have one IP at this location (DSL), so 1:1 NAT is not an option. Any help would be greatly appreciated.
... View more
Nov 16 2018
9:07 AM
After going through all possible troubleshooting, I gave up and factory reset the AP. Miracle of miracles - IT WORKED! All green now. Some mysteries will never be solved...
... View more
Nov 15 2018
11:59 AM
Bounced the port. Still the same. BUT! I think I see the problem after doing a packet capture. I think the problem's at the router. Since that's not a Meraki, I'll work with the site to bounce it. Thanks for the help
... View more
Nov 15 2018
11:38 AM
Same result. "This device is using a DHCP IP address from VLAN 0 instead of using configured VLAN 1." Although, now the LAN IP says "192.168.1.6 (statically assigned)" vs. "192.168.1.6 (via DHCP)"
... View more
Nov 15 2018
11:03 AM
On the AP when it's configured to use DHCP (I have a reservation for that in my router)
... View more
Nov 15 2018
9:23 AM
"This device is using a DHCP IP address from VLAN 0 instead of using configured VLAN 1" When I try to statically address the AP with the exact same address, I get "Bad IP assignment configuration", and it still shows "(via DHCP)" on the console
... View more
Nov 13 2018
7:53 AM
I am having this same problem. I have my MR33 connected to a MS120 port configured in trunk mode with native VLAN1. The AP is up and working, and clients can connect to it normally. How do I clear the error?
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 4395 | Nov 16 2018 11:24 AM |
© 2024 Cisco Systems, Inc.
