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

@ww "but also some  servers can be capable of running on a trunk. so it  depends on your design and what you want to connect" I hope the server in question does. It has a 10.10.0.0 IP but has a VIP (Virtual IP) of 10.10.8.0 so I would need both VLANs on one port, right?   @BrandonS " Is it possible the Unix server has no default gateway assigned?  Or one different than you think it is?" EN0 on the server has a 10.10.0.60 with a Gateway of 10.10.0.2. However from what I understand the VIP is only an IP of 10.10.8.60. It being UNIX I'm not sure how it works. I am not the administrator of the UNIX server but I can access it and test things like ping, ftp, traceroute. Pings work fine from it cause it uses 10.10.0.60 but if I try to FTP to a printer, thats how the server sends print jobs, it wont work. I figured out that when I do a traceroute to a printer it uses the 10.10.8.60 IP.  I think my issue boils down to how do I tag the correct VLAN on one port since one port is using both VLANs.  ... View more

@ww Someone said that the ports that connect the switch to the MX and from switch to switch should be set to Trunk then all the others should be set to Access. Does that sound right? ... View more

@ww I cant ping across from my PC on 10.10.0.0 to anything on 10.10.8.0 threw the switch.  I could ping when I have a PC on 10.10.0.0 connected directly to the MX with its port set to Native VLAN 1 and then a PC on 10.10.8.0 connected directly to the MX with its port set to Native VLAN 8.   I've added the VLANs to my Cisco Switches,  I've added the the VLANs to the ports that need access to both subnets on the switch, everything is set to Trunk. I'm not sure what else I'm missing.  ... View more

@Nash @nuo @ww Is there something I did wrong? Something I need to do?  ... View more

I can't get anything on 10.10.8.0 to work once I switch over to the MX ... View more

I'm going to be doing more testing later today. I only have a small window where I can switch the LAN over to the MX and test. I'm going to hook a PC to the same switch as everyone else on 10.10.8.0 and test. My issue is a Unix server that has a IP  of 10.10.0.60 but then also has a virtual IP of 10.10.8.60. The virtual IP has no static gateway set for the VIO.  ... View more

@ww All I have set up are VLANs there are no static routes set. So I feel a little dumb, I didn't notice that when the PC connected it set it to a public network instead of private....so now I can ping both ways. I'll try connecting the PC into the switch next instead of directly connected to the MX. Something else do I need to set the ports on the switch to tagged? I just noticed they are set to untagged. ... View more

@BrandonS so from what I said it should work? Cause I thought it should work too and its not and its driving me crazy. Only firewall rule I've added is some port forwarding to allow a software vendor to a server and they tested that and it works.   ... View more

@BrandonS I've tested from two devices on 10.10.8.0. One is complicated cause its a virtual IP on a UNIX server. I did however connect a single windows computer with IP-10.10.8.50, 255.255.255.0, Gateway-10.10.8.1, and got the same result. The computer was connected directly to the MX and I did change the port to have Native VLAN 8.  ... View more

@timeshimanshu  Lets assume I'm not a Network Engineer, and simple down the network to the MX84, a Cisco SG200 Layer 2 switch, and then my computer and a server. All I want is to allow 10.10.0.0 and 10.10.8.0 to freely communicate with each other.  MX is configured  Subnet-10.10.0.0/24, ID-1, MX IP-10.10.0.2 Then also Subnet-10.10.8.0/24, ID-8, MX IP-10.10.8.1 All ports are set to Trunk VLAN-1 with All VLANs allowed on the MX SG200 Switch Added a VLAN ID 8. All ports are set to Trunk and Untagged Do I set the port on the Switch that goes to the MX to both IDs? Then the port where the server is to both since one is a Virtual IP on 10.10.8.0? I'm also assuming the software vendor of the server can set a ID for them.  ... View more

@timeshimanshu @ww @kYutobi @bayet I know 100% where my issue is now. When the server tries to connect to the printers its going out on the 10.10.8.60 IP. The way I have it set with the static route 10.10.0.0 can talk to 10.10.8.0 but nothing on 10.10.8.0 can talk to 10.10.0.0 I also did a small test with two computers connected directly to the MX. If I set VLANs up with mentioned subnets and set the Native VLAN to 8 on the port where the 10.10.8.0 computer is I could ping from the 10.10.8.0 to the 10.10.0.0 but not the other way around. If I set static routes for 10.10.8.0 I could ping from 10.10.0.0 to 10.10.8.0 but not the other way around. All I need is for 10.10.8.0 and 10.10.0.0 to be able to talk both ways. Is the only way of getting it to work is using VLANs? There are no VLANs now and it works.  ... View more

@timeshimanshu I should probably note the server is running IBM AIX ... View more

@timeshimanshu This is what I did before switching over to the MX # cd /u/jmi  <---location of the printtest file # ftp 10.10.0.74 <----- IP of the printer Connected to 10.10.0.74. 220 ET0021B7ABD56C Lexmark MS810 FTP Server NH63.YS.N639 ready. Name (10.10.0.74:root): 230 User root logged in. ftp> put printtest   <------ printtest file with a simple Hello message 200 PORT command successful. 150 Opening ASCII data connection (10.10.8.60,46526). 226 Transfer complete. 173 bytes sent in 0.2 seconds (0.8446 Kbytes/s) local: printtest remote: printtest ftp> quit 221 Good-bye.   This is after switching over to the MX # cd /u/jmi # ftp 10.10.0.74 <---- Just sat there and never connected ^C# # ping 10.10.0.74 <---- Decided to ping it  PING 10.10.0.74: (10.10.0.74): 56 data bytes 64 bytes from 10.10.0.74: icmp_seq=0 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=1 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=2 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=3 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=4 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=5 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=6 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=7 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=8 ttl=254 time=0 ms 64 bytes from 10.10.0.74: icmp_seq=9 ttl=254 time=0 ms ^C --- 10.10.0.74 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max = 0/0/0 ms # ftp 10.10.0.74 <---- Tried it again and it just sat there   From a command prompt from my computer C:\>ftp 10.10.0.74 Connected to 10.10.0.74. 220 ET0021B7ABD56C Lexmark MS810 FTP Server NH63.YS.N639 ready. 500 OPTS command not understood. User (10.10.0.74:(none)): 230 User default logged in. ftp>   Can you understand my frustration? All I'm doing is moving one cable from the ISP gateway to the new MX but certain things stop working.  ... View more

@timeshimanshu @ww I'm so confused as to whats going on. Before I switched over to the MX I tested opening a console on the server, FTP to a printer, then print a test file. It worked just fine. Once connected to the MX I open a console on the server but was unable to FTP to the same printer. I could however ping the printer from the server just fine. I then opened a command prompt on my computer and could FTP to the printer just fine.   Side note I've noticed the MX doesn't like non Meraki switches to much. I tried setting up a small network environment with a small D-Link smart switch I have and its like they don't want to recognize each other. No lights even come on the port. I even put a static IP on the switch and nothing. I even tried a dumb switch and still nothing.  ... View more

@timeshimanshu The printer, server, and my computer are in 10.10.0.0 but I am able to ping the virtual IP of the server at 10.10.8.60. From my computer I could ping everything just fine.  Physcal IP of server is 10.10.0.60 Virtual IP supposedly splits traffic across the NICs of the server.    ENO - 10.10.0.60, 255.255.255.0, 10.10.0.2 EN1 - 10.10.5.60, 255.255.255.0, 10.10.0.2 EN2 - 10.10.3.60, 255.255.255.0, 10.10.0.2 EN3 - 10.10.7.60, 255.255.255.0, 10.10.0.2 ... View more