we have just setup our wifi to use RADIUS auth with 802.1x - this all works. If we are plugged in via ethernet we can resolve computer names or devices on our network without using the FQDN. for example if we RDP to SERVER01 it wont work we need to use SERVER01.test.com   We are replacing an old legacy EOL network using a cisco WLC and old aironet 17 series devices. On that network we dont need to use FQDN either so we are thinking there is something we have missed or a protocol we need to enable. Can anyone assist? ... View more

I am in the process of replacing our entire core network with brand new Meraki Equipment. Before I can do the rest of the network I need to replace the router so we can use our new fibre connection we have and turn the old copper WAN one off. Right now we use a very dated checkpoint appliance which has been there for years and years but only capable of 100mbps where we now hvae a 1Gbps connection.   I have setup the new WAN link through the new MX250 one might say the easy bit. I have patched in Port3 in the MX250 directly into our exisiting (and old) HP Aruba core stack and ensured that its a trunk port at both ends so everything should flow.    On our HP network we have address ranges with 10.1.1 and 10.1.5 and 10.1.21 and 10.60.2 and 10.100.1 as well as 172.17.4 and 172.17.20 and 172.17.21 and 172.17.99 and 172.17.99.100   I have a few questions on how best to achieve what we need right now. Do I use routed mode or Passthrough? Single LAN or VLAN given the situation?   Also:   The checkpoint has a static IP of 172.17.99.1 and yet the MX250 doesn't so I am not sure what to use when setting up the routes (I can see that all our switches can have an IP set in them, why not the MX appliance?) Could the VLAN setup inside the HP Aruba core be causing issues? Should we setup our entire stack with MX250, MS425-16, MS355-48x and edge switches of MS255-48FP rather than messing with integration first into the HP Aruba? ... View more