@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

@ww I agree but for some reason the server is not sending the print job directly to the printer but to the gateway for it to direct it back to the printer. Don't ask me why but thats what I get from the software vendor of the server.  ... View more

Shouldn't the MX be acting as the gateway for the LAN? Am I confused as to what the MX can and can't do?   what is the printserver ip and gateway? 10.10.0.60 and 10.10.0.2 what is the printer ip and gateway? 10.10.0.75 and 10.10.0.2   in the Static route the gateway ip is misconfigured. please change it where are these subnet configured? Those subnets only exist on the software server. They are statically assigned. I put those subnets in the MX just so they can talk to each other.  ... View more

The other static routes are only there because the server in question has them (don't know why the software vendor for the server has it set like that) The server has 4 physical NICs and then the 10.10.8.0 is for virtual IPs on the server.  ... View more

The Fortigate is being removed when switching over to the MX. We have a MPLS with our current ISP (the Fortigate belongs to them) and we are trying to switch to a new ISP using the Meraki SD-WAN ... View more

All computers, Servers, Printers are configured with an IP 10.10.0.X Subnet 255.255.255.0 and Gateway 10.10.0.2. The MX should be the only Gateway and I don't know what else to configure on it other then what I have done.  The MX does have DHCP disabled as there is a DHCP server on the LAN. ... View more

*Update I took the VLANs out. There really isn't a reason to keep them separated, so I added some static routes in the MX and was able to ping all the IPs. However the system couldn't print for some odd reason. One problem down another one to go.  ... View more

I checked with the Software Vendor and there is no VLAN ID for the IPs.    I did try after hours yesterday and I was unable to ping the virtual IP. I'm not sure if this had to do with the MX saying there is an IP conflict with the 10.10.8.60 IP.   I did run a small test on the MX with two computers. One on port 5 with the Native VLAN 18 with IP 10.10.8.50 and another computer connected to port 9 with the Native VLAN 1 with IP 10.10.0.136 The 8.50 could ping the 0.136 but the 0.136 could not ping the 8.50   So far what I'm getting is I have to use VLAN IDs for this to work? The software vendor said they have never had to assign a VLAN ID before.  ... View more

Here is a Diagram  https://cloud.smartdraw.com/share.aspx/?pubDocShare=BC4FAD3533C79CC27EABDD933FEA809C597 ... View more