Cisco WAN :: 881 VPN Server Connected But Cannot Ping LAN Interface
Dec 11, 2010
I've configured a lot vpn server for 857/1800, etc. But this has never happened.I configured 881 as VPN server using CP.Shared key, local group and local user authetication with split route.Local pool 192.168.100.1-254? I have acl for telnet which allows local pool IPs.I have acl to deny local network to local pool IPs for NAT.I've deleted the whole settings and re-run the wizard. It's still the same thing. I can connect from the VPN Client, but no traffic going through. The problem to me is isakmp with DPD. But why it is dead? Why no response from the server? If it is an error, why connection has no problem.
CISCO ASA 5520 -K9 .Client can connects ASA server and get ip address(172.168.31.X),but can't ping ASA inside interface ip address and other servers in lan .
I have an Cisco 6500 CS and there is a Cisco Unified Communication Manger Server connected directly to the Core Switch.I tried to change duplex and speed ( fix and auto ) for both sides, but the same problem.
Haveing issue with DHCP server handing out IP addresses to client connected to VLAN5 interface.ISP Router>Firewall -(WatchGuard Drop-in mode) I have several 3750 switches and one acting as a L3 switch. The L3 is configured as follow: [code]
If I connect a laptop to int fa1/0/10 I DO NOT get an IP address from the 10.100.0.8 scope. If I connect to another interface within the VLAN 1, I get an address from the 10.100.0.0 range.
I have a new 3560G to set up a small network for a remote site. I configured the vlan and an SVI as the gateway. The switch is also the DHCP server for the LAN. I configured Gi0/2 as L3 port, connecting to the nearest neighbor. My network runs EIGRP so i advertised the routes into the EIGRP process. The switch forms EIGRP neighbors and learns all routes in the enterprise network. The problems I'm having now are: 1. The switch learns all routes in my enterprise LAN and can ping devices in the enterprise LAN, but I can’t ping any interface on the switch from the enterprise LAN. 2.
I have a Cisco ASA 5505 and I have my internal and external interfaces configured but I currently cannot ping from the inside to an IP Address on the outside. I had this setup and working and I have another set of equirement that I am replacing that is working with my service provider so I know it is a configuration issue. When I ping 4.2.2.2 for example I get:
Destination host unreachable
Do I need to add a static route from my inside interface to my outside interfaces?
I installed window server 2003 in a old Pentium III server as a standalone test server. Now I want to use it as a print server and connected it to the domain. I can ping workstations and other servers from that test svr. But i cannot ping that test server from the work stations.
I have a problem with pinging APs that are connected to WLC 2106. We have a TRUNK with VLAN50, VLAN51 and VLAN71 (all tagged) connected to our WLC 2106. VLAN50 is our management network. We have configured bot management and AP-management interfaces on WLC with IP addresses from our management network and we have set both to VLAN 50. We have also configured static IP addresses on every AP, connected to WLC.
The problem is we cannot ping APs. This means that APs can’t connect to any other device on the management network and we would like to use RADIUS for WiFi client authentication.
How can we solve this problem? I guess if we configure VLAN50 as native untagged VLAN in our TRUN, this would work? Is there any way to configure this without using native VLAN?
We also have problem with IPv6 connectivity. We have configured DHCP and we are using 1.1.1.1 DHCP proxy and it works great for IPv4, but how can we configure DHCP proxy for IPv6 addresses? Our WiFi clients need to get also IPv6 addresses. I have enabled “IPv6 enabled” option on the WLC.
The issue i was having is when i connect to 192.168.50.* network i cannot seem to ping or connect to 192.168.51.2 (esxi host1) and 192.168.51.3 (esxi host2) and also free nas device i.e 192.168.52.2. i can only connect to these devices if i ping the 192. 168.50.1 from both the esxi hosts and also from free nas. Everything starts working if i ping from the esxihosts & Freenas device to 192.168.50.1.
f i connect to the hp procurve switch i can ping the hosts fine from the switch not when i connect to Draytek Router i.e 192.168.50.1 unless i run a ping from esxi hosts and free nas device then everything starts working.Here is my network setup for my ESXI home lab.
I have Draytek Vigor 2800 Router with ipaddress 192.168.50.1 (This Router is Downstairs and connected to DSL Line) and another Router with Firmware flushed with DD-WRT and IP address for this is 192.168.50.2. (this router is in upstairs labroom and is connected in Wireless Bridge Mode to Draytek Router Downstairs)
There is a HP Pro curve Switch 2610-24 with IPaddress of 192.168.50.3 and has VLAN's configured on this switch.The VLAN's are : VLAN10 is esxi vlan and ipaddress is 192.168.51.1 and vlan20 is storagevlan and ipaddress is 192.168.52.1 and vlan 30 is internet vlan and ipaddress is 192.168.50.3 (Switch Address).Port 24 is untagged to vlan 30 i.e internet vlan and connnected the port to dd-wrt router lan port. I have untagged ports 1 to 5 to vlan10 i.e esxivlan and connected esxi host's 1 & 2 to ports 1 and 2 respectively and connected freenas device i.e storage to port 6 which is untagged to vlan20 i.e storagevlan
IP Routing is enabled on the switch and ip route 0.0.0.0 0.0.0.0 192.168.50.2 and Default gateway on the switch is 192.168.50.1.
On the Draytek router i have configured a static route for 192.168.51.0/24 and Default Gateway is 192.168.50.3 and another static route 192.168.52.0/24 and default Gateway is 192.168.50.3
I've been stuck with a connection problem on my desktop for 6 months and nothing I do can fix it. My computer technician friends can't fix it either, so here's my last gasp attempt to get it online before I throw the machine out of the window.I'm using XP, don't recall ever having downloaded any Service Packs, and am trying to connect wirelessly to my home network here in France. Laptops and iPhones connect no problem. I don't think it's the wireless network card (which I bought nearly 5 years ago) as I had the same connection problem in my last apartment, with the same internet provider. I eventually borrowed an ethernet cable and managed to get it working wirelessly, but I have no idea how I did it.
The computer connects to the wireless network but I can't browse or ping. I've flushed dns, tried to input the ip manually, checked and unchecked LAN settings, checked and unchecked Internet Protocol TCP/IP, i've tried winsock, I've done the netsh reset and NOTHING worksI've checked the security settings, password and encryption a hundred times, I've disabled the firewall and today I've pulled out the recovery disks It didn't.Interestingly, the desktop has suddenly decided to go online once or twice (after I'd disabled Norton) but as soon as I shut down, I'm back to square one
I have a cisco ASR 1002 I have plugged a host into an addressed port and the port comes up however the host cannot ping the router and the router cannot ping the host. Neither can router ping its self. I do the same on a cisco 2800 router and it works fine. What's goin on. Is it the fact that this is a ASR router ?
I have configured eigrp routing on cisco 1941 ISR with two interfaces advertised. However i can not ping the router interface on g 0/0 but can ping the device and computers attached to that network. When i ping from the same network i'm able to ping the interface but not from anyway else. i can also ping the other devices on other network from g 0/0 attached hosts. How can i enable ping to this interface so that i start monitoring the network?
Below i have attached the network configurations for the router;
I have lots of 857's routers in the field with mostly the latest OS - 12.4(15)T17 making ezVPN connections to a 2951 with 15.1(4)M5.All the 857's have lookback and vlan interfaces similar to :
interface Loopback0 ip address 50.43.8.1 255.255.255.255 ip tcp adjust-mss 1452 end
[code]....
Now lately for some or other reason we have instances where I can ping either the VLAN or the LOOPBACK interface, but not both. Or I have instances where the 2951 can ping all the interfaces on the 857, but the 857 can not ping the 2951. Or I have instances where the 2951 can not ping the 857, but the 857 can ping the 2951.The way I have been fixing this is either to add crypto ipsec client ezvpn SMS_VPN inside to the loopback interface, or if it is there already to remove it. This usually works for a few days, but then suddenly I have to reverse this again. If that does not work then I usually do lots of clear crypt sess and/or clear crypt ipsec client ezvpn on the 857, or clear crypt sess remote 857_ip_address from the 2951 and then suddenly it starts working again.
I have recently installed an ASA5510 at a site in South Africa to connect via VPN to a site in the UK (ASA5520). The VPN comes up fine with the 5520 in the UK, however, I can not connect to the inside interface over the VPN, but can access it from the internal LAN. All other hosts on the LAN are accessible over the VPN.
The 5510 also has another VPN to another site in SA and the 2nd site cannot ping the interface either.
I cannot seem to ping from the outside of my 5520 firewall to an inside network. I have a single physical outside interface connected to a Layer 2 switch, with a laptop connected to it. This is on network 10.11.131.0/28. From there, I cannot ping to the inside interface (which is a sub interface on G0/0) with network 10.11.130.0/24/ For some reason, it doesnt work.
Now. I had access-lists in place, but have removed them for testing and it still doesnt work. I have set the security level of inside and outside to 100, and entered the same-security-traffic permit inter-interface command - still no joy. Below is the relevant configuration.
I've had some issues with my 892 router. [code] When match address is set to acl-net12, I can't ping my router on external interface and tunnel is working very bad (15%-20% packet loss).If I change match address from acl-net12 to acl-net12-new then I can ping my router on external interface and vpn si working fine.
I have also an acl (set on external interface) which allow ping but it seems that is not working when acl-net12 is used on crypto map. [code]
I have a Cisco ASA 5505, the problem is I am not able to ping to outside natted interface (ip: 172.88.188.123 and 124 and 125) from inside network I have looked for ASA documentation through the internet and still got nothing.
I have one problem doing a ping to a router lan interface, I have 3 routers (2801) connected between each other (separated 1 mile each), the link is established trough microwave signals (connected to the 2801 fast ethernet interfaces), every router has a connection to a LAN. One of them is located at headquarters.Last thursday I replace one of the router with a cisco 2901, i configure the router with the same configuration that was on the 2801, i power up the router and the 2 link were up without problems.One day after the noc called me to tell me that after i replace the router they can't ping the router IP lan interface on the new 2901 (before the replacement the ping was sucessful). I called one user the lan connected to that 2901, and they can do a ping to the router's LAN IP address.
I can ping the 2901 IP wan interfaces, I can ping the LAN users ip address, but i cannot ping the router LAN IP address, from my desktop, and neither the 2 routers 2801 connected to the 2901.I show the configuration on the 2901, I couldn't change it because i didn't have time to do that, but i'll change the configuration to use ipsec tunnels.The configuration as you can see, has a crypto map, but the acl used by the crypto map, only permits the interfaces ip address, so i think that doesn't work, so the traffic doesn't get encrypted, but i don't know if that is the problem why i can't do a ping to the lan interface. [code]
I'm trying to set up a Guest VLAN for wireless at a client site, and I feel like I'm missing something small in the configuration, since I can't ping any of the VLAN interfaces from my laptop when the address is statically set to something in the 172.20.100.x range.
I've pasted the configs for the ASA 5505 and the 6 switches below for convenience. Near as I can tell, all should be well. The ports are in trunking mode, the "show cdp neighbors" command returns the proper information, VLAN 100 exists on all the switches, etc.
I've got a netbook (Acer Aspire One) with XP SP3 on it. It connects to my wireless network (so it says), but it won't get onto the internet. I can ping 127.0.0.1, but it won't ping my router. When I do ipconfig /release > ipconfig /flushdns > ipconfig /renew, it hangs up on the renew portion telling me that the DHCP server timed out. The exact error message is:"An error occurred while renewing interface Wireless Network Connection 2 : unable to contact your DHCP server. Request has timed out.No operation can be performed on Local Area Connection while it has its media disconnected"I've checked the TCP/IP settings, it's set to automatically obtain and IP address and DNS servers. I've checked the DHCP service and that's running. The internet works when it's wired. I've used the "repair" function when right-clicking the wireless icon and it tells me it can't renew my IP address. I made an ipconfig /all when it was connected and this is what it came up with:
I have a new ASA 5505 and all is working fine, I can CLI and ASDM into it, but just can't ping the inside interface, do I need to enable a feature to make this work somehow?
I have been working on figuring out a VPN problem on my companies ASA5510. I was accessing the device via: ASDM, SSH using Putty, and even initially with a console cable (also using Putty) using a computer in the networking closet. All 3 of these access methods worked properly for me.I believe I may have inadvertently changed something as of Friday using ASDM. I am mostly assuming this because, as of yesterday I can no longer connect to the device. I actually cannot even communicate with it (ping the interface I normally use to manage, which I could previously ping). No computer on the same subnet as me is able to ping the interface. The device is still accepting VPN connections, dishing out DHCP addresses and everything else it normally does, but I really need to be able to gain access to it again. I am thinking to reboot the device when there is some downtime, in the hopes that ASDM doesn't save to startup-config and only to running-config.
I'm currently configuring an ASA5510.I connected a laptop (IP 192.168.96.18/255.255.255.0) to port 0/2 and tried to ping 192.168.100.2 ... impossible to ping outside interface.I resetted the config of the ASA to retest more simple. [code]
I ran into a very strange icmp ping issue. The network has been working fine other than the issue listed below, L2L VPN works fine and all three data centers can access each other via L2L VPN.I have three ASA5510. [code]
What would cause an interface to show up/up (looped), but you still can't ping that loop?...It is on a Cisco 7613 with an Enhanced FlexWan (WS-X6582- 2PA), with a Mx Serial PA, 8 ports (73-1580-10) and running IOS ver 12.2(33)SRE2 [code]
I have an ASA 5505 that I'm trying to set up a guest network on. I've configured an interface as a trunk and allowed the 2 vlans but I'm not getting any layer 3 to it. The switch connected to it is a 3560 and port is configured as a trunk with the same vlans.
I can't ping the ASA inside interface but I see its MAC address in the swtich's table.
The ASA is configured in very simple transparent mode. As desired, traffic can flow in each direction between inside and outside. I can manage the ASA via console and direct connection to the management interface. The problem is that I cannot ping or ssh to the ASA via the inside interface. I need to be able to manage the ASA from any PC on the inside LAN. I suspect I am missing some easy aspect of the configuration but after a lot of hours I'm about at the end of my patience with it. Here is what I believe to be the relevant parts of the config.
So I have a client with an ASA 5520 running version 9.0 (was on 8.4) that I am trying to get either IPSec or SSL VPN configured on. I got everything setup and tried to connect. However, I couldn't connect to either. I fired up the real time monitoring and didn't see any syslog messages referring to a VPN build up. I also enabled SSH/Telnet on the outside interface and cannot connect to the ASA outside interface. I can ping the outside interface and can ping the internet from the ASA. I did set up a test ACL on the ASA and ran packet tracer on it and the results came back fine.
There is an IPS in the ASA as well, but I disabled the ACL for that and still am having these issues. Part of me wonders if the ISP has something set up to block inbound traffic. This should be a business class connection.
I have a copper over ethernet connected to an adtran 908e connected to an ASA 5505 with a port 192.168.150.254 connected to the router on the Gigabitethernet 0/0
I can ping to internal and external ip addresses but when a device is connected through the wireless signal then the device cannot ping anything; what could be stopping the device from pinging any ip addresses internal and external?
I posted my current config for the router and ap:
Router: Current configuration : 2245 bytes ! ! Last configuration change at 16:03:06 UTC Tue Sep 6 2011
I'm trying to configure a 2800 series router. .I'm consoled in and put a basic config on the router (see attached). After putting this basic config on, I plugged it into a small unmanaged switch, changed my laptop's IP and plugged it in the switch also. I can't ping the router from the laptop and vice versa. This is the second switch I've tried this with, so it must be.The first switch, I installed at location, connected a cisco cable to it and a local server, so i could remote in and finish configuration. In that scenario, I had plugged the switch into a managed switch and had the same result as I'm getting now--can't ping IP addresses (can't ping the switch's IP, not can it ping local IPs).
I am trying to connect my 2800 Series CIsco Office router with VPN client software from home. I can successfully authenticate and get the IP address from the pool configured but couldnt ping any LAN Ips including default gateway. I am pasting my router's configuration.
IP Address Of LAN: 192.168.22.x/ 24 IP Addresses handed out to Clients: 10.10.10.5- 10.10.10.20 aaa new-model ! ! aaa authentication login default local
[code]....
I have noticed that my virtual-access interface comes up but the line protocol of virtual-interface remains down as follows:
Virtual-Template100 x.x.x.x YES TFTP up down
Also The client PC picks up a random gateway of 10.10.10.1 which I never configured anywhere on the server.
I've setup a CISCO 871 which receives DHCP IP address on WAN interface Fa4 and DHCP-assigned static IP Address on virtual-ppp1. The static address is used for site-to-site VPN's, while I've planned the DHCP address for standard web access and CISCO VPN Client dial-out.
Internally, I've created 2 VLAN's, one for standard PC's with access to the remote sites via site-to-site and cisco client, and the other for a 'secured' area with only HTTP/S allowed out. [code]
Clients in the PCLAN should also be allowed to dial-out using CISCO VPN client to remote sites via the OUTSIDE interface. This is partially working because the client does log into a remote site, however I cannot ping or rdp remote stations once connected."ip inspect log drop-packets" does not reveal dropped packets when trying to ping or rdp. [code]
