So the accepted solution was not the solution. 😅 ... View more

I'm currently facing a challenge with this. A customer needs to put Mx65 on it's network for a Demo but the MX is not connecting because there is a firewall in place that's blocking it. How can we give the MX a STATIC IP that will be allowed on the firewall??? ... View more

A while back I had a similar speed problem problem with clients on on business SSIDs assigned via group policy.  Guest SSIDs worked just fine.  Turned out to be something in the settings that were being used.  It had been on my to do list for a while to update the security protocols, so I didn't spend time figuring out what the issue was, just moved on to the next thing.  In my case I needed to migrate to something new, so did a new SSID making sure everything is set to WPA2 only, AES (no TKIP), once that is what the laptops used, the speed increased immediately.   ... View more

Correct, @getnyce32 - Put the MX in place, add routes to it so it knows how to get to the MPLS Gateway and remote subnets, then point your desktop to the MX as your default gateway.  Hopefully you also have a 2nd Internet Line for the MX  all local traffic to the internet and / or VPN failvoer if the MPLS goes down.   The routes you put in have options to check up/down status of another device, and if the remote device is down fail over to the VPN.   The documents that @PhilipDAth linked have details on that setup.   I used this for quite a while, and it worked great once I got it setup.       ... View more

You could treat it kind of like a router using internal interfaces.  Plug the MPLS into LAN2, then LAN 3 is uplink to the rest of that local branch, then setup routes and IPs associated with that LAN2 port in the Addressing and VLANs page.  This process is pretty manual for sure.  You could then plug the WAN1 port into internet service and let the MX still act as your internet filter and all that good stuff.     IF you have MXs at both / all sides, you could enable their site to site VPN, over the MPLS circuits or over the internet and it can handle routes for you.    I'll say for my experience, we were using an MPLS, but really didn't have a need anything but basic connectivity between sites.  After some testing, we ditched MPLS, and each site has a low speed (10-20 mbit) fiber we use as Primary VPN, and a 2nd Coax internet 100 mbit connection we use as Primary internet and fail over VPN as needed.  It was a big cost savings for us!   That's a pretty simplistic sum-up, but maybe that will help set you on a good path. ... View more

@AnythingHostedwrote: @PhilipDAthwrote: I agree with @Uberseehandel - best practice would be to use something like Office 365 and forget the issue, And then make sure you've whitelisted all the office 365 addresses if you have enabled Spam and Malware blocking on the MX! 🙂 On my list of things to do later this year, after getting to grips with the API, is updating the whitelist from the RSS feed automatically. There are too many entries to do this manually every month just for MS, let alone the other big services sites. When I have mentioned this to some (quite prominent) dev-ops types, they have looked blank. It seems an obvious one to me. For giggles, I wonder if Alexa .  . .  ... View more