Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi everyone,I'm not sure if I've created a problem on our network with our MX devices.We have a single LAN network 192.168.100.0./22 (No VLANs)We have a single DMZ network 172.16.30.0/24 (No VLANS)These networks are physically separated different swi...
New MX user here:I've just replaced an ASA 5510 with an MX device which is going fine so far, apart from the Client VPNI can connect to the VPN and can ping the MX LAN IP I can also ping 192.168.100.31192.168.100.48(In fact i can't ping anything else...
Thank you, just came across this issue and it turned out to be a miniport device that was the culprit.I don't know which one i just uninstalled the main adapter and all miniport devices then reboot all reinstalled automatically and tried to connect t...
@jdsilva That's one thing we don't have to worry about as we run fixed IP for everything.(something else we inherited!)I disabled DHCP on both interfaces on both MXs before we tried going live.@robbytachenyI'll take a look at those articles thanks.ED...
Hi T-800,Your first sentence is spot on that is exactly what we have!(well what we inherited from previous employees no longer here anyway)Would i be correct in saying that the ASA5510's were not acting as L3 gateways ?Hence us not having any problem...
Hi Adam,We don't have two networks there is only one LAN 192.168.100.0/22We don't have site to site VPNsALL PCs and Servers sit on the same LANThanksIan
What do you mean by redundant link?I've never really got my head around spanning tree!I always assumed it was to do with accidentally creating loops on the network.Some of our switches have trunked fibre ports to give larger bandwidth between buildin...
