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

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

Updated last night and still same issue. ... View more

They are pre configured from RingCentral.  ... View more

I schedualed the update later tonight. Hopefully that will fix the issue.  ... View more

No there is no VLAN set up its just a single single LAN ... View more

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

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

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

@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

@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

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

Check to see if both the IKE and IPec services are running? I had one where the IKE service was not running.  ... View more

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

No, there are 10 branch locations. Is there any documentation on what needs to be add? I couldn't seem to find any. ... View more

@BrandonS "Or- hopefully the VIP is assigned tagged to a sub interface and in that case you would want the port connected to the server to be trunk with VLAN 8 tagged."   If I have it set with VLAN 8 tagged and VLAN 1 untagged you think 10.10.0.80 will still work? Or No VLAN 1 added at all? If so would the 10.10.0.80 still work? ... View more

@nuo Ok I understand now what is going on and why its not working. I did have a PC plugged into the switch with an IP of 10.10.8.40 - The port it was plugged into set to Access with the VLAN set to 8. It worked so that tells me VLANs are working as they should. I was able to get to it and was able to ping other devices on the network. So now its just the UNIX server that I don't know what to do with. I cant set the port to access because it needs to use both VLAN's and setting it to Trunk isn't working.  ... View more

@BrandonS This is what the Admin of the server sent me   The VLAN research I did for AIX highly recommends having VLAN take place in the switches NOT on the RS/6000 NIC cards.   There is not a static gateway for the VIO 10.10.8.60.    Since it is a virtual IP created by combining the 4 NIC that have 10.10.0.2 as their gateway, it has no entry.   Change / Show a Virtual IP Address Interface   Type or select values in entry fields. Press Enter AFTER making all desired changes.                                                           [Entry Fields]   Network Interface Name                                                               vi0   INTERNET ADDRESS (dotted decimal)                                    [10.10.8.60]   Network MASK (hexadecimal or dotted decimal)         [255.255.255.0]   Current STATE                                                                               up                     +   Network Interface(s) using this VIPA           Interface Name(s)                                                                  [en0,en1,en2,en3]       +           ADD/REMOVE Interface(s)                                                  ADD                    +   IBM RS/6000 IP information: It has a 4-port NIC card.   NIC:                            EN0 Hostname:                 cashwell IP:                               10.10.0.60 Newtwork Mask:       255.255.255.0 G/W:                           10.10.0.2   NIC:                            EN1 Hostname:                 cashwell IP:                               10.10.5.60 Newtwork Mask:       255.255.255.0 G/W:                           10.10.0.2   NIC:                            EN2 Hostname:                 cashwell IP:                               10.10.3.60 Newtwork Mask:       255.255.255.0 G/W:                           10.10.0.2   NIC:                            EN3 Hostname:                 cashwell IP:                               10.10.7.60 Newtwork Mask:       255.255.255.0 G/W:                           10.10.0.2     # named virtual ips 10.10.8.60      vipa60 10.10.8.10      vipa10 10.10.8.11      vipa11 10.10.8.12      vipa12 10.10.8.13      vipa13 ... View more