Hot answers tagged cisco
Sure, that info's usually in the output of show version , though that might vary with specific devices and software versions.
Please have a look at the following: http://msdn.microsoft.com/en-us/library/azure/jj156075.aspx According to the documentation, assuming all of your network information is correct, you should disable Perfect Forward Secrecy if you are using static routing.
what is the difference between inside_access_in and inside_access_out ? Inside_access_in and Inside_access_out are just friendly names for your access lists. In your case, Inside_access_in is an 'Inbound' access-list, and inside_access_out is an 'Outbound' access list. An inbound access-list is applied to traffic as it ENTERS that interface. ...
I admit to being initially confused by your question, because this sounds like a nonstandard configuration. I'd expect you to be installing AnyConnect on your home machine. (I suspect this is Cisco's assumption as well; I don't see Server 2003 as an approved OS for AnyConnect.) Rather than ask you what specific problem you're trying to solve with this ...
Does your host use a DNS name? If so, ask for DNS rewrite to be enabled on the Cisco ASA NAT rule for your host.
It's just device oversubscription. The ratio of oversubscription on that particular module is 8:1. So in industry terms, it's a "blocking" switch, versus a "non-blocking" device. See this document from Cisco explaining the blocking ratios. The ports are grouped 1-8, 9-16, and so forth. The better question is whether you're continually pushing Gigabit-speed ...
What you are looking to do is perform REVERSE PORT ADDRESS TRANSLATION. People call it all sorts of crazy things like: NAT Hairpinning, NAT-on-a-stick, NAT reflecting, and NAT loopback. Just to clear this up,.. Hairpinning is a technique used in a NAT-on-a-stick configuration that involves having the NAT "loopback" the traffic. This sounds like what ...
I have had this problem before -- and if your tunnel is up correctly and the Cisco side is pinging through into the 192.168 network, it means your tunnel is up and passing traffic. If you can't ping back to the Cisco or the 10.10 segment, the problem is not the tunnel. The problem is -- most likely -- that you are usng the Ubuntu box as your firewall for ...
Sadly the NAT is happening before the policing I believe; thus making all traffic appear as the NAT'ted address instead of the internal address you have specified in your ACL / Class Map. One idea is to mark the traffic coming in on FA0/0 matching the Ubuntu server with a DSCP value. Then police based on that DSCP value. That will solve your outbound ...
Reset it to factory default settings with the reset button on the device (hold it down as the device boots up) to clear out whatever configuration it has on it, and then login with the default username and password (admin for both).
Can I still add this switch as a slave? No. It cannot be added as a stack member as it does not have the required stack ports.
Only top voted, non community-wiki answers of a minimum length are eligible