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
Similar Messages
-
Sql Connection using jquery in HTML
Hello friends.. . Sql Connection using jquery is possible ?
If possible.. .pls tell the procedures and steps...
pls clarify my doubt.. .jQuery has no helper functions for handling SQL.
It has Ajax functions which can be used
to talk to a web service that runs SQL on the server.
Client side JavaScript doesn't have the ability to access raw
sockets, so you can't connect directly to a remote database.
There are various client side databases, including storage,
which can be accessed directly with JavaScript (but jQuery doesn't have anything to interact with them).
Please 'propose as answer' if it helped you, also 'vote helpful' if you like this reply. -
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] -
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 -
SQL Connection using AIR - AS3
Hi guys, I'm currently developing a mobile app that have to connect itself to a MySQL database.
Googoling I found this code:
import flash.filesystem.File;
import flash.data.SQLConnection;
import flash.data.SQLStatement;
import flash.net.Responder;
var connection:SQLConnection;
openDatabase();
function openDatabase():void
var dbFile:File = File.applicationStorageDirectory.resolvePath("mySQL.db");
connection = new SQLConnection();
connection.addEventListener(SQLEvent.OPEN, onOpen);
connection.openAsync(dbFile, SQLMode.CREATE);
function onOpen(SQLEvent):void
var stat:SQLStatement = new SQLStatement();
stat.sqlConnection = connection;
stat.text = "CREATE TABLE IF NOT EXISTS contacts (id INTEGER PRIMARY KEY AUTOINCREMENT, fname TEXT, lname TEXT, phone INTEGER)";
stat.execute(-1, new Responder(selectItems));
function selectItems(SQLEvent):void
trace("Select items!");
But there's a problem!
Adobe Flash CS 5.5's compile gives me this error: "Access to a null or undefined property SQLMode"
Is there anyone that can help me?
Thanks!!!
BrandonSQLConnection and SQLStatement are for using a local SQLite database, not a remote MySQL database. To get data out of a remote database, you need to call a service, which is written in a server-side language such as PHP, .Net, Java, ColdFusion, etc.
If you had a typo and actually meant a local SQLite database, then I can share some resource recommendations that helped me.
AIR SQLite: an optimization conversa by H. Paul Robertson
http://tv.adobe.com/watch/360flex-conference/air-sqlite-an-optimization-conversa-by-h-paul -robertson/
Working with local SQL databases in AIR
http://help.adobe.com/en_US/as3/dev/WS5b3ccc516d4fbf351e63e3d118676a5497-7fb4.html
Documentation
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/data/SQLConnectio n.html -
Running a Select query against multiple sql servers using SSIS script task.
Hi Guys,
I need to fetch data from multiple sql servers using SSIS scirpt task inside a foreach container.
is there anyway i can build dynamic sql connections using ssis variables inside SSIS script task in each loop
Please guide me or refer any blogs so that i will try..
Thanks in advance.Your only options is using .net code, then it will be no different than using a console app in a loop.
using (SqlConnection connection = new SqlConnection(connectionString))
connection.Open();
Console.WriteLine("ServerVersion: {0}", connection.ServerVersion);
Console.WriteLine("State: {0}", connection.State);
and so forth for each connection string
the connection string would come from the ForEach loop
Arthur My Blog -
SQL Connection does not repond?
Hi,
I have opened 25 SQL connection using (System.Data.SqlClient) in my service.When ever data is coming to the application ,it will take one connection and put entry to database(SQL Server 2008 R2).Sometimes the opened connections
are not responding.i have put timeout property is 120 secs,but its not throwing any excepion also.once i restart the service then only ,it will work.How can i solve this issue?
Thanks Regards R.KarthickBelow link may be helpful,
http://msdn.microsoft.com/en-us/library/8xx3tyca(v=vs.110).aspx
Regards, RSingh -
Can connect using sqlplus, cannot using SQL Developer
Hi
I cannot find out why I cannot connect using SQL developer, while sqlplus works fine with the same login information.
*1. TNS ping:*
C:\>TNSPING manila
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 24-GRU-2
010 13:28:38
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
C:\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 10.0.0.171)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = XE)))
OK (370 msec)
*2. sqlplus*
SQL> CONNECT SULU_DEV/<pass>@MANILA
Connected.
*3. sqlplus - by IP*
SQL> CONNECT SULU_DEV/<pass>@10.0.0.171:1521/XE
Connected.
*4. SQL Developer*
Username: SULU_DEV
Connection type: TNS
Network alias: MANILA
Error: I/O Exception: Connection reset
*5. SQL Developer - by IP*
Username: SULU_DEV
Connection type: Basic
Hostname: 10.0.0.171
Port: 1521
SID: xe
Error: I/O Exception: Connection reset
*6. SQL Developer - without username*
Username: <blank>
Connection type: TNS
Network alias: MANILA
Error: ORA-01017: invalid username/password
It seems that I have connection to the server, but from some reason it is disconnected when I'm using SQL Developer, but works fine with sqlplus.
Any ideas on what it might be?
Thank you in advance,
Regards,
MarekThe connection export function it's available in 2.1.1.64, you need to right click on the main Connections node, and it will allow you to export all or part of the current connections, or import from a previously exported file.
As for the highlight statement feature it's available in SQLDeveloper; actually you do not even have to highlight the required statement, as long as you take the habit of ending every statement with a ";", in this case you only need to place the caret inside the statement and SQLDeveloper will automatically highlight it for you (if you want to manually highlight a statement you can still do so without problems).
Finally as a last try to solve your connection problem without having to call for network support you could try to check
Preferences -> Database -> Advanced -> Use OCI/Thick DriverThis will force SQLDeveloper to use your oracle client for connections instead of it's native JDBC based connections (even if you use TNS based connections you will still use JDBC unless you have this checked).
As for other graphical tools for Oracle there are many both free or for a price.
1) In the for price world Toad stands out, i heard of a free option too but I'm not sure of the limitations.
2) For free you can use DBVisualizer which is fairly good (never used it too much thou).
3) Finally there is SQuirreL which is both free and open source but it has fairly basic functionality compared to the two above.
Obviously there are many others, but IMHO few will provide you with the same functions of SQLDeveloper or Toad for Oracle databases -
Can't connect to SQL Database using new login
I can connect to Azure SQL Database using the admin ID created when I set up the Azure account. Now I want to set up a different login that has only regular read/write privileges. I have followed the instructions on several web posts, to create
a login at the server level, then create a user at the database level from the login. When I try to connect, though, the connection fails. I get an error message, and a GUID that I am supposed to supply to MS tech support, except that all I have
is a standard Azure subscription, which does not include tech support.
Here is what I have done so far:
Logging in to the server with the admin account with SQL Mgmt Studio, I go to the master database on my Azure server, and create the login:
CREATE LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
This appears to work (password supplied is a "strong" password), or at least it doesn't show any error response.
Then, connecting to the production database in Azure, I set up a user and set permissions as follow:
CREATE USER clouduser1 FROM LOGIN clouduser@gxw8x04nlb;
EXEC sp_addrolemember 'db_datareader', 'clouduser1'
EXEC sp_addrolemember 'db_datawriter', 'clouduser1'
When I attempt to connect to Azure using the new login, however, I get an error message (from SQL Mgmt Studio as well as from MS Access). I am using the SQL Server Native Client 10.0.
The message is:
Connection failed:
SQLState '28000'
SQL Server Error 18456
[Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'clouduser'.
Connection failed:
SQLState: '01000'
SQL Server Error: 40608
[Microsoft][SQL Server Native Client 10.0][SQL Server]This session has been assigned a tracing ID of
'271851d5-8e94-497c-a332-d9d40682bb7a'. Provide this tracing ID to customer support when you need assistance.
Is there some missing step I need to do, to permit the login to see the database? I have looked for such in the various discussions about connection problems, but have not been able to find such a thing. Or extend more permissions to the new
user? Or specify a default user ID for a given login ? (as they do not have the same names, in the examples I have seen). I tried making the user ID the same as the login (w/o the server name), but that didn't seem to help, either.
I have done numerous web searches, and tried about every variation of login or user ID, password, etc. that I can think of, and all of them encounter the same error. It's got to be something very simple - clearly Azure supports more than one login
per database. But's that's all I have at the moment. That login connects just fine, but others won't, using the same PC, middleware, IP address, etc.
Any help would be much appreciated -
Thanks,
DougOlaf -
I noticed that, but all of the examples I have seen have Users named slightly differently from the Logins. I did try logging in with the Login name instead. No good. I tried making the Login and the User name the same (clouduser). Also
no good - same symptoms.
I think the problem is that the initial creation of the Login needs to be done WITHOUT the server name on the end.
Logged in to the master DB, I tried: Create LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
That didn't give me an error message, but I think it created a LOGIN of 'clouduser@gxw8x04nlb'. When
referenced from the outside world, I would need to specify 'clouduser@gxw8x04nlb@gxw8x04nlb'.
I tried deleting the logins, and then creating the login 'clouduser' in the Master DB. Then in
the application DB, I created User clouduser from LOGIN clouduser, and then assigned a role. That seems to work!
In my connection string, File DSN, etc. I still need to supply the login as 'clouduser@gxw8x04nlb'.
But when I am logged in to the server, and working in the Master DB or the application DB, I just refer to the Login as 'clouduser'.
Seems a little more complicated than it really should be, but at least I now have something that works.
Doug
Doug Hudson -
Please tell how to store jpeg images in SQL Server using NI Database Connectivity Toolset.
http://www.w3schools.com/sql/sql_datatypes.asp
You setup a field as BLOB and store the binary of the picture there. Depending on the database it can be called differently as you can see in the link, in SQL server there's even a Image datatype.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV -
Not Converted : Free-hand SQL connection problem
While converting a Free Hand SQL report from Desktop Intelligence to Web Intelligence report in BI XI 3.1, I am faced with the problem
Not Converted : <REPNAME> - Free-hand SQL connection problem
It is be noted that there are some other Free Hand SQL Reports, that go converted and published without any error. The subject report has two Data Providers; one referring to the Universe and other from the Free Hand SQL tagged to a DB ConnectionAjay,
Some more points that can be of consideration to you to help understand my problems.
The conversion from DeskI to WebI is in the same version BI XI 3.1 and not to BI 4.0 in which Free Hand SQLs is not supported.
I have converted one other Free Hand SQL Report with an error "Partially Converted : <REPNAME2> - Conditional or permanent Hide Header not available in Web Intelligence", for which I had to edit the report in InfoView and un-tick the "Show When Empty" property of the table ( http://www.forumtopics.com/busobj/viewtopic.php?t=197157&view=next&sid=e6840aafa2d1267c66dae164d1dbf9db ). I think the solution mentioned in this link does not meet the purpose as the table is not displayed in the design time after the above untick.
Coming back to our issue, further probing into this aspect I stumbled upon this link meant for RCT for BI 4.0 version
https://csdwportal.dhhs.state.nc.us/downloads/Business%20Objects%20XI%20R4.0%20Docs/SAP%20BusinessObjects%20Report%20Con…
where in Section 3.4.9, there is a mention of the limitation in conversion as under
"Conversion of reports with free-hand SQL or stored procedures is only possible in Connected mode, since the Report Conversion Tool needs to use the secured connection to the database that is saved in the CMS."
I want to how the secured connection to the database in REPNAME2 is different from the subject report REPNAME1 as REPNAME2 got partially converted. The error reported for Subject report is "Free Hand SQL Connection Problem" and not conversion problem which can occur after the connection is established.
I did check the security properties of various FHSQL connections in the CMC and all of them are identical in nature.
Please advise -
How do i connect to sql server using java?
hi ever body
i need to connect to sql server using java
what is the driver i will use?
thanksMicrosoft make a jdbc driver and it is readily available through MSDN. Here is a link http://msdn2.microsoft.com/en-us/data/aa937724.aspx. Whatever jdbc driver you are looking for, Google it, and if it exists you'll find it in 10 seconds.
-
I bought my own laptop (Macbook Pro) and set it up and am using wifi that my parents use on their computer. Everything was working great until I wanted to put my itunes from the desktop to my laptop. I used my Mom's sign on of her apple id and since then when I log on to my laptop it says another computer is using my ip address...what do I do? Thanks!
Hey there Toni D.,
I suggest the troubleshooting outlined in this article here:
Wi-Fi: How to troubleshoot Wi-Fi connectivity
http://support.apple.com/kb/HT4628?viewlocale=en_US
Does the symptom occur with more than one Wi-Fi device?
Wi-Fi issues may be related to the network in question or they may be related to the Wi-Fi computer joining that network. Usually, if other computers or devices (such as the Apple TV or iPhone) are able to get on the Internet without issues, then your Wi-Fi router is probably fine.
If you only have one Wi-Fi device, proceed with this article.
Make sure your software is up-to-date.
Install all software updates available for your Mac.
If you use a third-party Wi-Fi router, check with the manufacturer to confirm that it has the latest firmware installed. If an update is available, follow the manufacturer's instructions for updating the firmware.
To determine if your Apple Wi-Fi base station firmware is up-to-date, see Updating your software.
Check your connections.
Some networking issues may be caused by loose or disconnected cables. Verify that all Ethernet and power cables connected between your modem and your Wi-Fi router are correct. Checking that devices such as your router and modem are on, disconnecting and carefully reconnecting Ethernet cables, and/or replacing damaged Ethernet cables may resolve the issue without any further troubleshooting.
Verify that you are using the recommended settings for your device.See Recommended settings for Wi-Fi routers and access points.
Restart your network devices.Powering your modem or router off for a few seconds and then on again may resolve network issues without any additional troubleshooting. If you have phone service through your ISP, power cycling your modem may interrupt that service. You may need to contact your ISP in order to restore your phone service if your modem is reset or powered off. Ensure that you have alternative means to contact your ISP (such as a cell phone) to avoid unnecessary delays in restoring your Internet or phone service
And if this does not get the network connection going again I would use the troubleshooting from down the bottom in the section labeled Symptom: My Mac does not connect to the Internet.
Take care,
Sterling -
Error while connecting to external SQL table using BCS identity in SharePoint 2010
Hi all,
I am working on SharePoint Foundation 2010. I have a stand alone setup. Now I am trying to connect to a SQL table in another server. I have used SharePoint Designer to connect using BCS. I have selected "BCS Identity" for authenticating with SQL
in the external content type. then I created a list with this external content type.
I get the following error upon opening the external list.
Login failed for user 'INYKGW\sp_farm'.
I am confused. how do I solve this error.
any help is greatly appreciated.
Thanks.Hi letShare ,
Whether the account 'INYKGW\sp_farm' is current user account or a service managed account?
Could you please provide detail error message of ULS log to determine the exact cause of the error.
For SharePoint 2010, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
Also please have a look at the blog :
http://www.wonderlaura.com/Lists/Posts/Post.aspx?ID=82
Best Regards,
Eric
Eric Tao
TechNet Community Support -
When replying to an ad, via email, posted on Craig's List , for example, it attempts to use my old email address I had with IE, then fails to connect with the ad's author. How do I get it to only use my gmail address with Firefox?
== This happened ==
Every time Firefox openedSee https://support.mozilla.com/en-US/kb/Changing+the+e-mail+program+used+by+Firefox
Maybe you are looking for
-
How to manage music from an external hdd on iTunes?
Hello everyone. I will try to keep it simple in order to be easy to understand... I have my entire music on an External Drive: WD MY PASSPORT. I found around here that, if I press OPTION while I move a music folder to itunes, it doesn't copy the musi
-
How to identify Which function modules are used in the planning area?
Hi all, there are couple of function module derviation is used to derive the calendar year, month, fiscal period etc. But how to identify which function module is used in which planning area? I cant find out from the where used list from function mod
-
How do i stream Brawo films to my imac
I have found the following site Brawo.com and it allows me to stream and watch films free of charge on my ipad, this is graet when im out and about but when i tried on my imac at home it doesnt seem to allow me too. I can watch a trailer of some film
-
How avoid "AUD: OS Errors" after server restart
Hi, After restart my windows 2003 i'm receiving the next messages in my Oracle 11g R2 Standard Edition Be one alert.log file: AUD: OS Error = 31 encountered while writing audit record AUD: OS Error = 5 encountered while writing audit record AUD: OS E
-
The Development Team says Welcome!
This forum revolves around the <a href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/java/javaMemoryAnalysis">SAP Memory Analyzer</a>. The Memory Analyzer is a tool to find <b>memory leaks</b> and analyze <b>memory consumption</b> based on Java