Search results for query: *

AFAIK the VXR chassis has an upgraded backplane. Thus supporting newer & faster modules.

the command is no service config

Update: Putting the whole router behind another (Netgear) router and disabling the dialer interface didnt help at all. The same issues are there, when my DSL gets a new ip / has to relogin with PPPOE my VPN connection is dropped without the router noticing it. I will continue to investigate &...

Adding these should do the trick: ip nat inside source list 110 interface Serial0.1 overload access-list 110 permit ip 192.168.10.0 0.0.0.255 any

1 night has passed and this is what Ive learned from the logs: nothing. I kept my ip overnight, and my Cisco phone stayed online (for once). So Ill have to wait until it decides to disconnect. However Ive run into another problem. My ip nat static commands has for some reason stopped working...

Thanks for all your answers. SFC18C, im using the cli. And ill look into getting a newer IOS asap. However im not sure that is applies to me as im running 12.2, however its worth a try. Also the auto part is kind of working, as the tunnel is automatically connected whenever i reboot the...

You seem to be correct, i just noticed that after a dropout the router reports that: "A pre-shared key for address mask xxxxxxx already exists!" Which is one of the exact same messages I get when i take the dialer interface down & up again. However, im still not certain on how knowing that...

You are correct, im using DSL at home. However i would think that if my dialer would get a new ip it should "know" that it has to reestablish the vpn connection. Or atleast it should do some basic heartbeating to check if the connection is still alive. Ill monitor my Dialer interface and get...

Hi, I have a Cisco 831 (12.2(8r)YN) That im using to EzVpn into my job's concentrator. The tunnel is only used by my Cisco Ip Phone (7960) to reach our CCM. The problem is that once or twice every day the phone drops its connection to the CCM. Upon further investigation i notice that I no...

Try ip nat inside source static <proto> <internal ip to forward to> <port> interface <external interface> <port> This should forward tcp port 2234 ->> 10.1.1.2 port 2234 ip nat inside source static tcp 10.1.1.2 2234 interface ethernet 0 2234

gconnect is correct: 1605R(config)#ip multicast ? auto-enable Support for AAA enabling of ipmulticast heartbeat Monitor multicast heartbeat mrinfo-filter Mrinfo source filter multipath RPF across equal-cost paths netflow NetFlow parameters for multicast...

Also you havent enabled nat. ip nat inside source list 1 interface Ethernet1 overload should do it.

First, dont ever post your password lines on a public board, I suggest you change those passwords asap. The problem seems to be that your access-list 100 doesnt contain any permit statements at all, meaning no traffic can pass in on Ethernet 1. Try to add . access-list 100 permit ip any any...

I am so ashamed to admit this, so be gentle. Apparently I had misunderstood how the authentication works, so I had put in my router username & password in the client when connecting. When in fact I should have entered the name of the group and the pre-shared key. After correcting this mistake it...

I managed to get my hands on the Vpn Client v 3.6.3. It got the same errors. Im really beginning to get desperate here.. I took a look at the ezVPN examples and configured it: I got the same / similar errors: Client: Initializing the connection... Contacting the gateway at 192.168.0.101...

Thanks for your response, I did as you asked and gave it another try. No luck. The debugging info I got is quite huge so I put the full thing at Http://naiv.us/error.txt Config: crypto isakmp policy 1 authentication pre-share group 2 crypto isakmp key vainare address 0.0.0.0 0.0.0.0 crypto...

Ive tried it out with client v. 3.6.6. Same problem. Can anyone spot any errors in my config? Or have any other suggestions?

My router is currently using 12.3 but it is an 1605R so Im quite sure it cant handle AES. Ill give the older client a try.

Thank you, though I found another solution. Due to the extremely messy ACL system i set it up so that there is an ACL that prevents all traffic from 16.x to enter all ports (Except 2) and another that prevents traffic from 0.x to enter the port containing the 16.x net. So instead of applying...

ip nat inside source static tcp 192.168.0.200 3453 interface ethernet 1 3453 Where 192.168.0.200 is your internal server ip. 3453 is ofcourse the (tcp)port. Also make sure your ACL´s allow this traffic. And you should never post the password part of your configs online.