we have a block of IP's 10-15 of them, some being nated for internal services as usual, and it's all working good - so;
.132 webmail / autodiscover
all services are working, but... for some reason, more often then I'd like lately .132 goes into la la land and I cant ping from the outside, pinging is enable for the purpose of checking that this interface (ip) is up...when I cant ping i know users will call cause emails cant be sent from mobile devices, or received.
so i usually loggin with vpn, and i have to generate traffic internal out and eventually .132 comes up. Other then a tracker which i have setup to ping out to keep connection live, which is not working properly - any other ideas? When services are in use .132 has no issue, usually in the evening when less traffic.
Cisco SD-Access 126.96.36.199 Features OverviewBorder handoff enhancements: 4-byte ASNEmbedded wireless support on Fabric edgeFiaB deployment models:Multiple VN for Guest Access in Cisco SD-AccessCisco SD-Access Group-Based Access Control PolicyCisco SD-Access ...
. My work contains abbundance of networking gear.i have 3945 routers with attatched nme,3850 switches 48 gig port with 4 tengig port,3850 switch with 16 fiber ports, fortigate 600d along with servers with 8tbs of free space.if you have any labs for me id ...
Hello I have a network in prodcution like it mensionned in this picture. The customer wants to renovate the current infrastructure by changing all the hardware. For this reason we had think about deploying DNA Center and make automat...
I want to show how to quickly and reliably troubleshoot a network using notepad++.If you are not using Cisco GENIE and your network is not very big and you have several routers/switches only.For illustration, I created a simple topology.First, the loopbac...