Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About CashG
Community Record
58
Posts
10
Kudos
1
Solution
Badges
Jan 15 2024
9:30 AM
I tried the MX64 and same issue. Directly connecting is the same thing. I would have to time a packet capture. When iCT220 is plugged in you can see an event log of it trying to give it a DCHP lease with all the correct IP, subnet, and DNS but its like the iCT220 won't accept it. Like I said the iCT220 is a very old model and even the CC company said they wont try to do much with it since its so old. I even tried to set static info in the MX using the iCT220 MAC.
... View more
Jan 15 2024
7:43 AM
No this is not on Wifi. Like I stated it seems to be older out of date devices. With the ATA192 I had no issues with DHCP on the MX64 but would not get DHCP on the MX84 until I did a firmare upgrade on the ATA192 and then it worked fine. I've tried 3 differnt iCT220 on the MX84 and none would get DHCP but a newer model (I don't remember the exact model) would get DHCP just fine. I'm thinking about taking it to a location with a MX64 and trying it.
... View more
Jan 15 2024
7:28 AM
Our main location uses a MX84 and our branch locations use MX64. I've had some issues with older devices on the MX84 getting DHCP. I'm just trying to figure out why and what I can do to maybe get them to work. So on the MX84 I don't have any issues with computers or cameras or printers getting DHCP. However the first time I had an issue is with a Cisco ATA192. It would not get DHCP, but if I went to another location with the MX64 it would. I then figured out if I manually update the firmware of the ATA192 it would then work properly. My issue now is I have a old credit card machine, ingenico iCT220, that will not get DHCP. I've had a newer model work fine. My guess is that if I take it to a location with the MX64 it will work. There is an event log where it attempts to get a DHCP lease but its like it just doesnt stick. Also I can not set a static IP on this machine because it is owned by the CC company. I'm just trying to understand why this is.
... View more
May 23 2023
6:58 AM
I finally found a download for the ATA firmware and was able to install it and now it works.
... View more
May 22 2023
10:43 AM
I schedualed the update later tonight. Hopefully that will fix the issue.
... View more
May 19 2023
1:37 PM
None of this makes sense to me. I put a static IP on the ATA again so it shows up in the clients list on Meraki. If I go to the event log for it I see lots of DHCP DHCP problem extra: no_offers_received, vap: 0, vlan: 0 Then I tried doing a packet capture on it for 60 seconds and there was not a single thing in it. Its like its not trying to do anything. I've done it twice now even when rebooting it.
... View more
May 19 2023
12:19 PM
I just thought of something. The ATA192 does run DCHP on it for computers connected to it. There is a Network and Ethernet port. Do you think the MX84 is blocking it because it is trying to run DHCP on it? Although I dont know if it only does it for devices plugged into the Ethernet side and wouldn't affect it being plugged into the Network side.
... View more
May 19 2023
12:10 PM
Yes. Everything is configured to automatically connect. I don't understand why the Cisco CP8851 will automatically obtain an IP from the MX84 but the Cisco ATA192 will not. I've loggen into the ATA192 and it is set to obtain an IP from DHCP. Also doesn't make sense why even putting a Static IP in it will not work.
... View more
May 19 2023
11:42 AM
Don't know if someone can help me with this or not. At our main site we use a MX84 and our other locations use the MX64 and DHCP is turned on all locations. We are switching over our phones to RingCentral VoIP phones. We are using a Cisco ATA192 at some locations. Locations with the MX64 work fine with the ATA192 and they automatically aquire a IP and connect fine. For some reason the ATA192 here where the MX84 is they will not aquire an IP. I've even tried putting in a static IP and it still won't connect. DHCP is working because if I plug a new Cisco CP8851 phone in it will get an IP and connect. Any idea why just the ATA192 won't work? Also I've tried 6 of them and none of them will connect and took one of them to another location where the MX64 is and it worked there.
... View more
Feb 14 2022
6:52 AM
2 Kudos
Contacted Cisco support and they said the VPN Registry is loaded pretty heavy and they will change the registry.
... View more
Feb 11 2022
7:37 AM
This is the site-to-site VPN and only this one location is having an issue. There are 10 other locations configured the same way to connect back to a Hub.
... View more
Feb 11 2022
7:20 AM
I have one location that is experiencing a lot of hesitation in the system. Meaning they enter in some information and they have to wait a minute or two to get information back, but this only happens on and off. It will work fine for a while then act slow then work fine again and so on. They have a fiber connection there and the ISP says everything checks out on their end. When I look at their MX64 they are barely using any bandwidth and nothing looks wrong except every so often the VPN Registry will say Partially connected sometimes then go back to Connected. Any help in trying to determine the issue is appreciated.
... View more
Feb 8 2022
1:34 PM
4 Kudos
Ok, that fixed one Client now I just have to make sure everyone else is up to date.
... View more
Feb 8 2022
12:34 PM
I just now noticed another post about a Windows update. I'll try that. 😁
... View more
Feb 8 2022
12:31 PM
So our Client VPN has worked fine for a long time but now no one can connect. Nothing has changed so I don't understand what is going on. Client side they get the The L2TP Connection Attempt Failed Because the Security Layer Encountered a Processing Error. I've checked and the IKE and AuthIP services is running. I tried to do a packet capture but not sure what I'm looking for. I do see one for the Clients IP and I see the ISAKMP Phase 1 where it says Next payload: Security Association (1) but I don't see anything about a Key Exchange.
... View more
Apr 9 2020
9:03 AM
@BrechtSchamp No there is only one. We were trying it out to see how it works. All the Windows Laptops work. I've tested here on a hotspot connection to rule out something with the clients ISP. Also logged into the Chromebook with my profile and still doesn't work.
... View more
Apr 9 2020
7:57 AM
@rwiesmann Yes, most of that has to do with Windows. I'm having an issue with Chrome OS and I don't have much experience with Chrome OS. I can use all the same settings and credentials on a Windows 10 computer and works fine. First day I was testing I set it up and worked fine and then it wanted to do a update. After the update it wouldn't work but I told it to forget the VPN and I recreated it and it worked again. As far as I know there hasn't been another update and I've tried redoing the VPN.
... View more
Apr 9 2020
7:28 AM
Has anyone had experience using Client VPN and Chrome books? I set a Chrome book up the other day and everything was working fine. The client said she disconnected the VPN when she went to lunch but could never get it to reconnect after. I even tried forgetting the VPN connection and recreating it and still nothing. I can however go to a Win 10 laptop and use all the same settings and it works fine. I don't know what this means but in the logs I see "invalid DH group 19" and "invalid transform-id=20 in ESP".
... View more
Oct 23 2019
6:33 AM
1 Kudo
Ok so I looked at the Zosi Smart app and its similar to how our Amcrest cameras are. When you go to Add Device on the app and then select IP Camera you then select Camera C199 (thats your camera model). It wants to scan a QR code. From what I can tell its on the bottom of the Camera. Our Amcrest ones you can look under the Network settings and find the QR but I don't know if your camera has something like that. As long as the camera can connect to the Internet and register itself with the Zosi cloud services you should be able to view it anywhere without setting up port forwarding. The camera probably registers itself using its Serial Number and then your app needs the QR code that contains the camera Serial Number to connect to it. When you are looking at the settings are you using the app on your phone? Have you tried going to a PC on the same LAN and typing in the IP in a browser? If that doesn't work you may need to use a different IP camera viewing app that allows you to view a camera by IP. Then I would try doing a 1:Many NAT Your Public IP - TCP - (Pick a public port) 1234 - LAN IP 192.168.128.73 - Local Port 37777 (37777 is a typical TCP camera video streaming port) - Allowed IPs Any Your Public IP - UDP - (Pick a public port) 1235 - LAN IP 192.168.128.73 - Local Port 37778 (37778 is a typical UDP camera data streaming port) - Allowed IPs Any
... View more
Oct 22 2019
1:32 PM
Check to see if both the IKE and IPec services are running? I had one where the IKE service was not running.
... View more
Oct 22 2019
1:22 PM
Is the camera connected to a DVR? From what I can find it talks about the DVR being connected to a Cloud service. We have Amcrest cameras that as long as they are connected to their cloud service we don't have to do any port forwarding.
... View more
Aug 29 2019
8:27 AM
Right now I have 2 MX84's at one location. The main one is connected to a fiber connection and the second is a warm spare connected to a cable connection. Each one is plugged into WAN1 of the MX. I'm guessing load balancing won't work like this? Do I need to connect the cable connection into WAN2 of the main MX also?
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 1574 | May 23 2023 6:58 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 4 | 795 | |
| 2 | 1084 | |
| 1 | 7643 | |
| 1 | 12027 | |
| 1 | 12247 |
© 2024 Cisco Systems, Inc.
