There is no information on the error ANYWHERE! *sigh*

Some people might find this funny, but I finally found an Authentication Monitor in the RSA Security Console, the whole thing is quite easy once you get your head around everything

After starting the Real-Time Authentication Monitor It logged the following error..

Now at this point in time, I have not setup any node secret, the ACE Admin guide explains the following

Best Practices for Automatic Delivery
If you use Automatic Delivery, which is the default setting, the Authentication
Manager automatically creates and sends the node secret to the Agent Host in
response to the first successful authentication on the Agent Host. The transmission
containing the node secret is encrypted with a key derived from the user’s passcode in
combination with other information.
• Windows Agents with a version of 4.4.0 or later store the node secret file in the
system registry.
• Windows legacy Agents (other than 4.4.0) store the node secret file in the
%SYSTEMROOT%\system32 directory.
• All UNIX Agents store the node secret file in the in the ACEDATA directory.
The default name of the node secret file is securid.
In the case of Automatic Delivery, capture of the node secret is possible if you are not
careful to control the circumstances in which the first authentication on each Agent
Host occurs.

So, with that in mind, I did the following..

I went back and tested the authentication, and BAM, it now works. “Authentication method success”

You will notice that it’s now auto generated a new secureid file It’s probably better that you create a new Node Secret file for each Agent, however i’m just in the testing phase right now, apart from a crap interface and confusing setup process, it handles it’s intended job very well. kudos to RSA.

To resolve this slightly unwanted issue… do the following.

Maybe make a backup eh

Remove the RPM database.

make the rpm rebuild the database (Could take a little while todo)

Now try and run you up2date command again

Note: Before starting this, please disable your current proprietary drivers (if in use) from ‘Hardware Drivers’ in the system menu

Card = ATI Radeon

Drivers = ati-driver-installer-9-4-x86.x86_64.run download from http://ati.amd.com/support/driver.HTML

Once download, open a terminal alt+F2 type in gnome-terminal

cd to the location downloaded, firefox default is the desktop.

cd ~/Desktop
sudo sh ./ati-driver-installer-9-4-x86.x86_64.run

This will run you through the setup, follow the prompts on the screen.

Here is the trick to get dual x sessions working correctly from the command line with little fuss.

sudo aticonfig –initial=dual-head –screen-layout=right

Change -screen-layout=right to the position of your second screen. e.g -screen-layout=left

network-manager-pptp

terminal cmd:  sudo apt-get install network-manager-pptp

Once the package is installed do the following:

Note: Do not enter the domain you are connecting to, in the username field, enter it like the following domain\username

network-manager does not contain any options to refuse eap, this will need to be done via the command line or gconf-editor

I have provided both options below as chrunchbang linux EEE PC release, does not contain networking in gconf-editor.

1. open up a terminal window, type is sudo gconf-editor expand  system expand networking expand Connections expand either folder, 1,2,3,4 then VPN folder 3 contained my vpn connection settings.

2. right click, create a new key

3. Name: refuse-eap -> Type: String -> Value: Yes

if Networking folder is available in gconf you should now be able to connect to the PPTP VPN without any troubles.

However, if the folder in gconf is not there, please follow the steps below.

1. Open a terminal window.
2. cd ~/.gconf/system/networking/connections/
3. ls -la

output : 1 2 3 4 5 6 %gconf.xml

The folder above represent different connections, you will need to find the connection with the VPN folder, mine is 3, so I would enter the following.

cd 3/vpn/

4. check the  full current working director, mine is /home/username/.gconf/system/networking/connections/3/vpn this can be found by issuing the command pwd
5.  issue the command: nano %gconf.xml
6. The XML file contains specific values for the VPN connection, add the refuse-eap option in bold below and save the file, more information on using nano can be found on google.com

<!–[if gte mso 9]> Normal 0 false false false EN-US ZH-TW X-NONE MicrosoftInternetExplorer4 <![endif]–><!–[if gte mso 9]> <![endif]–>

<?xml version=”1.0″?>
<gconf>
<entry name=”require-mppe” mtime=”1238198504″ type=”string”>
<stringvalue>yes</stringvalue>
</entry>
<entry name=”refuse-eap” mtime=”1238198504″ type=”string”>
<stringvalue>yes</stringvalue>
</entry>
<entry name=”user” mtime=”1238198504″ type=”string”>
<stringvalue>intabill\shayne</stringvalue>
</entry>
<entry name=”gateway” mtime=”1238198504″ type=”string”>
<stringvalue>220.157.75.66</stringvalue>
</entry>
<entry name=”service-type” mtime=”1238198504″ type=”string”>
<stringvalue>org.freedesktop.NetworkManager.pptp</stringvalue>
</entry>
</gconf>

7. restart networking, command: sudo /etc/init.d/networking restart

Reconnect to your Local Area Network / Mobile broadband and you should now be able to connect to your VPN