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. thanks
Btreksun 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.
Similar Messages
-
I am having a problem connecting to a remote SQL server 2005 instance. The remote server is for a website hosting account of mine. I can connect to the server from computers other than the problem computer just fine. I cannot connect to the server using any software including SQL Server Management Studio Express, Visual Web Developer, or even when trying to use aspnet_regsql.exe on the problem computer. The request to connect to the remote server never seems to leave my computer. When talking to my hosting service, they replied that they did not receive a request to connect to their server from me. I have shut down Windows Firewall as well as my third-party firewall with no change. The error message that I receive is:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
If anyone has any ideas they would be appreciated.There are a couple of changes that need to be made to allow remote connections to the server... and these need to be made on the server. Have a look at this KB Atricle. Also one way to test is to create a simple ODBC Connection and see if you can get through. Also I see it stange that a hosting company is allowing remote connections to the database server, normally they only allow connections through some sort of web interface or one of there own client tools.
-
Trying to use Linked Servers in SQL 2005 to connect to RDB 7
I'm looking for detailed info on how to set up a linked server in SQL 2005 to connect to my Oracle RDB 7 database (running on VMS). I'm able to connect via odbc using VS.Net and Sql Server 2005 Reporting Services. I'm not sure if I need to use the ODP.NET or not. I have created a generic linked server, but it requires me to use the OpenQuery function to access the data, which is not giving me the functionality I'm looking for.
Hi doanpq,
Please download and install OLE DB Provider for Visual FoxPro 9.0, which exposes OLE DB interfaces that you can use to access Visual FoxPro databases and tables from other programming languages and applications. Please see:
http://www.microsoft.com/en-us/download/details.aspx?id=14839
Then, please follow up the following article to create a linked server:
Creating Linked Servers:
http://technet.microsoft.com/en-us/library/ff772782(v=sql.105).aspx
For more information, you can also take a look at the following article, especially Dave K's comment:
http://blog.dbase.integralwebsolutions.co.za/2008/10/accessing-your-dbf-tables-via-linked.html
Elvis Long
TechNet Community Support -
Connect Non-SAP Oracle db (32bit) in sql 2005 (64 bit) using linked server
Hi,
I am connecting Oracle 10g database from SQL 2005 using linked server, in which i get the error
"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
SAP Server with sql 2005 db is in 64 bit server / Windows 2003
Non-SAP Oracle 10g is in 32 bit windows 2003 server.
i have installed Oracle 64 bit client in the SAP Server and also copied the 64 bit version of dboraslib.dll to the DIR_LIBRARY path. I am able to view the oracle tables in the oracle client.
But, when i create the linked server, it gives the above error.
If i install 32 bit version of Oracle client in the SAP Server, i am able to create the linked server in the db level, but, it says "Work Process restarted, session terminated" message in the Z program in SAP.
The same works in the test environment where both are 32 bit servers. problem is when SAP server is in 64 bit and non sap is in 32 bit.
Please suggest.
Thanks and Regards,
Nagu"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
check the workprocess traces for errors (and/or SM21). It seems that the system is "not aware" that an Oracle client is installed.
64bit programs can´t load 32bit libraries/DLLs that´s why the workprocess dumps when you use the 32bit client.
Markus -
Windows authentication for SQL 2005 DB connect
Hi all,
I'm trying to create a DB connect
in the connection parameters when I mention a user name and password who is created as a SQL authentication then it is working fine.
but in my connection parameters if I mention a user name password who have a Windows authentication in the SQL 2005 which we are trying to connect then it gives an error. It is not connecting .
Can you please tell me how can we connect using a windows authentication.
MeySolution to solve the actual issue :
For the SAP system to use standard default NT authentication
Please refer to this link: http://help.sap.com/saphelp_nw04s/helpdata/en/9c/d736b880c34f76b507bac7751a0474/content.htm
1. Database login:
SQL Server login with System Administrator privileges, that is this login should be member of the sysadmin fixed server role on the target SQL Server. If such a login does not exist, you have to create it on the target SQL Server. The SAP multi-connect mechanism allows both integrated security logins and the use of SQL Server authentication. For security reasons, we highly recommend to use integrated security (Windows authentication). If you use Windows security, leave this field empty.
2.  Password / Re-enter password :
If you have decided to use integrated security, leave these fields empty. Otherwise enter the password of the SQL Server login.
The above pointer was used to solve the login issue but we still had issues in getting the schema visible in SAP BW. As the user ID was left blank we were not able to get the schema view for the <blank> user.
Note to be applied to solve the Schema issue :
note 1091929 :  Link
so now you can enter the schema to be used in DS creaton screen. -
Hi there,
Could you let me know me - how do you configure / disable remote logon for SQL 2005. Are <sid> and SAP<SID>DB allowed to logon remotely?
Thank you!
SimHi,
if you want to disable remote login on sql server 2005 do following
-> Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
->On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.
->On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections
if you only allowed local connection then check local connections only. apply
regards,
kaushal -
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 -
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] -
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 -
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,
error: 40 - Could not open a connection to SQL Server)An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hello,
Make sure your SQL Server service is started.
Make sure TCP\IP and names pipes protocol is enabled
Make sure you have made an exception in firewall for SQL Server connection
Make sure SQL Server browser service is enabled
Make sure you connect with correct name hostname\instance name for named instance,MSSQLSERVER for default instance and Hotname\SQLEXPRESS for express edition.
Please make sure you use port no when connecting to SQL server listeing on different port (hostname\instance ,portno)
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
How Crystal report XI connect to SQL 2005(9.0.3073)
hi
i am trying to connect sql server 2005 to create a new report, however, it seems Microsoft OLE DB Provider for SQL server is not working for sql server 2005
please advise which data link i have to use for connecting sql server 2005?
thanksit seems Microsoft OLE DB provide for SQL server is only working for sql 2000 and earlier version, for sql 2005, it should use sql server provide, however, it is not an option in the crystal report?
i don't want to use ODBC to connect sql 2005, any body knows if there is other way to connect sql 2005? -
ODI 10.1.3.4.0 - Topology Manager Connection Error using SQL 2005 SP3
Hello All,
I am using the ODI repository in SQL 2005 SP3. I could create my master repository using the following parameters:
driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
URL:jdbc:microsoft:sqlserver://server_name:1433;SelectMethod=direct;DataBaseName=ODI
I needed to copy to the drivers directory all files of SQL 2000 (msutil.jar, msbase.jar,mssqlserver.jar) and SQL 2005 (sqljdbc.jar). I am using the JRE 1.4.2 and JDBC 2005 1.2 (http://msdn.microsoft.com/en-us/library/ms378422(SQL.90).aspx)
But when I try to connect in Topology Manager to create the work repository appears the following error:
using this driver string: com.microsoft.jdbc.sqlserver.SQLServerDriver
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC] Can't start a cloned connection while in manual transaction mode.
using this driver string: com.microsoft.sqlserver.jdbc.SQLServerDriver
java.sql.SQLException: No suitable driver
Does Somebody know what is happening?
Regards,
Wallace Galvao
Sao Paulo - BrazilHi,
If you plan on using the SQL Server 2005 drivers then you only need the 1.2 sqljdbc.jar file in the drivers directory.
The connection details for SQL Server 2005 should be like the following.
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://<sqls machine>:1433;databaseName=<db name>;integratedSecurity=false
I would try just with just the correct driver in place, remove the others, restart any ODI components and then make sure the connection information is correct like above.
Cheers
John
http://john-goodwin.blogspot.com/ -
Dump while acessing tables in sql 2005 using DB connect
we have a sql 2000 as source system in place and now i created sql 2005 source system with DB connect.
bw version 3.0.
tables naming conventions are according to SAP.
when i click the button to show tables in source system (sql server) , it is throwing a short dump while connecting to data base.
I initially thought tahat something wrong with BW support pack , but my other sql connection is working perfectly fine.
plz help.
error in short dump
Error analysis
<b>Only message types A, E, I, W, S and X are allowed.
There is probably an error in the program
"RSDL_META_UPLOAD ". </b>
<b>MESSAGE_TYPE_UNKNOWN" C
RSDL_META_UPLOAD " or "RSDL_META_UPLOAD "
END-OF-SELECTION</b>"
> points will be awarded for useful inputs..
Message was edited by:
aravind sam
Message was edited by:
aravind samI am having the similar issue. I have DB connect to oracle schema, however, some of the tables I can view and access the data but others are throwing short dumps and following error:
Event with errors RSDL_META_UPLOAD in DataSource
I have applied support Pack 10 for BI. But this problem persist.
Any IDEA.
Thanks in Advance.
Shaukat
Maybe you are looking for
-
Regarding the Site Definition in Sharepoint 2010
Hi Forum, I am working on sharepoint 2010, I created SiteDefinition through visual studio in Sharepoint 2010, after deploy in sitedefinition. I got new features to add in that existing sitedefinition.Can you please tell me how to proceed. I am thinki
-
Hi, I wanted to create a custom webcenter application which is customizable by users at runtime with sandox feature enabled. And i want save all the changes done at runtime by the users as personalization as the changes must not get reflected for the
-
Color in both Bridge CS5 and ACR look yellow.
The color in my images are all yellow. I've seen some posts but so far no answer to the problem. Can anything at all be done to fix this problem. It it very, very frustrating. Because it's so yellow I cant use ACR for anything at all. Please help I
-
Adobe Updater won't respond, won't go away
On my install of Adobe CS4 at work (running WinXP), the Adobe Updater keeps trying to run but it's blank. The buttons will not respond either. Our IT guy has tried disabling them through the start up file for Windows but it keeps coming back. I've se
-
Hi there, concerning: Swing GUI. I like to use the CDE/Motif LnF, but have to customize the color settings in our application. Without changes, the default background is a nasty grey, the frame color is an ugly violett ... Now, I know there is a them