Rv220w pptp remote connection use two ip address
Hello, I am a long time quick vpn user. I recently purchased a new windows 8.1 pro and the quickvpn fails. After many searches It appears this is a know issue and I should look for another way to connect. I choose to use the PPTP option. I set it up and everything it going well. however I have one slight issues when I try to use an ip specific software on my system that has remotely made the vpn pptp connection. I ran the cmd and check the ipconfig and see now that my computer has two ip address one from the air card I am using to connect to the internet 192.168.0.192 and one that the pptp vpn connection assigns 10.0.0.21 my issue is for my ip specific software to work I am forced to register both ip address for the same computer and each license from the vendor is good for one computer one ip address so this is going to double my operating cost. can anyone help.
Please let me know if you need more info I will do my best to gather. Thanks in advance.
I was able to make a quickvpn connection to my rv220w router via a wifi connection. I am unsure of the exact change made and I am now wondering if anyone can review this log and tell me what happened to allow the connection. At first I was very taken back and had to triple check to make sure it was working. Below is today’s router log at 18:00 I was able to make a successful quickvpn connection. Anyone see how? The rest of the morning I was trying repeatedly to make a connection
is this important? "
2014-02-01 19:04:31: [rv220w][IKE] INFO: Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
2000-01-01 00:00:36: [rv220w][IKE] INFO: IKE started
2014-02-01 12:47:49: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "joey01"
2014-02-01 12:47:49: [rv220w][IKE] INFO: Adding IKE configuration with identifier "joey01"
2014-02-01 12:47:59: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[500].
2014-02-01 12:47:59: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>166.155.0.67[500]
2014-02-01 12:47:59: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 12:47:59: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 12:47:59: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 12:47:59: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 12:47:59: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 12:48:00: [rv220w][IKE] INFO: For 166.155.0.67[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 12:48:00: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 12:48:00: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[500]
2014-02-01 12:48:00: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 12:48:00: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 166.155.0.67[4500]
2014-02-01 12:48:00: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:3671b391a56b4bee:52b561ece6e2aa09
2014-02-01 12:48:00: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 12:48:00: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 12:48:00: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 12:48:00: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 12:48:01: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=266310588(0xfdf93bc)
2014-02-01 12:48:01: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3530213431(0xd26ac837)
2014-02-01 12:49:19: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=3671b391a56b4bee:52b561ece6e2aa09.
2014-02-01 12:49:20: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:3671b391a56b4bee:52b561ece6e2aa09
2014-02-01 13:36:02: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3530213431(0xd26ac837)
2014-02-01 13:36:02: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=266310588(0xfdf93bc)
2014-02-01 13:46:50: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[4500].
2014-02-01 13:46:50: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 13:46:50: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
2014-02-01 13:46:50: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 13:46:50: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 13:46:50: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 13:46:50: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 13:46:50: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 13:46:50: [rv220w][IKE] INFO: For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 13:46:50: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 13:46:50: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[4500]
2014-02-01 13:46:50: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 13:46:50: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:1d7d95d359ea4f66:d71a5efcd843af68
2014-02-01 13:46:50: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 13:46:51: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 13:46:51: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 13:46:51: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 13:46:51: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=225127593(0xd6b2ca9)
2014-02-01 13:46:51: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=1534791298(0x5b7b0e82)
2014-02-01 13:48:34: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=1d7d95d359ea4f66:d71a5efcd843af68.
2014-02-01 13:48:35: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:1d7d95d359ea4f66:d71a5efcd843af68
2014-02-01 14:34:01: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "alohavpn"
2014-02-01 14:34:01: [rv220w][IKE] INFO: Adding IKE configuration with identifier "alohavpn"
2014-02-01 14:34:06: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.250/8<->166.142.243.242/30
2014-02-01 14:34:06: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 14:34:06: [rv220w][IKE] INFO: Initiating new phase 1 negotiation: 192.168.0.10[500]<=>166.142.243.242[500]
2014-02-01 14:34:06: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 14:34:06: [rv220w][IKE] INFO: [ident_i1send:180]: XXX: NUMNATTVENDORIDS: 3
2014-02-01 14:34:06: [rv220w][IKE] INFO: [ident_i1send:184]: XXX: setting vendorid: 4
2014-02-01 14:34:06: [rv220w][IKE] INFO: [ident_i1send:184]: XXX: setting vendorid: 8
2014-02-01 14:34:06: [rv220w][IKE] INFO: [ident_i1send:184]: XXX: setting vendorid: 9
2014-02-01 14:34:27: [rv220w][IKE] INFO: accept a request to establish IKE-SA: 166.142.243.242
2014-02-01 14:34:27: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 14:34:37: [rv220w][IKE] ERROR: Phase 2 negotiation failed due to time up waiting for phase1. ESP 166.142.243.242->192.168.0.10
2014-02-01 14:34:52: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=1534791298(0x5b7b0e82)
2014-02-01 14:34:52: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=225127593(0xd6b2ca9)
2014-02-01 14:34:58: [rv220w][IKE] ERROR: Invalid SA protocol type: 0
2014-02-01 14:34:58: [rv220w][IKE] ERROR: Phase 2 negotiation failed due to time up waiting for phase1.
2014-02-01 14:35:06: [rv220w][IKE] ERROR: Phase 1 negotiation failed due to time up for 166.142.243.242[500]. a8c862e86c5d65ea:0000000000000000
2014-02-01 14:35:18: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.250/8<->166.142.243.242/30
2014-02-01 14:35:18: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 14:35:18: [rv220w][IKE] INFO: Initiating new phase 1 negotiation: 192.168.0.10[500]<=>166.142.243.242[500]
2014-02-01 14:35:18: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 14:35:18: [rv220w][IKE] INFO: [ident_i1send:180]: XXX: NUMNATTVENDORIDS: 3
2014-02-01 14:35:18: [rv220w][IKE] INFO: [ident_i1send:184]: XXX: setting vendorid: 4
2014-02-01 14:35:18: [rv220w][IKE] INFO: [ident_i1send:184]: XXX: setting vendorid: 8
2014-02-01 14:35:18: [rv220w][IKE] INFO: [ident_i1send:184]: XXX: setting vendorid: 9
2014-02-01 14:35:29: [rv220w][IKE] INFO: an undead schedule has been deleted: 'isakmp_chkph1there'.
2014-02-01 14:35:29: [rv220w][IKE] INFO: IPSec configuration with identifier "alohavpn" deleted sucessfully
2014-02-01 14:35:29: [rv220w][IKE] WARNING: no phase2 bounded.
2014-02-01 14:35:29: [rv220w][IKE] INFO: Purged ISAKMP-SA with spi=44ad4081d881ca39:0000000000000000.
2014-02-01 14:35:29: [rv220w][IKE] INFO: an undead schedule has been deleted: 'purge_remote'.
2014-02-01 14:35:29: [rv220w][IKE] INFO: an undead schedule has been deleted: 'isakmp_ph1resend'.
2014-02-01 14:35:29: [rv220w][IKE] INFO: IKE configuration with identifier "alohavpn" deleted sucessfully
2014-02-01 14:45:36: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[4500].
2014-02-01 14:45:36: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 14:45:36: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
2014-02-01 14:45:36: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 14:45:36: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 14:45:36: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 14:45:36: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 14:45:36: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 14:45:36: [rv220w][IKE] INFO: For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 14:45:37: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 14:45:37: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[4500]
2014-02-01 14:45:37: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 14:45:37: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:e7ff5eebc74fe18e:26a523a055bdd961
2014-02-01 14:45:37: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 14:45:37: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 14:45:37: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 14:45:37: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 14:45:38: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=233645680(0xded2670)
2014-02-01 14:45:38: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3473253380(0xcf05a404)
2014-02-01 14:47:04: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=e7ff5eebc74fe18e:26a523a055bdd961.
2014-02-01 14:47:05: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:e7ff5eebc74fe18e:26a523a055bdd961
2014-02-01 14:49:00: [rv220w][IKE] ERROR: Could not find configuration for 99.120.21.158[500]
2014-02-01 14:49:01: [rv220w][IKE] ERROR: Could not find configuration for 99.120.21.158[500]
2014-02-01 14:49:03: [rv220w][IKE] ERROR: Could not find configuration for 99.120.21.158[500]
2014-02-01 14:49:07: [rv220w][IKE] ERROR: Could not find configuration for 99.120.21.158[500]
2014-02-01 14:49:42: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "tim000"
2014-02-01 14:49:42: [rv220w][IKE] INFO: Adding IKE configuration with identifier "tim000"
2014-02-01 14:49:44: [rv220w][IKE] INFO: Configuration found for 99.120.21.158[500].
2014-02-01 14:49:44: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.120.21.158[500]
2014-02-01 14:49:44: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 14:49:44: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 14:49:44: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 14:49:44: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 14:49:44: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 14:49:44: [rv220w][IKE] INFO: For 99.120.21.158[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 14:49:44: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 14:49:44: [rv220w][IKE] INFO: NAT-D payload does not match for 99.120.21.158[500]
2014-02-01 14:49:44: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 14:49:44: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 99.120.21.158[4500]
2014-02-01 14:49:44: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:c37856d7496f4bc0:d866a785808f18ff
2014-02-01 14:49:44: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 14:49:45: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
2014-02-01 14:49:45: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
2014-02-01 14:49:45: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 14:49:45: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=201496659(0xc029853)
2014-02-01 14:49:45: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3623586341(0xd7fb8a25)
2014-02-01 14:51:02: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=c37856d7496f4bc0:d866a785808f18ff.
2014-02-01 14:51:03: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:c37856d7496f4bc0:d866a785808f18ff
2014-02-01 15:33:39: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3473253380(0xcf05a404)
2014-02-01 15:33:39: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=233645680(0xded2670)
2014-02-01 15:37:46: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3623586341(0xd7fb8a25)
2014-02-01 15:37:46: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=201496659(0xc029853)
2014-02-01 15:38:35: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 15:38:35: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 15:38:55: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
2014-02-01 15:38:55: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 15:38:55: [rv220w][IKE] INFO: Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
2014-02-01 15:40:28: [rv220w][IKE] INFO: IPSec configuration with identifier "happy00" deleted sucessfully
2014-02-01 15:40:28: [rv220w][IKE] WARNING: no phase1 found for "happy00"
2014-02-01 15:40:28: [rv220w][IKE] INFO: IKE configuration with identifier "happy00" deleted sucessfully
2014-02-01 15:40:28: [rv220w][IKE] ERROR: sainfo identifier not found ("happy00")
2014-02-01 15:40:28: [rv220w][IKE] ERROR: Failed to Delete the IPSec configuration with identifier "happy00"
2014-02-01 15:40:28: [rv220w][IKE] ERROR: remote identifier not found ("")
2014-02-01 15:40:28: [rv220w][IKE] ERROR: Failed to Delete the IKE configuration with identifier ""
2014-02-01 15:40:47: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 15:40:47: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 15:40:55: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
2014-02-01 15:40:55: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 15:40:55: [rv220w][IKE] INFO: Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
2014-02-01 15:44:52: [rv220w][IKE] WARNING: no phase2 found for "joey01"
2014-02-01 15:44:52: [rv220w][IKE] INFO: IPSec configuration with identifier "joey01" deleted sucessfully
2014-02-01 15:44:52: [rv220w][IKE] WARNING: no phase1 found for "joey01"
2014-02-01 15:44:52: [rv220w][IKE] INFO: IKE configuration with identifier "joey01" deleted sucessfully
2014-02-01 15:44:52: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "joey01"
2014-02-01 15:44:52: [rv220w][IKE] INFO: Adding IKE configuration with identifier "joey01"
2014-02-01 15:45:02: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[500].
2014-02-01 15:45:02: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>166.155.0.67[500]
2014-02-01 15:45:02: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 15:45:02: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 15:45:02: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 15:45:02: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 15:45:02: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 15:45:02: [rv220w][IKE] INFO: For 166.155.0.67[500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 15:45:03: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 15:45:03: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[500]
2014-02-01 15:45:03: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 15:45:03: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 166.155.0.67[4500]
2014-02-01 15:45:03: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:26214a2b8fde97de:0f3107405c30ec29
2014-02-01 15:45:03: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 15:45:03: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 15:45:03: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 15:45:03: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 15:45:04: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=171519328(0xa392d60)
2014-02-01 15:45:04: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=995888774(0x3b5c0e86)
2014-02-01 15:46:19: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=26214a2b8fde97de:0f3107405c30ec29.
2014-02-01 15:46:20: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:26214a2b8fde97de:0f3107405c30ec29
2014-02-01 15:47:22: [rv220w][IKE] INFO: IPSec configuration with identifier "happy00" deleted sucessfully
2014-02-01 15:47:22: [rv220w][IKE] WARNING: no phase1 found for "happy00"
2014-02-01 15:47:22: [rv220w][IKE] INFO: IKE configuration with identifier "happy00" deleted sucessfully
2014-02-01 15:47:22: [rv220w][IKE] ERROR: sainfo identifier not found ("happy00")
2014-02-01 15:47:22: [rv220w][IKE] ERROR: Failed to Delete the IPSec configuration with identifier "happy00"
2014-02-01 15:47:22: [rv220w][IKE] ERROR: remote identifier not found ("")
2014-02-01 15:47:22: [rv220w][IKE] ERROR: Failed to Delete the IKE configuration with identifier ""
2014-02-01 15:48:37: [rv220w][IKE] INFO: Configuration found for 99.120.21.158[4500].
2014-02-01 15:48:37: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 15:48:37: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
2014-02-01 15:48:37: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 15:48:37: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 15:48:37: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 15:48:37: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 15:48:37: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 15:48:37: [rv220w][IKE] INFO: For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 15:48:37: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 15:48:37: [rv220w][IKE] INFO: NAT-D payload does not match for 99.120.21.158[4500]
2014-02-01 15:48:37: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 15:48:37: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:95b646cb75adbb50:0ed9f31398ea14aa
2014-02-01 15:48:37: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 15:48:37: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
2014-02-01 15:48:37: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
2014-02-01 15:48:37: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 15:48:38: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=254599107(0xf2cdfc3)
2014-02-01 15:48:38: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2917092721(0xaddf4d71)
2014-02-01 15:50:17: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=95b646cb75adbb50:0ed9f31398ea14aa.
2014-02-01 15:50:18: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:95b646cb75adbb50:0ed9f31398ea14aa
2014-02-01 15:50:23: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 15:50:23: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 15:50:39: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
2014-02-01 15:50:39: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 15:50:39: [rv220w][IKE] INFO: Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
2014-02-01 15:51:12: [rv220w][IKE] INFO: IPSec configuration with identifier "happy00" deleted sucessfully
2014-02-01 15:51:12: [rv220w][IKE] WARNING: no phase1 found for "happy00"
2014-02-01 15:51:12: [rv220w][IKE] INFO: IKE configuration with identifier "happy00" deleted sucessfully
2014-02-01 15:51:12: [rv220w][IKE] ERROR: sainfo identifier not found ("happy00")
2014-02-01 15:51:12: [rv220w][IKE] ERROR: Failed to Delete the IPSec configuration with identifier "happy00"
2014-02-01 15:51:12: [rv220w][IKE] ERROR: remote identifier not found ("")
2014-02-01 15:51:12: [rv220w][IKE] ERROR: Failed to Delete the IKE configuration with identifier ""
2014-02-01 16:33:05: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=995888774(0x3b5c0e86)
2014-02-01 16:33:05: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=171519328(0xa392d60)
2014-02-01 16:36:39: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2917092721(0xaddf4d71)
2014-02-01 16:36:39: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=254599107(0xf2cdfc3)
2014-02-01 16:43:50: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[4500].
2014-02-01 16:43:50: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 16:43:50: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
2014-02-01 16:43:50: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 16:43:50: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 16:43:50: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 16:43:50: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 16:43:50: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 16:43:50: [rv220w][IKE] INFO: For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 16:43:50: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 16:43:50: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[4500]
2014-02-01 16:43:50: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 16:43:50: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:6a803bd2c559ba70:d005a2ba6e84b619
2014-02-01 16:43:50: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 16:43:50: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 16:43:50: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 16:43:50: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 16:43:51: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=98566123(0x5dfffeb)
2014-02-01 16:43:51: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3231695043(0xc09fc0c3)
2014-02-01 16:45:28: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=6a803bd2c559ba70:d005a2ba6e84b619.
2014-02-01 16:45:29: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:6a803bd2c559ba70:d005a2ba6e84b619
2014-02-01 16:47:29: [rv220w][IKE] INFO: Configuration found for 99.120.21.158[4500].
2014-02-01 16:47:29: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 16:47:29: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
2014-02-01 16:47:29: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 16:47:29: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 16:47:29: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 16:47:29: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 16:47:29: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 16:47:29: [rv220w][IKE] INFO: For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 16:47:29: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 16:47:29: [rv220w][IKE] INFO: NAT-D payload does not match for 99.120.21.158[4500]
2014-02-01 16:47:29: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 16:47:29: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:6852c876e1425084:944da52b84937c9a
2014-02-01 16:47:29: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 16:47:29: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
2014-02-01 16:47:29: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
2014-02-01 16:47:30: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 16:47:30: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=103279842(0x627ece2)
2014-02-01 16:47:30: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2492252444(0x948cc11c)
2014-02-01 16:48:47: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=6852c876e1425084:944da52b84937c9a.
2014-02-01 16:48:48: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:6852c876e1425084:944da52b84937c9a
2014-02-01 17:31:52: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=3231695043(0xc09fc0c3)
2014-02-01 17:31:52: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=98566123(0x5dfffeb)
2014-02-01 17:35:31: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2492252444(0x948cc11c)
2014-02-01 17:35:31: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=103279842(0x627ece2)
2014-02-01 17:42:40: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[4500].
2014-02-01 17:42:40: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 17:42:40: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
2014-02-01 17:42:40: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 17:42:40: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 17:42:40: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 17:42:40: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 17:42:40: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 17:42:40: [rv220w][IKE] INFO: For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 17:42:40: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 17:42:40: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[4500]
2014-02-01 17:42:40: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 17:42:41: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:610f4e8b8a701292:1b5b4fac9129d2cc
2014-02-01 17:42:41: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 17:42:41: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 17:42:41: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 17:42:41: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 17:42:41: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=5442197(0x530a95)
2014-02-01 17:42:41: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=281087573(0x10c10e55)
2014-02-01 17:43:58: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=610f4e8b8a701292:1b5b4fac9129d2cc.
2014-02-01 17:43:59: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:610f4e8b8a701292:1b5b4fac9129d2cc
2014-02-01 17:46:24: [rv220w][IKE] INFO: Configuration found for 99.120.21.158[4500].
2014-02-01 17:46:24: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 17:46:24: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
2014-02-01 17:46:24: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 17:46:24: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 17:46:24: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 17:46:24: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 17:46:24: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 17:46:24: [rv220w][IKE] INFO: For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 17:46:24: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 17:46:24: [rv220w][IKE] INFO: NAT-D payload does not match for 99.120.21.158[4500]
2014-02-01 17:46:24: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 17:46:25: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:34fbdc2521b83861:4f04939eefba3853
2014-02-01 17:46:25: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 17:46:25: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
2014-02-01 17:46:25: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
2014-02-01 17:46:25: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 17:46:25: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=232320279(0xdd8ed17)
2014-02-01 17:46:25: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2789259203(0xa640b7c3)
2014-02-01 17:48:02: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=34fbdc2521b83861:4f04939eefba3853.
2014-02-01 17:48:03: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:34fbdc2521b83861:4f04939eefba3853
2014-02-01 18:30:42: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=281087573(0x10c10e55)
2014-02-01 18:30:42: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=5442197(0x530a95)
2014-02-01 18:34:26: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=2789259203(0xa640b7c3)
2014-02-01 18:34:26: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=232320279(0xdd8ed17)
2014-02-01 18:41:21: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[4500].
2014-02-01 18:41:21: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 18:41:21: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
2014-02-01 18:41:21: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 18:41:21: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 18:41:21: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 18:41:21: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 18:41:21: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 18:41:21: [rv220w][IKE] INFO: For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 18:41:21: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 18:41:21: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[4500]
2014-02-01 18:41:21: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 18:41:22: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:11605c3a8435559f:38b8c86ef5bc8173
2014-02-01 18:41:22: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 18:41:22: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 18:41:22: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 18:41:22: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 18:41:22: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=116125724(0x6ebf01c)
2014-02-01 18:41:22: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=712542982(0x2a788b06)
2014-02-01 18:43:05: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=11605c3a8435559f:38b8c86ef5bc8173.
2014-02-01 18:43:06: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:11605c3a8435559f:38b8c86ef5bc8173
2014-02-01 18:45:11: [rv220w][IKE] INFO: Configuration found for 99.120.21.158[4500].
2014-02-01 18:45:11: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 18:45:11: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
2014-02-01 18:45:11: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 18:45:11: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 18:45:11: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 18:45:11: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 18:45:11: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 18:45:11: [rv220w][IKE] INFO: For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 18:45:11: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 18:45:11: [rv220w][IKE] INFO: NAT-D payload does not match for 99.120.21.158[4500]
2014-02-01 18:45:11: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 18:45:11: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:78a21d9a6ff7a028:d143c9317afa091b
2014-02-01 18:45:11: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 18:45:11: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
2014-02-01 18:45:11: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
2014-02-01 18:45:11: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 18:45:12: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=129883376(0x7bddcf0)
2014-02-01 18:45:12: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=654476335(0x2702842f)
2014-02-01 18:46:32: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=78a21d9a6ff7a028:d143c9317afa091b.
2014-02-01 18:46:33: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:78a21d9a6ff7a028:d143c9317afa091b
2014-02-01 19:04:30: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 19:04:30: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 19:04:31: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
2014-02-01 19:04:31: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 19:04:31: [rv220w][IKE] INFO: Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
2014-02-01 19:05:13: [rv220w][IKE] INFO: IPSec configuration with identifier "happy00" deleted sucessfully
2014-02-01 19:05:13: [rv220w][IKE] WARNING: no phase1 found for "happy00"
2014-02-01 19:05:13: [rv220w][IKE] INFO: IKE configuration with identifier "happy00" deleted sucessfully
2014-02-01 19:05:14: [rv220w][IKE] ERROR: sainfo identifier not found ("happy00")
2014-02-01 19:05:14: [rv220w][IKE] ERROR: Failed to Delete the IPSec configuration with identifier "happy00"
2014-02-01 19:05:14: [rv220w][IKE] ERROR: remote identifier not found ("")
2014-02-01 19:05:14: [rv220w][IKE] ERROR: Failed to Delete the IKE configuration with identifier ""
2014-02-01 19:05:53: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 19:05:53: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 19:06:07: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
2014-02-01 19:06:07: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 19:06:07: [rv220w][IKE] INFO: Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
2014-02-01 19:06:27: [rv220w][IKE] INFO: IPSec configuration with identifier "happy00" deleted sucessfully
2014-02-01 19:06:27: [rv220w][IKE] WARNING: no phase1 found for "happy00"
2014-02-01 19:06:27: [rv220w][IKE] INFO: IKE configuration with identifier "happy00" deleted sucessfully
2014-02-01 19:06:27: [rv220w][IKE] ERROR: sainfo identifier not found ("happy00")
2014-02-01 19:06:27: [rv220w][IKE] ERROR: Failed to Delete the IPSec configuration with identifier "happy00"
2014-02-01 19:06:27: [rv220w][IKE] ERROR: remote identifier not found ("")
2014-02-01 19:06:27: [rv220w][IKE] ERROR: Failed to Delete the IKE configuration with identifier ""
2014-02-01 19:09:21: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 19:09:21: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 19:09:33: [rv220w][IKE] INFO: Configuration found for 99.101.94.86[500].
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
2014-02-01 19:09:33: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received Vendor ID: RFC 3947
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:33: [rv220w][IKE] INFO: For 99.101.94.86[500], Selected NAT-T version: RFC 3947
2014-02-01 19:09:33: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 19:09:33: [rv220w][IKE] INFO: NAT-D payload does not match for 99.101.94.86[500]
2014-02-01 19:09:33: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 19:09:34: [rv220w][IKE] INFO: Configuration found for 99.101.94.86[500].
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
2014-02-01 19:09:34: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received Vendor ID: RFC 3947
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:34: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:09:34: [rv220w][IKE] INFO: For 99.101.94.86[500], Selected NAT-T version: RFC 3947
2014-02-01 19:09:34: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 19:09:34: [rv220w][IKE] INFO: NAT-D payload does not match for 99.101.94.86[500]
2014-02-01 19:09:34: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 19:09:34: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 99.101.94.86[4500]
2014-02-01 19:09:34: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:c45d81319a7961c2:df7f2a51e8084be5
2014-02-01 19:09:34: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 19:09:34: [rv220w][IKE] NOTIFY: The packet is retransmitted by 99.101.94.86[500].
2014-02-01 19:09:35: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.101.94.86[0]
2014-02-01 19:09:35: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.0.192/32
2014-02-01 19:09:35: [rv220w][IKE] INFO: Adjusting peer's encmode 3(3)->Tunnel(1)
2014-02-01 19:09:35: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 99.101.94.86[4500]
2014-02-01 19:09:35: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:51bf7e3f5283a021:c319b19d85b0abd0
2014-02-01 19:09:35: [rv220w][IKE] ERROR: wrong state 8.
2014-02-01 19:09:35: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=43713598(0x29b043e)
2014-02-01 19:09:35: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2920045730(0xae0c5ca2)
2014-02-01 19:10:33: [rv220w][IKE] INFO: Configuration found for 99.101.94.86[500].
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
2014-02-01 19:10:33: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received Vendor ID: RFC 3947
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:10:33: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:10:33: [rv220w][IKE] INFO: For 99.101.94.86[500], Selected NAT-T version: RFC 3947
2014-02-01 19:10:33: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=51bf7e3f5283a021:c319b19d85b0abd0.
2014-02-01 19:10:33: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 19:10:33: [rv220w][IKE] INFO: NAT-D payload does not match for 99.101.94.86[500]
2014-02-01 19:10:33: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 19:10:33: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 99.101.94.86[4500]
2014-02-01 19:10:33: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:518570911a48e055:e1b21587fbe64a7d
2014-02-01 19:10:34: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:51bf7e3f5283a021:c319b19d85b0abd0
2014-02-01 19:11:31: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=518570911a48e055:e1b21587fbe64a7d.
2014-02-01 19:11:32: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:518570911a48e055:e1b21587fbe64a7d
2014-02-01 19:29:23: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=712542982(0x2a788b06)
2014-02-01 19:29:23: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=116125724(0x6ebf01c)
2014-02-01 19:33:13: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=654476335(0x2702842f)
2014-02-01 19:33:13: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=129883376(0x7bddcf0)
2014-02-01 19:40:16: [rv220w][IKE] INFO: Configuration found for 166.155.0.67[4500].
2014-02-01 19:40:16: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 19:40:16: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>166.155.0.67[4500]
2014-02-01 19:40:16: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 19:40:16: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 19:40:16: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:40:16: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:40:16: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:40:16: [rv220w][IKE] INFO: For 166.155.0.67[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:40:16: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 19:40:16: [rv220w][IKE] INFO: NAT-D payload matches for 166.155.0.67[4500]
2014-02-01 19:40:16: [rv220w][IKE] INFO: NAT detected: ME
2014-02-01 19:40:16: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-166.155.0.67[4500] with spi:86a51befd7ee8b38:1c072d85c8c7ab2e
2014-02-01 19:40:16: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 19:40:16: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>166.155.0.67[0]
2014-02-01 19:40:16: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.155.0.67/32
2014-02-01 19:40:16: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 19:40:17: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 166.155.0.67->192.168.0.10 with spi=131309239(0x7d39eb7)
2014-02-01 19:40:17: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->166.155.0.67 with spi=656105156(0x271b5ec4)
2014-02-01 19:41:35: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=86a51befd7ee8b38:1c072d85c8c7ab2e.
2014-02-01 19:41:36: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-166.155.0.67[4500] with spi:86a51befd7ee8b38:1c072d85c8c7ab2e
2014-02-01 19:43:57: [rv220w][IKE] INFO: Configuration found for 99.120.21.158[4500].
2014-02-01 19:43:57: [rv220w][IKE] INFO: Ports floated, peer initiatedcommunication on 4500
2014-02-01 19:43:57: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[4500]<=>99.120.21.158[4500]
2014-02-01 19:43:57: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 19:43:57: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 19:43:57: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:43:57: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:43:57: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:43:57: [rv220w][IKE] INFO: For 99.120.21.158[4500], Selected NAT-T version: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:43:57: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[4500]
2014-02-01 19:43:57: [rv220w][IKE] INFO: NAT-D payload does not match for 99.120.21.158[4500]
2014-02-01 19:43:57: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 19:43:57: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.120.21.158[4500] with spi:e1442468d0529bbe:f66c9601351bd3a2
2014-02-01 19:43:57: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 19:43:57: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.120.21.158[0]
2014-02-01 19:43:57: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.1.68/32
2014-02-01 19:43:57: [rv220w][IKE] INFO: Adjusting peer's encmode 61443(61443)->Tunnel(1)
2014-02-01 19:43:58: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.120.21.158->192.168.0.10 with spi=191762664(0xb6e10e8)
2014-02-01 19:43:58: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.120.21.158 with spi=3118196926(0xb9dbe8be)
2014-02-01 19:45:02: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=e1442468d0529bbe:f66c9601351bd3a2.
2014-02-01 19:45:03: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.120.21.158[4500] with spi:e1442468d0529bbe:f66c9601351bd3a2
2014-02-01 19:57:36: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2920045730(0xae0c5ca2)
2014-02-01 19:57:36: [rv220w][IKE] INFO: IPsec-SA expired: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=43713598(0x29b043e)
2014-02-01 19:59:08: [rv220w][IKE] INFO: Configuration found for 99.101.94.86[500].
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
2014-02-01 19:59:08: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received Vendor ID: RFC 3947
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:59:08: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 19:59:08: [rv220w][IKE] INFO: For 99.101.94.86[500], Selected NAT-T version: RFC 3947
2014-02-01 19:59:08: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 19:59:08: [rv220w][IKE] INFO: NAT-D payload does not match for 99.101.94.86[500]
2014-02-01 19:59:08: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 19:59:08: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 99.101.94.86[4500]
2014-02-01 19:59:08: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:5fbfcd9413b4c0f5:76e81b7495bfa7c8
2014-02-01 19:59:08: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
2014-02-01 19:59:08: [rv220w][IKE] INFO: Responding to new phase 2 negotiation: 192.168.0.10[0]<=>99.101.94.86[0]
2014-02-01 19:59:08: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->192.168.0.192/32
2014-02-01 19:59:08: [rv220w][IKE] INFO: Adjusting peer's encmode 3(3)->Tunnel(1)
2014-02-01 19:59:09: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 99.101.94.86->192.168.0.10 with spi=267963700(0xff8cd34)
2014-02-01 19:59:09: [rv220w][IKE] INFO: IPsec-SA established[UDP encap 4500->4500]: ESP/Tunnel 192.168.0.10->99.101.94.86 with spi=2847327220(0xa9b6c3f4)
2014-02-01 20:04:12: [rv220w][IKE] INFO: an undead schedule has been deleted: 'pk_recvupdate'.
2014-02-01 20:04:12: [rv220w][IKE] INFO: Purged IPsec-SA with proto_id=ESP and spi=2847327220(0xa9b6c3f4).
2014-02-01 20:04:12: [rv220w][IKE] INFO: Purged ISAKMP-SA with proto_id=ISAKMP and spi=5fbfcd9413b4c0f5:76e81b7495bfa7c8.
2014-02-01 20:04:13: [rv220w][IKE] WARNING: no phase2 found for "happy00"
2014-02-01 20:04:13: [rv220w][IKE] INFO: IPSec configuration with identifier "happy00" deleted sucessfully
2014-02-01 20:04:13: [rv220w][IKE] INFO: ISAKMP-SA deleted for 192.168.0.10[4500]-99.101.94.86[4500] with spi:5fbfcd9413b4c0f5:76e81b7495bfa7c8
2014-02-01 20:04:13: [rv220w][IKE] WARNING: no phase2 bounded.
2014-02-01 20:04:13: [rv220w][IKE] INFO: Sending Informational Exchange: delete payload[]
2014-02-01 20:04:13: [rv220w][IKE] INFO: Purged IPsec-SA with spi=2920045730(0xae0c5ca2).
2014-02-01 20:04:13: [rv220w][IKE] INFO: Purged IPsec-SA with spi=267963700(0xff8cd34).
2014-02-01 20:04:13: [rv220w][IKE] INFO: Purged IPsec-SA with spi=43713598(0x29b043e).
2014-02-01 20:04:13: [rv220w][IKE] INFO: Purged ISAKMP-SA with spi=c45d81319a7961c2:df7f2a51e8084be5.
2014-02-01 20:04:13: [rv220w][IKE] INFO: an undead schedule has been deleted: 'purge_remote'.
2014-02-01 20:04:13: [rv220w][IKE] INFO: IKE configuration with identifier "happy00" deleted sucessfully
2014-02-01 20:04:13: [rv220w][IKE] ERROR: sainfo identifier not found ("happy00")
2014-02-01 20:04:13: [rv220w][IKE] ERROR: Failed to Delete the IPSec configuration with identifier "happy00"
2014-02-01 20:04:13: [rv220w][IKE] ERROR: remote identifier not found ("")
2014-02-01 20:04:13: [rv220w][IKE] ERROR: Failed to Delete the IKE configuration with identifier ""
2014-02-01 20:06:01: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 20:06:01: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 20:06:07: [rv220w][IKE] INFO: Using IPsec SA configuration: 10.0.0.0/8<->166.142.243.242/32
2014-02-01 20:06:07: [rv220w][IKE] INFO: Configuration found for 166.142.243.242.
2014-02-01 20:06:07: [rv220w][IKE] INFO: Ignoring request for negotiation to 166.142.243.242 as Local is configured as Responder.
2014-02-01 20:07:25: [rv220w][IKE] INFO: IPSec configuration with identifier "happy00" deleted sucessfully
2014-02-01 20:07:25: [rv220w][IKE] WARNING: no phase1 found for "happy00"
2014-02-01 20:07:25: [rv220w][IKE] INFO: IKE configuration with identifier "happy00" deleted sucessfully
2014-02-01 20:07:25: [rv220w][IKE] ERROR: sainfo identifier not found ("happy00")
2014-02-01 20:07:25: [rv220w][IKE] ERROR: Failed to Delete the IPSec configuration with identifier "happy00"
2014-02-01 20:07:25: [rv220w][IKE] ERROR: remote identifier not found ("")
2014-02-01 20:07:25: [rv220w][IKE] ERROR: Failed to Delete the IKE configuration with identifier ""
2014-02-01 20:09:58: [rv220w][IKE] INFO: Adding IPSec configuration with identifier "happy00"
2014-02-01 20:09:58: [rv220w][IKE] INFO: Adding IKE configuration with identifier "happy00"
2014-02-01 20:10:11: [rv220w][IKE] INFO: Configuration found for 99.101.94.86[500].
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received request for new phase 1 negotiation: 192.168.0.10[500]<=>99.101.94.86[500]
2014-02-01 20:10:11: [rv220w][IKE] INFO: Beginning Identity Protection mode.
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received Vendor ID: MS NT5 ISAKMPOAKLEY
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received Vendor ID: RFC 3947
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received Vendor ID: draft-ietf-ipsec-nat-t-ike-02
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 20:10:11: [rv220w][IKE] INFO: Received unknown Vendor ID
2014-02-01 20:10:11: [rv220w][IKE] INFO: For 99.101.94.86[500], Selected NAT-T version: RFC 3947
2014-02-01 20:10:11: [rv220w][IKE] INFO: NAT-D payload does not match for 192.168.0.10[500]
2014-02-01 20:10:11: [rv220w][IKE] INFO: NAT-D payload does not match for 99.101.94.86[500]
2014-02-01 20:10:11: [rv220w][IKE] INFO: NAT detected: ME PEER
2014-02-01 20:10:12: [rv220w][IKE] INFO: Floating ports for NAT-T with peer 99.101.94.86[4500]
2014-02-01 20:10:12: [rv220w][IKE] INFO: ISAKMP-SA established for 192.168.0.10[4500]-99.101.94.86[4500] with spi:1e81ce312812da50:569671b6b2a1ad6a
2014-02-01 20:10:12: [rv220w][IKE] INFO: Sending Informational Exchange: notify payload[INITIAL-CONTACT]
Similar Messages
-
BPF Package Manager won't open in remote connection using Public IP address
I have a problem to open BPF package manager.
Im able to open bpf package manager in my server and to all local bpc users but on the remote connection (vpn/web) they couldn't open the bpf.
Our server uses an private Ip address which is 10.1.25.81 (local LAN) but we also access BPC remotely using an
Public IP address (202.129.238.46 or http://servername.example.com/osft ) using a configuration of IP Forwarding in our router.
example:
(LAN)
User 1 on System 1 - does the BPF work?yes
User 1 on System 2 - does the BPF work?yes
User 2 on System 1 - does the BPF work?yes
User 2 on System 2 - does the BPF work?yes
(WAN/VPN)
User 1 on System 1 - does the BPF work?no
User 1 on System 2 - does the BPF work?no
User 2 on System 1 - does the BPF work?no
User 2 on System 2 - does the BPF work?noWhen you are performing installation of BPC or after if you are looking into Server Manager - Server Option you will see for application server, web server and reporting services server you have two fields where you can specify name for internal and nae Example for application server:
Application Server name: FQDN (or IP)
External Application Name: FQDN (or IP)
Normally we recommedn to use FQDN (Fully qualified DNS name)
because if the DNS entry are set correct then you will be able to connect from internal and also from external without any problem.
The system will provide every time the correct IP.
In my opinion you used IP and the problem it is that internal the external IP is not recognized.
Please verify the configuration and provide more information about the landscape.
Only in this way we will be able to provide you the right sugestions to fix this issue.
Kind Regards
Sorin Radulescu -
Hi, I use two email addresses within one account with gmx.
I created one account with the first email address now. How do I add the second one to this account?
Now it looks like this.
One account was opened with address A.
I receive in this account emails for address A and B.
But I can only write and answer with address A.Hi Rudegar,
Sorry for my late reply.
It s not the amount of accounts I'm struggling with.
When I create now for both email addresses one account, then I receive the same emails two times.
That is not what I want.
Because on gmx the two email addresses have the same inbox and outbox.
E.g. I can login to my gmx account either with email A or B. It doesn't matter.
Now I want to have the same on my ipad.
One account with both email addresses. -
Can I use two gmail addresses via the same Mail account?
Please help! My brain is fried. I have two email addresses: one is a regular gmail one, the other uses my own domain but it's gmail too. I currently have both set up on Mail on my Mac. I receive and send from both. But I really want to have both working through one account (this is mainly to simplify the very clever Sanebox tool on both my Mac and in the Mailbox app on my iPhone).
If I forward my domain email to my regular gmail then I can receive them all in one fell swoop. Which is fine. But can I then continue to send from both accounts? Is this what they mean by an 'alias'? It's really important that I can send from both.
Sanebox suggested this: http://support.apple.com/kb/TA23485. I'm not sure I really understand it and don't want to risk changing my settings yet in case it all goes wrong.
Thank you very much!If you're asking whether you can connect one device to two itunes store accounts, the answer is no.
-
MS SQL 2005 remote connection using sqljdbc
Hi,
I have production line computer with software using java code and firebird database, i also have sqljdbc.jar also in the library.
my software is trying to connect to mssql2005 database in a remote computer and got this error message:
java.lang.classnotfoundexception: com.microsoft.sqlserver.jdbc.SQLServerDriver.
I have no problem when connecting to my local mssql2005 database though. but have problems when trying to make remote connection.
May i know what could seem to be the cause of the problem, is there anything missing ? do i need to instal anything else on the production line computer? currently it does not have mssql2005 instal on the production computer do i need to instal it ? please help. thanksBtreksun wrote:
Hi,
Im using MS SQL 2005 Express edition, I dont find any sqljdbc.jar driver inside the installation,
I dont see any other driver or driver folder in the installation path.
Inside my instalation path C:\Program Files\Microsoft SQL Server: only shows these folders
MSSQL$MSSQL2000
MSSQL.1
80
90
100
"Class path" applies to java. None of the above is java.
I dont know what to set my classpath with?You are running your java in "something". That "something" is an application. That "something" does not have the correct class path. You didn't tell us what it is so we can't help you with it.
I even download sqljdbc.jar and put it inside C:\Program Files\Microsoft SQL Server and set the classpath but doesnt work ?I suggest you google for class path, read several articles about it and try some of the stuff that they talk about. -
SQL connection using "FREE" IP address
we have a server running CF MX (6.1), making SQL requests to
another server on the network.
The strange thing is, when viewing the active connections on
the SQL server, the CF server is listed using
an unassigned IP address on the CF server.
How does CF choose which IP address it uses for outbound
connections,
where multiple IP addresses are assigned to the NIC?From what you say in your post, it almost sounds like you have to change your Network setting to connect with ethernet for you to get a connection.
The Airport Tab in the Network has to correspond with the type of connection you are using.
It must be highlighted and the green dot showing and drag it to the top of the list.
Then when you travel and use Wireless you can change it back to Airport and connect.
Cheers Don -
Remote connection between two macs.
I'm trying to set up a remote connection between my iMac and my MacBook so I can share them over the network. On the MacBook's Terminal I'm entering the following command: "ssh username@hostname" witch is supposed to let me remotely login into my iMac, after a few seconds the command line prompt me with this message: "connect to host 1.2.3.4 port 22: Operation timed out". What am I missing?
This forum is for troubleshooting Apple Remote Desktop, Apple's application for managing networked Macs. You should post your question in the OS X networking forums:
http://discussions.apple.com/forum.jspa?forumID=1222 -
In Mail, is it better to use two email addresses or just one (iCloud)
With iOS5, I have two accounts on my iMac (my regular acct and my iCloud) and it is the same way on my iPad. On my iMac, I have iCloud as the default. I don't quite understand this iCloud thing yet. Should I have both accounts listed on both iMac and iPad, or should I have just one and, if just one, which one should it be?
What is the advantage of iCloud with Mail?Probably not. There will be no appreciable difference in range between those two choices. Each will be limited by the same phenomena, namely, interference from competing wireless networks and the presence of intervening obstructions and building construction.
Extending a wireless network "wirelessly" is always a compromise that generally manifests itself in reduced bandwidth for devices connected to the "extended" base station. If you are not willing to compromise, use a wired connection between the two. That's the way large wireless deployments are accomplished. -
Simple remote connection using Cisco AnyConnect and ISR router
Hi all,
I am just wondering what the easiest and simplest method would be to make remote PCs (running Cisco AnyConnect) establish a VPN IPsec to a Cisco ISR (881/887, 1900s,2900s series). I used to use EasyVPN method (simple and fast to configure and no need for special licences other than crypto licence) but since Cisco VPN Client is no longer supported I had to resort to WebVPN which requires a licence depending on the number of clients to support (SSL licences for 10,20 users and so forth). I've read a bit about FlexVPN but I can't find an easy example to what I want to do. The closest is this one (FlexVPN and Anyconnect IKEv2 Client Configuration Example):
http://www.cisco.com/c/en/us/support/docs/security/flexvpn/115941-flexvpn-ikev2-config-00.html
But that example makes use of RADIUS. Is there a way to make use of local database (users configured on the router) instead of RADIUS?
Basically what I am after is the following
- Remote users install Cisco AnyConnect to establish a VPN connection to HQ
- HQ ISR (880s, 1900s, 2900s) terminates that VPN connections and allows access to local resources (shared drives, applications...).Authentication method would be local database on the router. No need of RADIUS/ACS as this is for very small companies with no IT resources to maintain and configure a RADIUS/ACS server.
I think what I need is this AnyConnect to IOS Headend Over IPsec with IKEv2 and Certificates Configuration Example:
http://www.cisco.com/c/en/us/support/docs/security/flexvpn/115014-flexvpn-guide-cert-00.html
But the example is too highlevel for me to follow, basically I don't know how to generate such certificates and distribute it to remote clients.
Any help as to how to create such certificates or how to configure FlexVPN to just requiring the user to enter usr/pass (using local database not RADIUS nor ACS) would be highly appreciated.
Cheers
AlvaroIf you insist .. try this:
http://www.cisco.com/c/en/us/support/docs/security/flexvpn/116032-flexvpn-aaa-config-example-00.html
http://www.cisco.com/c/en/us/support/docs/security/flexvpn/115907-config-flexvpn-wcca-00.html
http://www.cisco.com/c/en/us/support/docs/security-vpn/ipsec-negotiation-ike-protocols/50282-ios-ca-ios.html -
Remote Connection using Back to my Mac for Time Capsule?
How do I connect to my Time Capsule and connected usb drive/printer now that Back to my Mac for Mobile Me is disabled and iCloud is running Back to my Mac?
More information:
I used to use the Mobile Me's version of Back to my Mac to enable connecting with my time Capsule, but how is this done now that iCloud has taken over Back to my Mac and I have upgraded to Lion.
I have a Feb2011 MBP and a 2010 minimac the macmini is always connected to the time capsule, but I would like to be able to connect directly to the time capsule without having to go through the macmini.
Thank you for your helpIt is possible but I am not sure it is worth the hassle..
Your key issue here is public IP for your network.. if you have a static ip you are fine.. but very few people have this. It also depends on how the TC is setup.. is it the main router for the network or plugged into a modem router which has the role of main router, even if you use the TC as a secondary router.
Without more info..
1. This is easy if you have a static public IP and the TC is the main router and gets the public IP on the wan port.. just go to disk sharing in the airport utility manual setup and check for wan (internet access).
2. If you have a dynamic IP, then you will have to sort out how you are going to find that IP.. the normal method to use dyndns account is not directly applicable because the TC has no client. It is possible to set up dyn dns but you will need to purchase your own domain name.
3. You may find it easier to use standard router and bridge the TC. A standard router can be setup to port forward 548 AFP files service to the TC ip address. You may or maynot be able to access the printer. Certainly would be easier if the printer has IPP services. And is a true network printer.
4. Use vpn.. get a vpn router so you can setup proper vpn endpoints.. then you use VPN service to access your local network.. this is far more secure and will work with dyndns just fine. -
Remote connection using SAProuter and Service Connector
Hello everyone!
What I am trying to do is to connect to an SAP system of a client of ours.
This is what I have found out and what works -
I found out that for such a scenario a SAProuter and the Service Connector somewhow come into play. I worked with the SAProuter and could connect to a test IDES system in our company with the following router string -
/H/<localsystem_where_SAProuter_is_running>/H/<IP_of_IDES>/S/3200
This basically means that I would have to connect my SAProuter with the client's SAProuter and the client router would then pass on my connection to their SAP system like this -
/H/<mySAProuter>/H/<clientSAProuter>/S/<port_client_SAProuter>/W/<client_password_if_specified>
When this connection is established, I can access the client's SAP system through a SAPGui (Windows or Java) from my side using the connection string as specified above.
If this works, why do I need a service connector? What would it's function be?
Another question being - I have been told that a connection can also be established by using a connection from us to SAP and then from SAP to the client's SAP system (this has been suggested by the client). Where does this scenario fit in? If it is indeed possible, what do I need to do to make such a connection work?
I would appreciate it if someone answers who has actually worked on such a situation.
Bye!
SameerThe service connector is used by SAP to automatically open your systems for customer messages; it's not relevant in the scenario you describe.
You can't use SAP's servers as a "stepping stone" to get to another customer's system.... you can directly link the two organizations by allowing the connections through both firewalls to specific saprouters at each end though:
CustA <> saprouter <> firewall <> INTERNET <> firewall <> saprouter <> CustB
It requires coordination between both customers and the use of saprouter strings in the SAPGUI configuration, as you've described.
Rich -
Using two email address in imessage
Hello to all. I am the owner of an iPad.
I am wondering, say if I have two frequently used email addresses, one for work, and one for family and friends. I know that in iMessage, i can add to receive messages from both account.
However, assuming if my caller ID is set to my home email, and a client or co-worker messages me through my work email. When i reply, do they see my home email? or do they see my work email?
Any help would be much appreciated.You can use the same ID for both devices. However, for Messages and FaceTime you need to add another email address in Settings>FaceTime>You can be reached at and Settings>Messages>Send and Receive and uncheck the Apple ID email address.
Elitegate wrote:
Don't use the same Apple ID for both the iPhone and the iPod. Create an own Apple ID for her. Maybe that helps you.
Elitegate, he had Message wsworking before so your suggestion really does not help. -
ORA-28511: lost RPC connection to heterogeneous remote agent using SID=%s
Hi,
Please Help to relsove below issue:
I am using Oracle gateway for Sql Server 11.2 on Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi, on a IBM Power p595 AIX 6.1, SQL Server 2008
When I run a query the first time, it runs perfectly. After some time, I try to run it again and it displays the following error: lost RPC connection
09:44:09 SQL> select count(*) from GSUP_ATRIBUTO@SQLPRD;
COUNT(*)
73
09:48:48 SQL> /
select count(*) from GSUP_ATRIBUTO@SQLPRD
ERROR at line 1:
ORA-02068: following severe error from SQLPRD
ORA-28511: lost RPC connection to heterogeneous remote agent using SID=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.20.8.28)(PORT=1521))(CONNECT_DATA=(SID=SQLPRD)))
09:49:05 SQL> /
COUNT(*)
73
In the gateway trace file we can see:
Oracle Corporation --- FRIDAY MAR 09 2012 09:51:04.140
Heterogeneous Agent Release
11.2.0.1.0
HS Agent received unexpected RPC disconnect
Network error 1003: NCR-01003: NCRS: Read error.
Gateway initSQLPRD.ora file
# This is a customized agent init file that contains the HS parameters
# that are needed for the Database Gateway for Microsoft SQL Server
# HS init parameters
HS_FDS_CONNECT_INFO=[ipSQLSERVER]:port//
# alternate connect format is hostname/serverinstance/databasename
HS_FDS_TRACE_LEVEL=OFF
HS_FDS_RECOVERY_ACCOUNT=RECOVER
HS_FDS_RECOVERY_PWD=RECOVER
Gateway Listener
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME=SQLPRD)
(ORACLE_HOME=/home/oracle/app/oracle/product/10.2.0)
(ENV="LD_LIBRARY_PATH=/home/oracle/app/oracle/product/10.2.0/dg4msql/driver/lib:/home/oracle/app/oracle/product/10.2.0/lib")
(PROGRAM=dg4msql)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = ipGateway) (PORT = 1521))
SQLNET.INBOUND_CONNECT_TIMEOUT=0
My tnsnames.ora file
SQLPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = tcp)(HOST = ipGateway)(PORT = 1521))
(CONNECT_DATA =
(SID = SQLPRD)
(HS = OK)
Alert log message in Oracle Server:
Fri Mar 09 09:48:47 GMT-03:00 2012HS: Lost RPC connection to remote Agent...
HS: ... Agent SID = (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ipGateway)(PORT=1521))(CONNECT_DATA=(SID=SQLPRD))), NCR status = -2147385340
Please helpHi,
It looks like the gateway connection has been closed for some reason and then you have tried to use it again in the same session which gives the ORA-28511.
There is a default gateway timeout but that is 20 minutes, whereas you are seeing problem after about 4 minutes and the listener timeout is set to 0.
Do you have any timeout settings configured in sqlnet.ora ?
Regards,
Mike -
ORA-28511: lost RPC connection to heterogeneous remote agent using
hi,
I have configured dblink between Oracle and sqlserver using "Oracle Database Gateway for SQL Server" method.
i am following the below listed documents
ID 437374.1---How to Setup DG4MSQL (Oracle Database Gateway for MS SQL Server) Release 11 on Linux
http://download.oracle.com/docs/cd/B28359_01/gateways.111/b31042/configsql.htm
All the steps have done and listener, tns also working fine. but, retrieve the data from sqlserver its shows following error.
SQL> select from "demo"@slink;*
select from "demo"@slink*
ERROR at line 1:
ORA-28511: lost RPC connection to heterogeneous remote agent using
SID=ORA-28511: lost RPC connection to heterogeneous remote agent using
SID=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=erpdev01.4iapps.com)(PORT=1511))(C
ONNECT_DATA=(SID=dg4msql)))
ORA-02063: preceding line from SLINK
Process ID: 25158
Session ID: 298 Serial number: 5602
System Details:
Oracle Database :
OS : Enterprise Linux Enterprise Linux Server release 5.2
DB Version : 11.1.0.7.0 Enterprise Edition Release
Oracle Database Gateway for SQL Server version : 11.1.0.6.0
Sqlserver Database :
OS : windows xp
DB Version : sql server 2005 express edition
kindly share your ideas....
Thanks in advanceHi,
To follow up could you please provide the following information -
- the gateway listener.ora
- gateway init<sid>.ora
- gateway tnsnames.ora file
- create database link statement
- a gateway debug trace from the failing select. Add the following to the gateway init<sid>.ora file -
HS_FDS_TRACE_LEVEL=debug
and issue a select from a new SQLPLUS session, then end the session.
Are the gateway and the RDBMS in the same or different ORACLE_HOME directories ? The gateway is at a lower version than the RDBMS so you should apply the 11.1.0.7 patchset to the ORACLE_HOME where the gateway is installed, to bring it to 11.1.0.7.
Regards,
Mike -
ORA-28511: lost RPC connection to heterogeneous remote agent using SID=
I am currently using the HS DG4ODBC on 11.2.0.3 with Linux X86-32bit platform, and I’ve gotten the gateway to work for all DML operations via DBLinks against a TimesTen database.
However, I am getting the following error in red when trying to execute the DBMS_COMPARISON package: ORA-28511: lost RPC connection to heterogeneous remote agent using SID=ORA-28511: lost RPC connection to heterogeneous remote agent using SID=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=timesten-hol)(PORT=1521))(CONNECT_DATA=(SID=hsodbc1)))
An internet search about the error leads me to think that this is a config issue with the cause being that:
Cause: The listener is unable to spawn the HS agent or the agent cannot find the ODBC lib directory.
Action: The PROGRAM line in the listener.ora file is incorrect or not specified. Make sure LD_LIBRARY_PATH includes the $ODBC_HOME/lib directory. If not, set LD_LIBRARY_PATH and restart the listener.
But I’ve revisited the settings and they all look OK, and also the HS agent seems to work fine for all types of DML operations on TimesTen, so I am at a loss of why the above error is occurring with dbms_comparison.compare.
I am also using the datadirect ODBC driver manager.
Thanks,You've already filed a bug for this issue ( DG4ODBC CORE DUMP WHEN USING DBMS_COMPARISON.COMPARE) so please close this thread.
Maybe you are looking for
-
HT5148 how do i take my edited video from final cut pro and save it to my hard drive
how do i take it from the program and save it as a .mp4
-
How can i backup itunes my library?
I don't use "itunes music" folder,my musics are stored in several folders of two disks,i add the folders separatedly, i want to use itunes to manage all the music i've added,and create many playlists in itunes,add many information related to the song
-
Program with update capabilities
I'm in the analysis stages of developing a system and i decided i want users to have an update function to patch an bugs that may arise in the final version. Everything i have ever made is one big jar file but i dont want people to have to download t
-
HELP SYNC is Not working properly, very frustrated
I have a first gen I pod touch. I just uninstalled Itunes 10.5.2.11 and installed 10.5.3.3 Untill just 3 days ago, everything worked fine. Then I tried to create a play list for some videos and found out I could not do so. Then I found out some of my
-
Can an iPod touch get a virus ? I thank my ipod got hacked but all my music and apps I have got from iTunes