Recent content by joshglover72

I cannot hit any other server except for 10.10.10.5 which is the dc, dhcp, and dns server.

Here is some commands on that IP, very strange. C:\Documents and Settings\Administrator>ping files1 Pinging files1.e5groupllc.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets...

OK this is goofy. I can now hit 10.10.10.5 via ping, rdp, and file browsing from the VPN. However, I cannot hit 10.10.10.10 via ping, rdp or file browsing from the vpn, but I can do all those from an rdp session from the outside???????

This is what the routing looks like on 10.10.10.1 Static Routing Static Routes can be entered in the spaces below. "Subnet IP" is the IP address of the subnet being defined. "Subnet Mask" is the subnet mask of the subnet being defined. "Gateway IP" is the IP address of the DSL Gateway and can...

I verified the dhcp server is sending out the correct gateway and it is. Also all static assigned devices also have the correct gateway.

Unfortunately I am not onsite to do this. Just using telnet to device and RDP. Testing with vpn client.

Logs: E5ASA(config)# sh access-list access-list cached ACL log flows: total 0, denied 0 (deny-flow-max 4096) alert-interval 300 access-list acl_in; 1 elements access-list acl_in line 1 extended permit icmp any any (hitcnt=49) 0x08983e47 access-list fass_splitTunnelAcl; 1 elements...

Cisco Adaptive Security Appliance Software Version 7.2(4) Device Manager Version 5.2(4) Compiled on Sun 06-Apr-08 13:39 by builders System image file is "disk0:/asa724-k8.bin" Config file at boot was "startup-config" E5ASA up 34 mins 33 secs Hardware: ASA5505, 256 MB RAM, CPU Geode 500 MHz...

I have added the routes to that device previously. The reason I think it is an ACL issue is this. I am trying to ping, folder browse, RDP, SIP communications from the vpn client: 192.168.10.0 network to the 10.10.10.0 network. Right now I can ping 10.10.10.1 (Gateway), 10.10.10.254 (asa...

Yes as the asa is not doing the primary routing of the network. ASA will only be used for client vpn connectivity.

Here is the config that is on the box as I had the same outcome removing nat and changing subnets. hostname E5ASA domain-name .com names ! interface Vlan1 nameif inside security-level 100 ip address 192.168.10.2 255.255.255.0 ! interface Vlan2 nameif outside security-level 0 ip address...

I tried removing nat and putting the VPN pools on different subnets and it still didn't work.

I disabled the firewall portion to see if it made a difference and it did not. It can ping the interfaces of the asa and that is beyond the fireall.

I don't think it would be the other firewall. I think that you wouldn't be able to connect to device's internal web page if that were the case? Or even establish a vpn connection. Ports that are open from that firewall to the ASA are: 10000 4500 1723 500

192.168.10.0 IP's for the clients