To work around this, download https://secure.logmein.com/activex/logmein-client-1.0.387-1.tar.gz, and extract to ~/.mozilla/plugins/ then download and install nspluginwrapper from the repos (sudo apt-get install nspluginwrapper).  Nspluginwrapper is a tool to create a layer of compatibility for non-native browser plugins.

You can then use nspluginwrapper by using:

sudo nspluginwrapper -i ~/.mozilla/plugins/libractrl.so

Restart firefox and navigate to the logmein website again and it should work…

The solution was to edit the the /tftpboot/sip.cfg and look for the line that says:

<digitmap dialplan.digitmap=”[2-9]11|0T|011xxx.T|[0-1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxT” dialplan.digitmap.timeOut=”3|3|3|3|3|3″/>

and replace with the correct number of digits for calls in your country…

<digitmap dialplan.digitmap=”[2-9]11|0T|011xxx.T|[0-1][2-9]xxxxxxxxxxx|[2-9]xxxxxxxxxxx|[2-9]xxxT” dialplan.digitmap.timeOut=”3|3|3|3|3|3″/>

You then need to restart the handsets in order for this to work.

Following this I ran evolution from the command line – the output of which was:

e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results)
e-data-server-ui-Message: Key file does not have group ‘Passwords-Exchange’

I checked available keys in my keychain and the correct keys were there – along with appropriate passwords….

The I stumbled across the following bug report:

https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/207723

Where I found this comment from Timothy Alexander:

“Something that worked for me was clearing the “mailbox name” under exchange settings, and reauthenticating on that page. The auth went through fine, and it filled out the mailbox again (exactly the same way) but after a restart of evolution it worked fine.”

I tried removing the mailbox name and clicking authenticate, was greeted with the usual errors, but following a restart of evolution it worked!

http://www.lightbluetouchpaper.org/2007/11/16/google-as-a-password-cracker/

I thought I’d put Cuil to the test, to see whether they can offer the same “service”….given their bold claims about their number of indexed pages

Step 1 – think of a password – for the sake of this test I’ll choose the weak password, gringo

Step 2 – hash the password (if you’re lazy, like me, this can be done here)

Step 3 – Google it!

Step 4 – Cuil it!

1) Ensure the service provider has enabled all services on the device – this is the most common problem for me….

2) Ensure that GPRS is functioning correctly.  The GPRS text at the top right hand sign should be in CAPS

3) Go to Options -> Mobile Network ->Data Services and ensure that Data services are switched on.

4) Go to Advanced Options ->Host Routing Table.  There should be a list of Routes.  select the top route and click “Register Now”

5) Set up an email address at O2email.co.uk

6) Go into the EMail setup wizard on the handset and create a user account.  This is a container for the email address.

7) When all steps are complete, if the handset is still not receiving email, log into the o2email.co.uk website from a PC browser.  Send a new service book.

Hope this helps someone….

http://creativecommons.org/weblog/entry/8267

This is a pretty bold step forward for the music industry…..

I’d struggled getting RPC/HTTPS working for ages using a self -signed certificate, and while it’s still recommended using a purchased certificate, I needed to get a particular user working extremely quickly – within about 4 hours.  Waiting for appropriate DNS to propogate to get the cert approved wasn’t an option so the existing self signed cert I used for OWA was the only option…

NOTE:  THIS SOLUTION INVOLVES EDITING THE REGISTRY ON YOUR SBS SERVER – USE AT YOUR OWN RISK!

First things first, the certificate needed to be installed in the Root Certification Authorities store on the client machine.  Note that adding the cert to the default store WILL NOT work.

Then create split DNS by adding the corresponding external DNS zone to your internal DNS server, and a host record for the SBS server.  Remember, if your external web site is hosted externally you need to ensure that there is an A record that points to the web servers IP address.

Next, a couple of Registry keys needed to be added (I would have never have sussed this if it wasn’t for the resources on Amset!). A reg key needs to be created on the SBS server as follows:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
“NSPI Interface protocol sequences”=hex(7):6e,00,63,00,61,00,63,00,6e,00,5f,00,\ 68,00,74,00,74,00,70,00,3a,00,36,00,30,00,30,00,34,00,00,00,00,00

Copy and paste the above into notepad and save with a .reg extension, then run.  This will create a key that looks like:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters Type REG_MULTI_SZ Name: NSPI Interface protocol sequences Value: ncacn_http:6004

Next on the Exchange server (this will be the same machine if using SBS) a different registry key needs to be created:

NOTE: THIS NEEDS TO BE ON A SINGLE LINE AND EDITED TO SHOW SERVER SETTINGS FOR YOUR SERVER

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy]
“ValidPorts”=”server:100-5000; server:6001-6002; server:6004;server.domain.local:6001-6002; server.domain.local:6004; mail.external.com:6001-6002; mail.external.com:6004;”

Save as a .reg file and run.

Then simply configure Outlook to use RPC over HTTPS and specify the FQDN of the server.  You can test the connection by holding CTRL and right-clicking the Outlook icon, then looking at the Connection Status in the taskbar.  If it is trying to resolve the external FQDN of the server then Outlook is configured correctly. Then just ensure that port 443 on your firewall is forwarded to the SBS server….

….sorted

As an add-on, I’ve installed Gnome-Do, an application that finds other applications based on a few keystokes.  Just press the “windows” key and the space bar and then type part of the name of the app you wish to launch…..

Pure Genius!

To install:

sudo apt-get install gnome-do

Then add it as a session using the string gnome-do-quiet to get it to launch at startup