Lost ability to connect through port forwarding after cisco guest software install

Using Remote Admin 2.2 software to remote into work computer.
E1000 I installed the cisco guest software on my pc and configured the guest about 2 months ago.
 Needed to get into office PC this past weekend and connection fails.
Have a static IP address on router.  forward a single port to my office machine within the router.
Get nothing but an error on connection.  Router is 2.1.02 build 6Jan 15, 2013.
Log file shows nothing on the incoming log?  dynamic ip at home...
Another office worker, on the same internal network,  has gotomypc running and port forwarding setup on router and he is still working fine, he can access his pc from home.  The only change I have made to router was the cisco connect for guest access.
Is it possible this is stopping my remote admin?
thanks kevin

Hey kevboac! Make sure that the computer you're using to access the remote computer is connected to the main wireless network and not to the Guest network. Being connected to the Guest network will prevent you from doing File and Printer Sharing, and Remote Access. Hope this helps!

Similar Messages

  • Have suddenly lost ability to connect to internet. Account and bills up to

    I have suddenly lost ability to connect to the internet, include itunes and App Store. Account and bills up to up date. ANy assistance appreciated

    I am having this problem as well. In the last week or two, my calendars haven't been syncing properly. Nothing goes updates to my main computer from the phone. Then in the last few days I could only access the internet sporadically, today not at all. No map showing in the gps, safari doesn't work, no weather... It says 'Safari could not open the page because the server stopped responding'. The 3G wheel is spinning and shows that there is service.
    I reset my phone completely a couple of days ago, reset history/cache, etc in settings, have turned it off and on, etc with no change.

  • Suddenly lost ability to connect on FaceTime?  help?

    Why would I have suddenly lost ability to connect on facebook?

    Apple is having problems with os6  update. The system has crashed a couple of times, and they are working on the problem.

  • Help: Port forward in Cisco SOHO 97

    Hi there!
    I have a Cisco SOHO 97.
    The IP is: 10.0.0.1/24
    Gw: 0.0.0.0
    *Default route via DIALER1
    I also have a RV042 configured as VPN Server (PPTP and IPSec).
    The IP is: 10.0.0.2/24
    I need help to configure the router to I be able to connect to VPN server from OUTSIDE-WORLD.
    I imagine I need Port forwarding from Cisco SOHO to RV042.
    I hope for possibles answers!
    Thanks!

    Sorry i found the issue.
    The problem was that, i wanted to redirect port 443 (https) to an private address.
    But by default port 443 is reserved to access ASA via https for management.
    I just reserved another port 888 for https management access and now i can redirect port 443 normaly as i wanted.
    Using this command: http server enable 888
    Germain

  • Unable to connect to Arch VM through port forward.

    I'm attempting to run Arch as a web server through VMware, everything appears to be working. The guest can connect to everything with some edits through the network editor, I can type my hosts IP in and it'll connect perfectly to the ArchVM.
    So everything seems to be working through my internal network, I just can't port forward the connection so that I can access my server over my internet IP. All my ports seem to be correct and opened like they need to be, I just can't see why I can access it perfectly fine on my internal network just not my external one.
    Could it be an issue with VMware not allowing port forwarding to it's internal guests(It doesn't make sense)? Any ideas/stats I can give you guys to help me out.
    Thanks
    ~Compulsed.
    Last edited by Compulsed (2012-01-04 04:20:05)

    Is your router configured to forward the necessary ports to the host ?
    Do you have a firewall/iptables running at the host ?
    if so, try connecting while iptables is stopped

  • Time Capsule disconnects internet when using web server through port forwarding

    My current config is: 2TB Time Capsule running 7.6.3, Mac Pro running Lion (10.7.5), MacBook Pro running Mountain Lion (10.8.3), and a couple of MacBook Pro Retinas running Mountain Lion. My current ISP is Comcast.
    I have the Time Capsule set up to port forward port 80 to the Mac Pro for the purpose of running a web server. Most of the traffic is shuttling fairly large m4v files back and forth to work (work product from video editing work). I can reach the webserver on the Mac Pro just fine from the outside world, and can list files in the directory just fine. When I initiate a download (via right click on a link, "Save As..." or whatever), the Time Capsule reports that the Internet has been disconnected, and all machines inside my network lose access to the outside world. I have to either power cycle the Time Capsule, or disconnect/reconnect the Cat-6 cable between the cable modem and the Time Capsule to re-establish the connection. Interestingly, the download continues and completes on the other end without issue (so, the connection is actually still there!).
    Before switching to Comcast, I was on AT&T Uverse - Uverse includes a router, so I had the TIme Capsule set up in Bridge Mode. That worked fine. I also have an older 500GB 1st generation Time Capsule. I set it up with the same config as my 2TB TC, and it shows the exact same behavior - internet disconnects upon initiating a file download through a forwarded port. I then hooked the Mac Pro up directly to the cable modem. I can initiate a download without issue, and I continue to stay connected to the Internet without problem. Called Comcast anyway - they report no errors on the line, but reset the whole device chain anyway. No change in behaviors.
    I tried downgrading the Time Capsule software to 7.6.2 (the earliest version that came on it). No dice, same behavior.
    So... I called Apple. Complete and utter FAIL. Apple Support reports that they have no training in the port forwarding features of the Time Capule or Airport products, and cannot help me resolve the issue because of that. So, I have a $300 router that apparently cannot perform a simple routing function (download through a forwarded port), that I cannot troubleshoot (because Airport software v7 is an epic fail in that regard), made by a company who cannot support it - and everything this $300 device is doing can be done by a $50 device with a $100 external hard drive?
    Do I understand this situation correctly? What have I missed in trying to troubleshoot this thing?

    Apple Support reports that they have no training in the port forwarding features of the Time Capule or Airport products, and cannot help me resolve the issue because of that. So, I have a $300 router that apparently cannot perform a simple routing function (download through a forwarded port), that I cannot troubleshoot (because Airport software v7 is an epic fail in that regard), made by a company who cannot support it - and everything this $300 device is doing can be done by a $50 device with a $100 external hard drive?
    Do I understand this situation correctly? What have I missed in trying to troubleshoot this thing?
    Excellent summary.. I think you have covered all the salient points most thoroughly.
    Port forwarding on the TC I would put into the category of "epic fail"
    I have a nasty feeling it just doesn't work in many cases. Clearly from your situation the port is forwarded correctly.. it is the actual download that is causing the device to crash.. which is probably not the port forwarding itself that is at fault but rather the external link and opening another port for the download to happen.
    Many of the issues were caused by using icloud and btmm.. which would work a lot better btw. Although the hassle there is needing to offer that as a service to any Tom Dick or Harry.
    Let me suggest a work around or other things to try.
    I also have an older 500GB 1st generation Time Capsule. I set it up with the same config as my 2TB TC, and it shows the exact same behavior - internet disconnects upon initiating a file download through a forwarded port.
    Use 5.6 utility.. more info below. And take the firmware of this unit (Gen1) back to 7.5.2 (before icloud mess ups in 7.6).
    You can go back to 7.5 firmware also in Gen4 TC if it is more than about 14months old.. Simply hold down the option key when you select firmware and the old versions will show up. If your TC came with 7.6.1 (the 7.6.2 was withdrawn as it was even bigger failure than 7.6.3). then you cannot go back.
    You might also find downloading via http is not as reliable as using FTP.. FTP is a better and more efficient protocol. It should be no problem to setup ftp server on the mac pro to allow download via ftp even with a browser.
    But in the end.. your $50 router suggestion.. well perhaps a little more than that.. $80-100 will work very well.. also this router can be setup with a Hard Disk and offer the files to the internet via FTP.. without needing full network access to your internal network.
    How to load 5.6 into ML.
    1. Download 5.6 for Lion.
    http://support.apple.com/kb/DL1482
    Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
    2. Download and install unpkg.
    http://www.timdoug.com/unpkg/
    Run unpkg on the desktop.. it is very simple.. drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. drill down.. applications utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
    You cannot uninstall 6.1 (now 6.2 if you updated) so don't try.. and you cannot or should not run them both at the same time.. so just ignore the toyland version.. the plastic hammer.. and start using 5.6.. a real tool.
    For screen shots see this post.
    https://discussions.apple.com/thread/4668746?tstart=0

  • Lost ability to connect to open WiFi router

    I've been using Leopard 10.5 that was installed when I bought the computer, and just updated to 10.5.4 which solved a problem I had running the original Adobe CS, InDesign was running 100+ percent of the CPU and crashing. But, I also lost the ability to connect to the open, non-WEP WiFi network in my studio. I have no idea why it won't connect and the computer connects fine at home to my airport. I think the router at my studio is a Linksys or something, but I really need to get my MacBook Pro to connect back to the router. Also, airport seems to be scanning continuously and fails to show the networks quickly. It seems very laggy.
    Any suggestions?

    If you see line after line of "Airport Beacon (Lost)" messages, the problem is with 10.5.3 upgrade, if you installed 10.5.4 a few days later when it came out, you still have the problem.
    That is simply not true. Beacons can be "lost" for a lot of reasons - and it has been happening to some people before 10.5.3 [Check the history!|http://discussions.apple.com/search.jspa?threadID=&q=airport+10.5.2&ob jID=&dateRange=thisyear&userID=&numResults=15&rankBy=10001]. It might be the 10.5.3 upgrade in some situations. I am a bit suspicious of the interaction between some Netgear routers and OS X, but I have not tested that theory very thoroughly.

  • Have lost ability to connect Cisco VPN - Westell 6100G modem and Netgear WNR1000 v2 router

    I have lost the ability to connect my work laptop VPN through my verizon dsl connection.  It works at the library, at hotels, and over my BB tether.  Corporate IT thinks it is either the router or the modem.  There are also some websites that will not load, such as tetongravity.com.  The websites seem to be a problem over a wired connection as well as wireless, and I have only tried attaching the VPN while on a wirelesss connection.
    Any advice on how to straighten this out?  I have rebooted both a couple of times and updated the firmward on the router to no avail.  Also, do you know what the default user name and password are on the modem?
    Any help would be appreciated.
    John

    PS - it worked last week, and stopped working over the weekend.

  • RV220W (1.0.4.17) - losing ability to connect through QuickVPN, reboot needed

    I keep getting a lot of errors in my log messages. Please, look at attachment.
    My problem manifests itself notoriously every 3-4 days. I have to do reset to connect through QuickVPN.
    Please, look at the newest log:
    2012-11-26 14:20:48: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=80f1f2dd37522b58:123fc4cc5c3b558a.
    2012-11-26 14:20:48: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=e728a1b036ccdb32:76014c353c9099fe.
    2012-11-26 14:20:48: [rv220w][IKE] WARNING:  no phase2 found for "m-test"
    2012-11-26 14:20:48: [rv220w][IKE] INFO:  IPSec configuration with identifier "m-test" deleted sucessfully
    2012-11-26 14:20:49: [rv220w][IKE] ERROR:  sainfo identifier not found ("m-test")
    2012-11-26 14:20:49: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "m-test"
    2012-11-26 14:20:49: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-93.154.129.33[4500] with spi:80f1f2dd37522b58:123fc4cc5c3b558a
    2012-11-26 14:20:49: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-93.154.129.33[4500] with spi:e728a1b036ccdb32:76014c353c9099fe
    2012-11-26 14:20:49: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2012-11-26 14:20:49: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2012-11-26 14:24:52: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:24:52: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:00: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:00: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:01: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:01: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:02: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:02: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:05: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:05: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:08: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:08: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:11: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:11: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:14: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:14: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:17: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:17: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:21: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:21: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:24: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:24: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:27: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:27: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:30: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:30: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:33: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:33: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:36: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:36: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:39: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:39: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:42: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:42: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    2012-11-26 14:25:45: [rv220w][IKE] ERROR:  Invalid exchange type 243 from 88.196.5.36[16].
    2012-11-26 14:25:45: [rv220w][IKE] ERROR:  Could not find configuration for 88.196.5.36[16]
    I'm so tired of the continuous reset the router...
    Edited by: Thomas Michalski

    Today I experience even stranger behavior
    this time even restart does not help
    application QucikVPN shows an error and does not create tunnel
    however, in the administration panel, the user appears to be connected
    log:
    2011-01-01 00:00:42: [rv220w][IKE] INFO:  IKE started
    2011-01-01 02:02:18: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "MKConnect"
    2011-01-01 02:02:18: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "MKConnect"
    2011-01-01 02:02:51: [rv220w][IKE] INFO:  IKE stopped
    2011-01-01 02:02:53: [rv220w][IKE] INFO:  IKE started
    2011-01-01 02:02:54: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "MKConnect"
    2011-01-01 02:02:54: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "MKConnect"
    2011-01-01 02:03:44: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2011-01-01 02:03:45: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2011-01-01 02:03:47: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:20:59: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:21:36: [rv220w][IKE] INFO:  IKE stopped
    2012-12-12 11:21:38: [rv220w][IKE] INFO:  IKE started
    2012-12-12 11:21:39: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "MKConnect"
    2012-12-12 11:21:39: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "MKConnect"
    2012-12-12 11:21:58: [rv220w][IKE] INFO:  IKE stopped
    2012-12-12 11:22:00: [rv220w][IKE] INFO:  IKE started
    2012-12-12 11:22:01: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "MKConnect"
    2012-12-12 11:22:01: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "MKConnect"
    2012-12-12 11:22:08: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:22:09: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:22:11: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:22:14: [rv220w][IKE] INFO:  IKE stopped
    2012-12-12 11:22:16: [rv220w][IKE] INFO:  IKE started
    2012-12-12 11:22:16: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "MKConnect"
    2012-12-12 11:22:16: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "MKConnect"
    2012-12-12 11:23:23: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:23:24: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:23:26: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:23:30: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:24:33: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:24:34: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:24:37: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:24:40: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:25:53: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:25:54: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:25:56: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:26:00: [rv220w][IKE] ERROR:  Could not find configuration for 88.149.181.128[500]
    2012-12-12 11:26:40: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "mk-test"
    2012-12-12 11:26:40: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "mk-test"
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Configuration found for 88.149.181.128[500].
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 46.28.241.202[500]<=>88.149.181.128[500]
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:26:43: [rv220w][IKE] INFO:  For 88.149.181.128[500], Selected NAT-T version: RFC 3947
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  NAT-D payload matches for 46.28.241.202[500]
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  NAT-D payload does not match for 88.149.181.128[500]
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  NAT detected: PEER
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 88.149.181.128[54975]
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  ISAKMP-SA established for 46.28.241.202[4500]-88.149.181.128[54975] with spi:6234ae59f51fa46e:767c84c57bfdca16
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 46.28.241.202[0]<=>88.149.181.128[0]
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  Using IPsec SA configuration: 192.168.0.0/24<->192.168.0.16/32
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 54975->4500]: ESP/Tunnel 88.149.181.128->46.28.241.202 with spi=235876248(0xe0f2f98)
    2012-12-12 11:26:44: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->54975]: ESP/Tunnel 46.28.241.202->88.149.181.128 with spi=2590254398(0x9a64253e)
    2012-12-12 11:27:14: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'pk_recvupdate'.
    2012-12-12 11:27:14: [rv220w][IKE] INFO:  Purged IPsec-SA with proto_id=ESP and spi=2590254398(0x9a64253e).
    2012-12-12 11:27:14: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=6234ae59f51fa46e:767c84c57bfdca16.
    2012-12-12 11:27:15: [rv220w][IKE] WARNING:  no phase2 found for "mk-test"
    2012-12-12 11:27:15: [rv220w][IKE] INFO:  IPSec configuration with identifier "mk-test" deleted sucessfully
    2012-12-12 11:27:15: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-88.149.181.128[54975] with spi:6234ae59f51fa46e:767c84c57bfdca16
    2012-12-12 11:27:15: [rv220w][IKE] WARNING:  no phase1 found for "mk-test"
    2012-12-12 11:27:15: [rv220w][IKE] INFO:  IKE configuration with identifier "mk-test" deleted sucessfully
    2012-12-12 11:27:15: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "mk-test"
    2012-12-12 11:27:15: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "mk-test"
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Configuration found for 88.149.181.128[500].
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 46.28.241.202[500]<=>88.149.181.128[500]
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:18: [rv220w][IKE] INFO:  For 88.149.181.128[500], Selected NAT-T version: RFC 3947
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Configuration found for 88.149.181.128[500].
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 46.28.241.202[500]<=>88.149.181.128[500]
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  For 88.149.181.128[500], Selected NAT-T version: RFC 3947
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  NAT-D payload matches for 46.28.241.202[500]
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  NAT-D payload does not match for 88.149.181.128[500]
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  NAT detected: PEER
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 88.149.181.128[54975]
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  ISAKMP-SA established for 46.28.241.202[4500]-88.149.181.128[54975] with spi:a40cc887fba17130:ceb68a542e2be5d0
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 46.28.241.202[0]<=>88.149.181.128[0]
    2012-12-12 11:27:22: [rv220w][IKE] INFO:  Using IPsec SA configuration: 192.168.0.0/24<->192.168.0.16/32
    2012-12-12 11:27:23: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2012-12-12 11:27:23: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 54975->4500]: ESP/Tunnel 88.149.181.128->46.28.241.202 with spi=150477233(0x8f819b1)
    2012-12-12 11:27:23: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->54975]: ESP/Tunnel 46.28.241.202->88.149.181.128 with spi=1882202289(0x703020b1)
    2012-12-12 11:28:18: [rv220w][IKE] ERROR:  Phase 1 negotiation failed due to time up for 88.149.181.128[500]. 413c589713f8bf63:ddd3bbd10b497c11
    2012-12-12 11:29:20: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "mk-test2"
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Configuration found for 88.149.181.128[63020].
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 46.28.241.202[500]<=>88.149.181.128[63020]
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  For 88.149.181.128[63020], Selected NAT-T version: RFC 3947
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  NAT-D payload matches for 46.28.241.202[500]
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  NAT-D payload does not match for 88.149.181.128[63020]
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  NAT detected: PEER
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 88.149.181.128[58145]
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  ISAKMP-SA established for 46.28.241.202[4500]-88.149.181.128[58145] with spi:358b08830b0aa15a:9962476ade8cf013
    2012-12-12 11:29:32: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2012-12-12 11:29:53: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=358b08830b0aa15a:9962476ade8cf013.
    2012-12-12 11:29:54: [rv220w][IKE] WARNING:  no phase2 found for "mk-test2"
    2012-12-12 11:29:54: [rv220w][IKE] INFO:  IPSec configuration with identifier "mk-test2" deleted sucessfully
    2012-12-12 11:29:54: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-88.149.181.128[58145] with spi:358b08830b0aa15a:9962476ade8cf013
    2012-12-12 11:29:54: [rv220w][IKE] ERROR:  sainfo identifier not found ("mk-test2")
    2012-12-12 11:29:54: [rv220w][IKE] ERROR:  Failed to Delete the IPSec configuration with identifier "mk-test2"
    2012-12-12 11:29:54: [rv220w][IKE] ERROR:  remote identifier not found ("")
    2012-12-12 11:29:54: [rv220w][IKE] ERROR:  Failed to Delete the IKE configuration with identifier ""
    2012-12-12 11:32:23: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'pk_recvupdate'.
    2012-12-12 11:32:23: [rv220w][IKE] INFO:  Purged IPsec-SA with proto_id=ESP and spi=1882202289(0x703020b1).
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Configuration found for 88.149.181.128[500].
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 46.28.241.202[500]<=>88.149.181.128[500]
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  For 88.149.181.128[500], Selected NAT-T version: RFC 3947
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  NAT-D payload matches for 46.28.241.202[500]
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  NAT-D payload does not match for 88.149.181.128[500]
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  NAT detected: PEER
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 88.149.181.128[54975]
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  ISAKMP-SA established for 46.28.241.202[4500]-88.149.181.128[54975] with spi:384bbd58ba55b90a:a84afa687a9cbdac
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 46.28.241.202[0]<=>88.149.181.128[0]
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Using IPsec SA configuration: 192.168.0.0/24<->192.168.0.16/32
    2012-12-12 11:32:24: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2012-12-12 11:32:25: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 54975->4500]: ESP/Tunnel 88.149.181.128->46.28.241.202 with spi=242919503(0xe7aa84f)
    2012-12-12 11:32:25: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->54975]: ESP/Tunnel 46.28.241.202->88.149.181.128 with spi=3164297225(0xbc9b5809)
    2012-12-12 11:34:18: [rv220w][IKE] INFO:  an undead schedule has been deleted: 'pk_recvupdate'.
    2012-12-12 11:34:18: [rv220w][IKE] INFO:  Purged IPsec-SA with proto_id=ESP and spi=3164297225(0xbc9b5809).
    2012-12-12 11:34:18: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=384bbd58ba55b90a:a84afa687a9cbdac.
    2012-12-12 11:34:18: [rv220w][IKE] INFO:  Purged ISAKMP-SA with proto_id=ISAKMP and spi=a40cc887fba17130:ceb68a542e2be5d0.
    2012-12-12 11:34:19: [rv220w][IKE] WARNING:  no phase2 found for "mk-test"
    2012-12-12 11:34:19: [rv220w][IKE] INFO:  IPSec configuration with identifier "mk-test" deleted sucessfully
    2012-12-12 11:34:19: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-88.149.181.128[54975] with spi:384bbd58ba55b90a:a84afa687a9cbdac
    2012-12-12 11:34:19: [rv220w][IKE] INFO:  ISAKMP-SA deleted for 46.28.241.202[4500]-88.149.181.128[54975] with spi:a40cc887fba17130:ceb68a542e2be5d0
    2012-12-12 11:34:19: [rv220w][IKE] WARNING:  no phase1 found for "mk-test"
    2012-12-12 11:34:19: [rv220w][IKE] INFO:  IKE configuration with identifier "mk-test" deleted sucessfully
    2012-12-12 11:34:19: [rv220w][IKE] INFO:  Adding IPSec configuration with identifier "mk-test"
    2012-12-12 11:34:19: [rv220w][IKE] INFO:  Adding IKE configuration with identifier "mk-test"
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Configuration found for 88.149.181.128[500].
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received request for new phase 1 negotiation: 46.28.241.202[500]<=>88.149.181.128[500]
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Beginning Identity Protection mode.
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received Vendor ID: MS NT5 ISAKMPOAKLEY
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received Vendor ID: RFC 3947
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  Received unknown Vendor ID
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  For 88.149.181.128[500], Selected NAT-T version: RFC 3947
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  NAT-D payload matches for 46.28.241.202[500]
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  NAT-D payload does not match for 88.149.181.128[500]
    2012-12-12 11:34:23: [rv220w][IKE] INFO:  NAT detected: PEER
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  Floating ports for NAT-T with peer 88.149.181.128[54975]
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  ISAKMP-SA established for 46.28.241.202[4500]-88.149.181.128[54975] with spi:1e132d66de83ecd7:83eed503d4f27fe5
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  Sending Informational Exchange: notify payload[INITIAL-CONTACT]
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  Responding to new phase 2 negotiation: 46.28.241.202[0]<=>88.149.181.128[0]
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  Using IPsec SA configuration: 192.168.0.0/24<->192.168.0.16/32
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  Adjusting peer's encmode 3(3)->Tunnel(1)
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 54975->4500]: ESP/Tunnel 88.149.181.128->46.28.241.202 with spi=22547734(0x1580d16)
    2012-12-12 11:34:24: [rv220w][IKE] INFO:  IPsec-SA established[UDP encap 4500->54975]: ESP/Tunnel 46.28.241.202->88.149.181.128 with spi=714334032(0x2a93df50)

  • Idle Oracle DB connection through ACE dropped after 1 hour

    Hi folks,
    I'm looking for some ideas how to troubleshoot a problem we're having with an Oracle App.
    What we are finding is that when a request takes more than an hour for the Oracle DB to process the connection is being dropped.
    When wireshark is used at DB server interface we see nothing for an hour and then a single packet RST,ACK with the source identified as the App Server.
    We have an App server farm that is behind an ACE module that is in bridging mode. The DB server is on another VLAN so the path the traffic takes is from the App Svr through the ACE from the back to the frontside vlan, through the 6506's MSFC to be routed to the DB server.
    Path like this:
    Appserver|-->VL203-->|ACE|-->VL202-->|L3 Switch|-->VL200-->|DB Server
    If we move the App server to Vlan 202 in front of the ACE the process carries on to completion (after 75 mins).
    Is there anything in the ACE settings that could cause the connection to be dropped after an hour for traffic that should simply be being bridged through?
    Any suggestions as to where to look next would be appreciated.
    TIA
    Zac

    OK Gilles, I'll look at that in the morning. However, this is where it gets interesting.
    We have DB servers on two other VLANs routed by the same switch. The connections to those DB servers don't get cut off after an hour (In the connection path I outlined swap VLAN 200 for VLAN 50 or VLAN 205) One of them is even behind the ACE in a different server farm.
    Zac

  • Suddenly lost ability to connect to others for gaming

    For 6 months, 4 friends of mine could connect to me no problem via port forwarding to play a game.  I own a wrt54g that works great.
    Last Sunday, this stopped suddenly, no one could connect to me.  Why?
    The only change is that I downloaded a couple 'updates' that Vista 'recommended'.  But this shouldn't chg my firewall or port forwarding settings.
    -Frustrated

    It might be the firewall security on your computer which you updated on your Vista computer.try to turn Off the firewall and check if it helps...

  • My iPad loses it's ability to connect to the internet after awaking from sleep mode. Needs to be rebooted to reconnect.

    My iPad loses it's ability to reconnect to the wifi after sleep mode often times, but not always. It is very annoying because it requires a reboot to reconnect. It is running the latest iOS software update. I have also reset network settings to the factory defaults. My wifi is working fine, and all other devices in my house have no issues at all.

    Well, I think I have finally come up with a solution. It seems this issue happens when it auto locks. I turned auto lock to "never" in settings, and the issue has not happened since. Seems there may be a bug in this feature???
    I now use manual lock, and upon awakening the wifi is now fully working.

  • Lost Ability to Connect to WiFi

    Hi Everyone:
    There have been lots of discussions about not being able to connect or losing connection to WiFi routers with very few solutions. Here is my saga, so far:
    Took delivery of an iMac 27 with OSX 10.6.4 in September 2011. Connected it to my home network, 802.11 b/g with WPA. Worked fine for a week then wouldn't connect. Didn't recognize the known network even though that network was in the know networks list and was the only one. Rebooted a couple of times and cycled the router. Started working again.
    Another week passes and the same thing happens but this time couldn't get it to recognize the network. Tried lots of things, some suggested by some of these discussions. No luck until I disabled the WPA protection. Now, it connected.
    Fast forward to last night. Everything was working fine then I decided to try to protect the network again so I enabled WPA. The iMac wouldn't connect. Removed the WPA and still wouldn't connect. Tried more stuff like deleting the known network from the Airport preferences and rebooting. Nothing. Cleared the PRAM. Nothing. The iMac won't connect.
    I have a Macbook Pro, 2009, OSX 10.6.8 that connects to the network with no problems. I have two iPod touches, a 2G and a 4G that connect to the network with no problems. I even have an iMac G3 that has no problems connecting.
    Any ideas?

    To continue the saga. Haven't been able to connect for awhile. Went to the Apple store tonight and had a genius appointment. From my description of the problem he was inclined to believe nothing is wrong with the iMac. Even though the other devices I own connect and the Macbook Pro runs the same version of the operating system, they have different hardware for the 802.11x and so may react differently to the router. I was going to take it to work tomorrow but when I fired it up tonight and turned Airport on, guess what, it connected.
    Earlier in the evening, I had to recycle the router for some unknown reason and its stability during the power on/off cycle is questionable. It sometimes has to be shut off twice to restart, so I am now thinking that our modem/router is a prime suspect. This thinking is in direct opposition to what I have posted earlier.
    The intermittent nature of the problem bugs me though. We'll see.

  • Connecting to port forwarding?

    I have a WRT54G Linksys router and I am wondering what is the default username and password for port forwarding?

    Default username and password for the router when you login to its web interface is just admin for the password and no username.
    Setting up port range forwarding on Linksys wireless-N routers and gateways
    http://homekb.cisco.com/Cisco2/ukp.aspx?vw=1&docid=d9b27a0c1bb9496d8c22d0d55f875ddf_17241.xml&pid=80...

  • Port Forward in Cisco series 800

    Dear Support
    below the configuration of Cisco Series 800 Router that Has VDSL  port of internet , the configuration as below : 
    i add three command
    what is required in order to make port forward
    ip nat inside source static tcp  8000 10.10.10.10 8000 dilar 0
    ip nat inside source static tcp 554  10.10.10.10 554 dilar 0
    ip access list extended 100
    permit ip any any
    what is required to make port forward to the local ip address 10.10.10.10 from outside interface that is VDSL port ?
    ! Last configuration change at 10:47:44 KSA Wed Apr 22 2015 by aamalsup
    version 15.2
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime
    service password-encryption
    hostname AamalNet
    boot-start-marker
    boot-end-marker
    logging buffered 51200 warnings
    enable secret level 2 5 $1$Y4PF$K6TQ5wf0gcHiO5IxvLZba0
    enable secret level 5 5 $1$WZeO$BzTCl0C0e1078CWxExJK0/
    enable secret 5 $1$plq6$P5HVL/tR81cs0GFDrD.0V/
    aaa new-model
    aaa authentication login default local
    aaa authentication login sdm_vpn_xauth_ml_1 local
    aaa authentication login sdm_vpn_xauth_ml_2 local
    aaa authorization exec default local
    aaa authorization network sdm_vpn_group_ml_1 local
    aaa session-id common
    clock timezone KSA 3 0
    crypto pki trustpoint TP-self-signed-1682106276
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-1682106276
     revocation-check none
     rsakeypair TP-self-signed-1682106276
    crypto pki certificate chain TP-self-signed-1682106276
     certificate self-signed 02
      30820250 308201B9 A0030201 02020102 300D0609 2A864886 F70D0101 04050030
      31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
      69666963 6174652D 31363832 31303632 3736301E 170D3032 30333031 30303038
      35315A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
      4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D31 36383231
      30363237 3630819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
      8100C2F3 49897460 71FEB259 7794B7C6 D398958A 2D338F0F C69F0E75 1137B16C
      C261A275 8416DAF6 FC19AA6E 50024019 66CE4DB8 3AFAB6FE CE892B42 86A93490
      97259E47 D740B2F4 9AA2D307 7B676841 2CAAA879 D945A6FD 717B507F 77399332
      1644CEDE 884BF133 ACFBBC80 9869A104 54CC3EEE 9D521378 EC762D86 C3F0ABC9
      CA990203 010001A3 78307630 0F060355 1D130101 FF040530 030101FF 30230603
      551D1104 1C301A82 18417761 6C416D61 6C792E61 77616C6E 65742E6E 65742E73
      61301F06 03551D23 04183016 80149ADD A651C9F9 F8369354 5C904777 090FEB75
      72E0301D 0603551D 0E041604 149ADDA6 51C9F9F8 3693545C 90477709 0FEB7572
      E0300D06 092A8648 86F70D01 01040500 03818100 50ACCA98 1A5FCCAD FC61D703
      A8589B02 AFB8CD47 BD1CC7B0 B095C97F AA0604A8 F8495053 C8A9CBB9 644F5674
      318A7AA0 873250AD 1DE28CE2 BE21ED19 BF212CF7 E2A97CFB FFA62F1E 643CEDFE
      90D02109 719FD4D3 98E6C40B D61CE89C D2426C1E 3CBD9FBE 397F7F7C F1DD279E
      14F8BB2D ABFA784B 6E04274B EDCBFC8F A805E91D
          quit
    ip cef
    no ip dhcp use vrf connected
    ip dhcp excluded-address 10.10.10.1
    ip dhcp excluded-address 10.10.11.1
    ip dhcp pool lan
     import all
     network 10.10.10.0 255.255.255.0
     default-router 10.10.10.1
     dns-server 212.93.192.4 212.93.192.5
     lease 0 2
    ip dhcp pool wireless
     import all
     network 10.10.11.0 255.255.255.0
     default-router 10.10.11.1
     dns-server 212.93.192.4 212.93.192.5
     lease 0 2
    no ip domain lookup
    ip domain name aamal.net.sa
    ip name-server 212.93.192.4
    ip name-server 212.93.192.5
    no ipv6 cef
    cwmp agent
     enable download
     enable
     session retry limit 10
     management server password 7 094D4308151612001D05072F
     management server url http://aamalservice.aamal.net.sa:9090
    license udi pid C887VA-W-E-K9 sn FCZ17459018
    archive
     log config
      hidekeys
    username k privilege 15 password 7 020D
    username admin privilege 15 password 7 14161606050A
    controller VDSL 0
    crypto isakmp policy 1
     encr 3des
     authentication pre-share
     group 2
    crypto isakmp client configuration group aamalnet
     key aamalnet
     dns 212.93.192.4 212.93.192.5
     include-local-lan
     dhcp server 10.10.10.1
     max-users 10
     netmask 255.255.255.0
    crypto isakmp profile sdm-ike-profile-1
       match identity group aamalnet
       client authentication list sdm_vpn_xauth_ml_2
       isakmp authorization list sdm_vpn_group_ml_1
       client configuration address respond
       virtual-template 1
    crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
     mode tunnel
    crypto ipsec profile SDM_Profile1
     set security-association idle-time 60
     set transform-set ESP-3DES-SHA
     set isakmp-profile sdm-ike-profile-1
    bridge irb
    interface ATM0
     no ip address
     no atm ilmi-keepalive
    interface ATM0.1 point-to-point
     pvc 0/35
      pppoe-client dial-pool-number 1
    interface Ethernet0
     no ip address
     shutdown
    interface FastEthernet0
     no ip address
    interface FastEthernet1
     no ip address
    interface FastEthernet2
     no ip address
    interface FastEthernet3
     no ip address
    interface Virtual-Template1 type tunnel
     ip unnumbered Dialer0
     tunnel mode ipsec ipv4
     tunnel protection ipsec profile SDM_Profile1
    interface Wlan-GigabitEthernet0
     description Internal switch interface connecting to the embedded AP
     switchport mode trunk
     no ip address
    interface wlan-ap0
     description Embedded Service module interface to manage the embedded AP
     ip unnumbered Vlan1
    interface Vlan1
     description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$
     ip address 10.10.10.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
     ip tcp adjust-mss 1452
    interface Vlan2
     no ip address
     bridge-group 2
    interface Dialer0
     ip address negotiated
     ip mtu 1452
     ip nat outside
     ip virtual-reassembly in
     encapsulation ppp
     dialer pool 1
     dialer-group 1
     ppp authentication chap callin
     ppp chap hostname [email protected]
     ppp chap password 7 0007145E2E5A05522E1858
     no cdp enable
    interface BVI2
     ip address 10.10.11.1 255.255.255.0
     ip nat inside
     ip virtual-reassembly in
    ip forward-protocol nd
    ip http server
    ip http access-class 23
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip nat inside source list 1 interface Dialer0 overload
    ip route 0.0.0.0 0.0.0.0 Dialer0
    access-list 1 remark SDM_ACL Category=2
    access-list 1 permit 10.10.10.0 0.0.0.255
    access-list 1 permit 10.10.11.0 0.0.0.255
    access-list 23 permit 212.93.196.0 0.0.0.255
    access-list 23 permit 212.93.192.0 0.0.0.255
    access-list 23 permit 212.93.193.0 0.0.0.255
    access-list 23 permit 10.10.10.0 0.0.0.255
    access-list 23 permit 10.10.11.0 0.0.0.255
    dialer-list 1 protocol ip permit
    no cdp run
    snmp-server community private RW
    snmp-server community public RO
    bridge 1 protocol ieee
    bridge 1 route ip
    bridge 2 protocol ieee
    bridge 2 route ip
    privilege interface level 5 encapsulation
    privilege interface level 5 description
    privilege interface level 5 no encapsulation
    privilege interface level 5 no description
    privilege interface level 5 no
    privilege configure level 5 ip route
    privilege configure level 5 interface
    privilege configure level 5 controller
    privilege configure level 5 ip
    privilege exec level 5 copy running-config tftp
    privilege exec level 5 copy running-config
    privilege exec level 5 copy
    privilege exec level 5 write memory
    privilege exec level 5 write
    privilege exec level 5 configure terminal
    privilege exec level 5 configure
    privilege exec level 5 show processes cpu
    privilege exec level 5 show processes
    privilege exec level 2 show running-config
    privilege exec level 5 show configuration
    privilege exec level 2 show
    privilege exec level 5 clear counters
    privilege exec level 5 clear
    banner exec
    CC
    % Password expiration warning.
    Cisco Router and Security Device Manager (SDM) is installed on this device and
    it provides the default username "cisco" for  one-time use. If you have already
    used the username "cisco" to login to the router and your IOS image supports the
    "one-time" user option, then this username has already expired. You will not be
    able to login to the router with this username after you exit this session.
    It is strongly suggested that you create a new username with a privilege level
    of 15 using the following command.
    username <myuser> privilege 15 secret 0 <mypassword>
    Replace <myuser> and <mypassword> with the username and password you want to
    use.
    banner login
    CC
    ********STC AamalNet Service****************************************
    ********Authorize Access Only. For more Support Call 909************
    line con 0
     privilege level 15
     no modem enable
    line aux 0
    line 2
     no activation-character
     no exec
     transport preferred none
     transport input all
     stopbits 1
    line vty 0 4
     access-class 23 in
     privilege level 2
     transport input telnet ssh
    scheduler max-task-time 5000
    scheduler allocate 20000 1000
    end

    Hello,
    Sure.
    What version are you running?
    Regards,

Maybe you are looking for