What does your Generated Errors Log File SAy?

Jackol · 04-30-2003, 05:51 AM

To those that are suffering from this frustrating 'bug', have you looked at the error log created when the games crashes? If you don't know where it is, right click on My Computer, then click on Manage. Then click on the cross next to Event Timer, then click on Application, there you will find the 'Error Log' created by your crash, note what time OOTP crashed so that you know you have the right log.

Mine has this,

Event Type: Information
Event Source: Oakley
Event Category: None
Event ID: 542
Date: 23/04/2003
Time: 08:17:51
User: N/A
Computer: COMPUTER
Description:
The IP Security policy for ISAKMP/Oakley specified an encryption algorithm that is invalid due to export cryptography restrictions. All 3DES encryption used by ISAKMP/Oakley is weakened to standard DES encyption. Generally, this is benign. ISAKMP/Oakley will still be able to negotiate IP security parameters, and protect that negotiation with DES encryption. This should only be of concern if you demand that the ISAKMP/Oakley negotiation be protected with 3DES encryption. If this is the case, please contact your network administrator.

Does yours say the same? Or does it make any sense to Steve and the lads at .400?

04-30-2003, 05:51 AM	#1
Jackol Minors (Single A) Join Date: Mar 2003 Location: Devon, England Posts: 79	What does your Generated Errors Log File SAy? To those that are suffering from this frustrating 'bug', have you looked at the error log created when the games crashes? If you don't know where it is, right click on My Computer, then click on Manage. Then click on the cross next to Event Timer, then click on Application, there you will find the 'Error Log' created by your crash, note what time OOTP crashed so that you know you have the right log. Mine has this, Event Type: Information Event Source: Oakley Event Category: None Event ID: 542 Date: 23/04/2003 Time: 08:17:51 User: N/A Computer: COMPUTER Description: The IP Security policy for ISAKMP/Oakley specified an encryption algorithm that is invalid due to export cryptography restrictions. All 3DES encryption used by ISAKMP/Oakley is weakened to standard DES encyption. Generally, this is benign. ISAKMP/Oakley will still be able to negotiate IP security parameters, and protect that negotiation with DES encryption. This should only be of concern if you demand that the ISAKMP/Oakley negotiation be protected with 3DES encryption. If this is the case, please contact your network administrator. Does yours say the same? Or does it make any sense to Steve and the lads at .400?