Sometimes you come into the situation where you cannot root the device, eg. in a corporate environment or if you just don’t want to crack a new device just to make the funambol client working, like me for now.

I’ve got a new Motorola Xoom and needed funambol to sync my contacts and calendar entries.

After asking Mr. Google there are only 2 ways till Android 4.x is ready:

• Using http without ssl

• Using ssl and recode the funambol client to accept all cert’s

I decided to use the 2nd solution – this also refreshes my java a little bit :-)

Of course i want to share everything with you – if you’re too lazy to read all the stuff you can point your Android client here to install my compiled Funambol 10.0.8 client without the certificate check:

funambol-android-client-10.0.8-devBioS.apk

Please take special care that you use the correct version numbers mentioned, e.g don’t accidently use the JDK 1.7 like me the first time, it will fail ;)

This readme has perfectly everything that you need to setup a fully working android development environment:

Funambol Android ReadMe.txt

I used the Android SDK 2.1 API v.7 (selected in the Android SDK Manager) and the SVN source from here: https://android-client.forge.funambol.org/svn/android-client/tags/10.0.8

Login with user guest without a password when asked.
Follow all the steps in the ReadMe, i changed to following to the get the client to compile:

Note that i installed the android sdk and javacc to C:\Android\…

Change the build.xml around line 10, replace

<property file=”${user.home}/funambol/build/android/build.properties”/>

with

<property file=”${basedir}/build.properties”/>

around line 54, replace

<property name=”android-tools-platform” value=”${sdk-folder-platform}/tools”/>

with

<property name=”android-tools-platform” value=”${sdk-folder}/platform-tools”/>

Copy the build.properties.example and set the following variables, according to your path, be careful with the forward slashes even for windows:

sdk-folder=C:/Android/android-sdk
android.sdk.version=7
javacchome=C:/Android/javacc-4.0

This should allow you to run “ant” as stated in the ReadMe.txt and successfully compile a debug version, test to your liking with “ant install” if it is working.

Now on to the changes that i did, kudos to transdroid.org for writing the 2 Fake classes:

Add the following files in <funambol source>\externals\java-sdk\common\src\main\java-se-android\com\funambol\platform (take care, CaSe SeNsItIvE!)

FakeSocketFactory.java

FakeTrustManager.java

Change HttpConnectionAdapter.java (same path …. platform) around line 227:

schemeRegistry.register(new Scheme(“https”, SSLSocketFactory.getSocketFactory(), 443));

with

schemeRegistry.register(new Scheme(“https”,new FakeSocketFactory(), 443));

Again run ant and ant install and test if the funambol client works without certificate problems.

Now we need to create a release version that is signed, i used a tutorial from here:
http://developer.android.com/guide/publishing/app-signing.html

After creating a keystore, change the build.properties again,

add

keystore.file=C:/Path/To/Your/Keystore-release-key.keystore
keystore.alias=youralias
keystore.password=Password – changeme ;)

Run “ant release” aaaaaand

Now you have an fully working new funambol client without the certificate check but still with SSL encryption!

Have Phun ^^

How to get some more root certificates on an android phone where you have root acces (or, at least, you can start & use root explorer).

Some background info:
I use a funabol community server to keep my phone’s and outlook’s in sync and recently my colleague sven did a great job converting my HTC HD2 with winmobile to Android 2.x (kudo’s to him! thanks!).

Update on 2011-12-27: I changed the client to allow self-signed certificates: here

The challenge is that if you use funabol with self signed ssl certificates you need to get those recognized by android which is a really complicated task if you don’t know how.  But here we go:

What you need before (and what i don’t describe):

• a rooted phone + root explorer. You NEED to be able to write to /etc/security/ in “RW” mode.
• a working funambol installation with ssl configured (see here: http://wiki.ow2.org/sync4j/Wiki.jsp?page=HowtouseHttps)

Our steps include:

1. Export the certificate out of the funambol java keystore
2. Get the cacert.bks from the android device
3. modify the cacerts.bks of android
4. reboot and finished

Step 1 – Export the funambol certificate

• Execute  “%JAVA_HOME%\bin\keytool -export -alias tomcat -file myroot.cer”  (in-detail like here)
• copy the myroot.cer to the SD-Card of the android device (or download to another computer)

Step 2

• insert the SD-Card to the android device, startup root explorer and navigate to /etc/security/
• copy the file cacert.bks
• navigate to /sd-card and paste the file
• insert to another computer
• Go and execute the Portecle Keytool and open the cacerts.bks from your SD-Card
• When promtes for a password, just hit enter
• go to Tools -> Import Key Pair   and select your myroot.cer, give it any name you want
• save the cacerts.bks
• re-insert the SD-Card to android device
• open up root explorer, head to /sd-card, copy, paste to /etc/security/
• make sure root explorer show “mounted as r/w” in the header of the program.
• set permissions of the newly copied cacert.bks to rw-r–r– (owner,group,other: read     owner:write)

Step 3

• double check if the permissions of cacerts.bks are set correctly to rw-r–r–
• restart the phone
• funambol sync should now complete.

Have phun to be in sync!

P.S. Keep in touch! the next xbee’s blogpost’s are half-way written, but i really don’t have time ATM… sry

In this case i (am forced to) use Internet Explorer to open up several intranet pages that allowed me to do my administration work.

The problem sums like this:

• Google, and everything else on “the internet” works seemless
• opening something internal just hang up IE8 for a couple of minutes and then just stop loading without an error
• Same in FireFox with IETab installed
• same in IE 7 + IE 8 64 bit and 32 bit

The solution is as easy as stupid:

In “Internet Options”  -> “Security” the “Local Intranet” is set up with disabled “Protected Mode”.
Enabling it fixed the Problem instantly for IE8, IE7 and Firefox with IETab.

It is in my nature to do crazy things, so i thought it would be really cool to have a notification Jabber Message to my Phone when someone put some letters for me in my letterbox. Here it is ;)

01-08-2010 Update:
The FTDI Chip gives me A fscking LOT PAIN more to come in the next Post. DO NOT USE IT :)

This is my Setup:

• XBee “Coordinator” API Mode connected through a FTDI USB Chip to a linux box
• XBee “End Device” Interfaced with an Atmel ATTiny13v power by two 1.5v AA Batteries
• Perl XBee Module API.pm from Thomas Jager
• Jabber Perl Modules to enable sending messages
• Siemens S685IP DECT Phone that can recieve Jabber messages

Before you read further you should note that i flashed the ZIGBEE firmware (XB24-ZB) API on my XBee’s because i don’t want to miss the mesh feature.

This Setup now runs with 2x Alkaline Batterys in the End-Device for 4 weeks now, and is still running!

– This setup is not the best-power saving setup –

I wanted my XBee to use only PIN HIBERNATE as Sleep-Mode and activate by the ATTiny.
This didn’t always work, maybe i will change the Setup later to use PIN HIBERNATE together with CTS Line to determine when we are “Clear to Send”…

Coordinator:

The coordinator is the middle of my Network. To the Coordinator End-Devices and Routers can connect.
There can be always only one coordinator in a Network.
My coordinator is interfaced with an FTDI Chip for easy connection to a USB enabled Computer.

The FTDI i used is an FT232BL and needs some external components to work, including a 6Mhz XTAL, see the schematics for more information.

Coordinator config (X-CTU):
-Networking-
ID: 001
SC: 1
-Addressing-
DH: 0
DL: 0
NI: COORDINATOR
-Serial Interfacing-
D7: 0
AP: 1
-Sleep Mode-
SM: 5
ST: 1338
-IO Settings-
D1: 3
P0: 0
- I/O Sampling-
IC: 2
V+: FFFF

Optionally you can add encryption by i don’t post my Settings here :)

Schematics:

End-Device:

The end-device is physically stored outside, power-driven by 2x 1.5V AA Batteries, and also connected to an ATTiny.
The ATTiny is not really required but i can control the behaviour of the XBee better.

In fact the ATTiny recognizes the letterbox-opening with an switch and does
1. recover the XBee from sleep by switching SLEEP_RQ on the XBee
2. switching the DIO1 line of the XBee to make it send a digital sample to the coordinator.

End-Device Config (X-CTU):
-Networking-
ID: 001
SC: 1
-Addressing-
DH: 0
DL: 0
NI: LETTERBOX
-Serial Interfacing-
AP: 1
AO: 1

Schematics:

ATTiny Code:
- please note i used BASCOM here, feel free to translate to ASM or avr-c -

$regfile = “attiny13.dat”
$crystal = 1200000

Config Portb.3 = Output
Config Portb.4 = Output
Config Portb.1 = Input
Enable Int0
Config Int0 = Low Level

Enable Interrupts

On Int0 Goon

‘high = Xbee Sleep
Portb.3 = 1
‘high = no current draw
Portb.4 = 1

Do
   NOP
   Powerdown
Loop

End
‘Label we jump to when the Opener is open ;)
Goon:
Disable Int0

‘Letterbox opened, go ahead
‘Activate XBEE
Portb.3 = 0

‘Push Sample-Line Low
Portb.4 = 0

Wait 10

‘Waitms 100
‘Send Sample
Portb.4 = 1

Wait 1
‘Xbee Shutdown
Portb.3 = 1

‘If someone put a Press in and the Opener Stays open
‘we don’t want to get a message every 10 seconds :)
Do
   Wait 1
Loop Until Pinb.1 = 1

Enable Int0

Return
Return

Xbee2Jabber on the Linux Host

As written before the Coordinator is connected to this host and is running some flavor of linux.
I used a Pre-written Perl Module that i extended to accept the XBee Explicit RX framing.

Please note i just extended the Library that i can get the sampling things out of the different Frame not to use anyting other.
If you want more please extend it on your own.

Get the Code here: http://www.divshare.com/download/11390948-788

Please note that Thomas Jager wrote the whole library and i just changed it.
Have a look here to get his original code: http://jager.no/projects/xbee

Have Phun, maybe the next time i will hook up my toilet to the internet ^^

This is a modified Atmel circuit that claims: “Get altered states of consciousness with this microcontroller-driven sound and light device.” by Mitch Altman.

I really enjoyed listening to the Videos and wanted to try it myself, just because it looks so funny to sit there with brainlooping  glasses in your face :)

So i decided to rebuild the whole Project but without the extra led’s that were original and without the Serial Connector because i have a Parallel ISP Interface for the Atmel Microcontrollers.

Download the firmware and instructions here:
http://www.tvbgone.com/cfe_mfaire.php
(Scroll to “Project: Make your own Brain Machine (from MAKE Magazine #10)”)

I used these Schematics without all the Serial Stuff:

This device really rocks you into some deep trance state when you want it :))

All credits go to Mitch Altman.

First i have to tell the terminology:
“Coordinator” – is the Main Boss of the Network, who coordinates everything – and let routers and endpoints connect
“Router” – is a endpoint but can route packets and other endpoints can connect to it.
“End Device” – is a endpoint but noone can conenct to it – it is designed to save energy and run from batteries.

Mesh Networking is really fantastic because you can have a coordinator (“middle”) which is connected to routers and end devices, and is “self-healing” this means if a router is powered off, packets get automatically routed through another reachable router – so packets can arrive to their destination.
If a Enddevice don’t have a connection to a router or the coordinator, put a router in between and it will connect seamless without configuring routing or anything manually.

More about the theory you can find in the references section at the end of my Post.

Okay, first a Picture of my actual “Setup” then the painful story :)

First of all i wanted to see if i can interface with the XBEE’s, so i took a MAX232 5v serial transciver out of my inventory and connected Tx,GND to the xbee.
Rx i connected with with a voltage divider (german: Spannungsteiler) because it came in with 5v and the Xbee only like 3,3v.

Looked everything well, started X-CTU (xbee config software), got a reply and can change values in the configurtion.

GREAT i thought, while reading the documentation i see i need to flash the firmware of one Xbee to get a Coordinator so i can connect the other Xbee to it.

So readed so done, selected “ZNet 2.5 Coordinator AT” in X-CTU, and clicked WRITE.

X-CTU is giving me the following output:

“Entering command mode…
No response from Modem…
“

Damn i thought!

The Xbee looks now damaged as i cannot connect to it anymore – resetting power helped me :)

Anything gone wrong, i readed the documentation again and saw that i need to connect RTS and DTE.

Tried again, don’t work, interchanging cables, don’t work.
I tried interchanging the cables in all possible ways for about 8 fscking hours but nothing helped me.

I can connect to the xbee and change values but i don’t get an other firmware on it.

For this day i was so angry that i gone to bed :o) I thought, new day new chance…

So new day in the morning first i installed an free Serial Sniffer so i can see what’s going on.
Communication is fine before it tries to flash then it invokes a command to flash and it looks like the chip is responsing binary bullshit.

I readed the documentation again and saw that i can enter the bootloader manually by Setting DTE, DIN (serial break) to low and RTS to high.
Tried that and i can enter the bootloader (you see this monitoring the CTS signal, if off it is in bootloader mode)

HAH! The same binary bullshit!

Now i have two possibilities:
- the Bootloader speaks binary bullshit  (against the documentation which says it should respond with “BL >”) or
- there is some problem with the communication

 I see the bootloader only works at 115200bps – that gave me finally the trick.

The 5v Max232 with the connected voltage divider seems to get the high-low and low-high transition not correct at 115200 baud – 9600, 19200 etc no problem, but 115200 is too fast for a voltage divider – at least mine.
I found a ADM2032 in my inventory after long search and hooked that up to the Xbee.

Immediately it flashed the Xbee without ANY problems!
Damn, whole Saturday for such an easy problem gone :(

After i solved this issue i had to fight with the Xbee’s as they didn’t associate.

Final solution was that i flashed the ZIGBEE firmware which looks to me more robust and also is recommended by Digi and now everything looks like a charm. ;)))

Have fun, and update your Xbees to the latest ZIGBEE firmware as described here: ZNet 2.5 to ZB Migration Instructions

More on the Xbee’s to come… ;)

I thought so!

Crawling the Internet looks promising and shows two different ways how to get an bootdisc on your USB thumbdrive:

• Booting a bootdisc as ISO stored on the drive (which is not compatible to most bootdisc’s)
• Booting abootdisc ISO extracted to a extra Partition on the USB-Drive (which is more compatible)

Remember: both ways are possible on a single Stick, so you can have ISO’s there AND extra partitions with the contents of the original ISO.

The Main problem having an ISO booted is that most Systems cannot access their system files after initial booting because they don’t use INT13 calls after booting the initial “bootstrap” system – DOS based bootdiscs should work always…

This is a very good quote from boot-land:

An operating system has basically two modes (exception made for DOS, see later) “real mode” and “protected mode”.
DOS has ONLY “real mode” i.e. “trusts” the info the BIOS gives it, and Windows 3.x/9x/Me though having a “protected mode” still trust the BIOS.
Windows NT based systems starts in “real mode”, trusting the info the BIOS gives it, then switches to “protected” mode, when the hardware is re-scanned and “protected mode” drivers load.
Linux does more or less the same, but not exactly.

…..

The main problem is that once the kernel is booted the grub4dos mapped iso isn’t visible for the linux kernel (doesn’t use INT13 BIOS calls to get data from a device), so SystemRescueCD can’t find the other files it needs.

However to get round this problem we can create an extra partition for the System – as it scans all partitions to find it’s boot files – so the boot files are found in one of those partitions.

I have the following Systems on my Multi-Boot USB Thumbdrive:

• Backtrack 3 Final USB (extra partition)
• Backtrack 4 (extra Partition)
• Hiren’s boot-cd (ISO)
• Ophcrack XP LiveCD (ISO)

Really cool is that you can do much more than only booting this or that System stored on the Thumbdrive, one can do also this:

• Booting ISO’s
• Booting partitions on the Thumbdrive
• Booting Floppy disks
• Find Windows (98/XP/Vista/7) Bootfiles and boot that (really helpful if you killed the original bootloader)
• Booting Win XP Recovery console

 Okay, enough cooliness, let’s start.

For this HowTo I assume the following:

• Basic knowledge of how to use Linux. You’ll NEED that!
• SystemRescueCD (or any other Linux distro which has Grub installed)
• No Harddrive connected in the Computer you build the Stick (i killed my Partition Table just due a Typo :))
• My USB-Stick is recognized as /dev/sda if your USB Stick is recognized as something other replace your /dev entry with mine!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I’ll describe the Steps you’ll ned to do, as every System is different i cannot guide you n00b-Step-by-Step :o)

1. Boot SystemRescueCD

2. Setup the Partition Table

Use Qtparted, gparted or parted to create the following partition Table:
1. Primary FAT32 (as big as you want, i took 10GB on a 16GB thumbdrive)
2. Extended (rest of drive)
now create inside the extended Partition the following Logical Partitions:
3. Locigal FAT16 (800MB, backtrack 3)
4. Logical FAT16 (1800MB, backtrack 4)

So it should look like that:

3. Copy Bootfiles

For quick-Start i uploaded you the grub4dos and grub-boot files you’ll need: (zip) or (tgz)
Copy everything to the FAT32 Partition on your USB-Stick

4. Setup Grub

This part is really important. Be sure you don’t have anything in your System that should not get a new bootsector :) Normally only the USB-Stick get it with this procedure but i’m not responsible if fsck up your running System!

Mount the freshly created FAT32 Partition:

# mkdir /mnt/usbstick
# mount /dev/sda1 /mnt/usbstick

Install Grub and copy it’s bootfiles:

NOTE: if you don’t have /dev/sda as your USB-Stick you need to edit /mnt/usbstick/boot/grub/device.map before executing the next command

# grub-install –root-directory=/mnt/usbstick /dev/sda

Setup Grub4Dos:

# cd /mnt/usbstick
# chmod +x bootlace.com
# ./bootlace.com /dev/sda

Easy isn’t it? :)  
You can give it a try now and see if the Stick is booting or you can continue.

If it is not booting mainly the (hd0) entry in the devices.map is wrong, some helpful tips you can find here:
How to add GRUB to your USB Thumb Drive

The next step is to setup your partitions and ISO files:

5. Copy the Bootdisc contents

I assume the following:

• You have created 2 Extended Partitions for backtrack 3 and 4
• You have Backtrack3 as iso in (usb-stick)/bootcds/bt3.iso
• You have Backtrack4 as iso in (usb-stick)/bootcds/bt4.iso
• You have Ophcrack as iso in (usb-stick)/bootcds/ophcrack.iso

First we need to make the usb-stick ISO’s and created partitions accessible:

# mkdir /mnt/usbroot
# mkdir /mnt/part1
# mkdir /mnt/part2
# mkdir /mnt/isoimg

We’ll mount the Partitions:

# mount /dev/sda1 /mnt/usbroot
# mount /dev/sda5 /mnt/part1
# mount /dev/sda6 /mnt/part2

Now we can access /mnt/usbroot where our subdirectory “bootcds” is and we load backtrack 3 ISO and copy the contents to our 1st extended Partition (yes you can mount ISO’s under linux ^^):

# mount -o loop /mnt/usbroot/bootcds/bt3.iso /mnt/isoimg
# cp -Rv /mnt/isoimg/* /mnt/part1/
# umount /mnt/isoimg

Go on with Backtrack 4:

# mount -o loop /mnt/usbroot/bootcds/bt4.iso /mnt/isoimg
# cp -Rv /mnt/isoimg/* /mnt/part2/
# umount /mnt/isoimg

Everything copied, we unmount the two Partitions:

# umount /mnt/part1
# umount /mnt/part2

Now edit /mnt/usbroot/menu.lst (vi, nano) to your liking – you don’t have to if you use my files and followed this HowTo.

Then unmount everything, reboot and Go On!

# umount /mnt/usbroot
# shutdown -h now

Have Phun!

References:

• How to: make a multi-boot USB drive
• Installing GRUB using grub-install
• Installation von GRUB
• How to add GRUB to your USB Thumb Drive

What i really like when i hear ”Microsoft” is that they want to make good products but they always manages to make a very uber big FAIL.
I must say im not a fan of this company - but i use, like a lot of people, some of their products.

Today i started playing XBOX360 () in a free time schedule i had between my job and my familiy…
Playing playing pla, – zzzz – Freeze
Damn. Ok no prob. Console turned off and on again.

But what the heck is that?! 3 red lights?
Fuck! This is the red ring of death.

After some google it is clear that – because it’s a console made in the begining of 2006 – i have a problem with my gpu or ram or something else hardware based.

Lol i thought – microsoft not only manages to crash my win7 work comuter and htc mobile, they even build gaming consoles that self-destroy!

Also too funny i have no warranty anymore so it is up to me to repair it or throw it out of the window on the street. Some some more hours of google i decided to burn the Motherboard with a hot air gun as shown in this Video:
XBOX 360 Hot Air Gun Fix

So before i can cook the Motherboard i have to open up the console, i used this tutorial it rip off all unneeded things:
XBOX 360 Open Tutorial

In the end - i can’t belive it - it really worked!
I tried the game for at least 3 hours without graphic errors or system freezes.

Here are some pics of my action:

I just thank god my car is not labled “Microsoft” :)

Edit: I played several days and i didn’t got any Problems.. Hurray! ;)

2010-02-17 Edit: Please Read the references i shown on the end of this Post to have an HowTo how to exactly install SipToSis! If i find the Time i can write a detailed Howto with Display environment variables etc, but only if i get some comments to do so :)

Nevertheless i finally managed to Get a working Skype <-> Asterisk connection via SipToSis. Hurray!
I didn’t get Skypeiax to work..

This is how i did it - with Asterisk 1.4.x branch on the same machine skype should also do – running Debian 5.0

First you really need to have a working asterisk distribution , second you need to install Xvfb virtual frame buffer and skype itself the installation and configuration will depend between the systems so i can only cover debian here.
Xtightvnc helps you to install and configure Skype the first time.

• You need to install xvfb, tightvncserver, dbus-x11, dbus, xfce4 ( for configuring skype)
• Next, download skype (from here) and install it
• Then we need SipToSis and install it:
  Download it from here unpack it and move it into /usr/local/siptosis

Use the following command to startup an X-11 VNC Server to start skype and configure it:

# vncserver

Connect to vncserver, usually to the display “:1″ so in Tightvnc you need to enter the address like this: “172.0.0.254:1″.

After this, open up an console and start Skype:

# /usr/bin/skype

and configure a new (or existing) user in this VNC session, then close everything and kill the VNC Server:

#killall -9 vncserver

Now we have skype ready, we need to configure SipToSis, this is what i changed in the default siptosis.cfg config:

#host_port=5070
#username=skypests
#passwd=unimportantpassword
#do_register=no
host_port=5070
contact_url=sip:skypetestuser@172.0.0.254:5070
from_url="skypetestuser" <sip:siptosisuser@172.0.0.254:5060>
username=siptosisuser
realm=asterisk
passwd=siptosisregpassword
expires=3600
do_register=yes
minregrenewtime=120
regfailretrytime=15

Now we need to configure Asterisk with our new SIP User so it knows where to go when SipToSis tries to connect.
Asterisk’s sip.conf:

[siptosisuser]
username=siptosisuser
type=friend
context=from-sip
secret=siptosisregpassword
host=dynamic
nat=no
dtmfmode=auto
canreinvite=no ;(possibly set to yes if you know what you are doing)
qualify=yes

incominglimit=1
outgoinglimit=1
call-limit=1
busylevel=1

insecure=invite,port

As alwas the context is important, this is how i configured the extensions.conf:

For incoming Skype Calls:

[from-sip]
;Dialin from Skype
exten => skype,1,Dial(SIP/myPhone,30,j)

For Outgoing Skype Calls:

exten => 101,1,Dial(SIP/siptosisuser/mySkypeUser)

Save and restart Asterisk.

Now it it time to boot everything together, but first we need a startup script for our SipToSys System.

Startup Script use this for easy copy & paste:

--------------------------------------------------
#!/bin/sh
# loading sound driver
/sbin/modprobe snd_dummy
# setting DISPLAY
export DISPLAY=:1
# starting virtual framebuffer X-Server
nohup /usr/bin/Xvfb ${DISPLAY} -screen scrn 300x600x8 >/dev/null &
#Start Skype
nohup skype >/dev/null &
#Give it some Time to boot
sleep 5
#Start SipToSiS
cd /usr/local/siptosis
nohup ./SipToSis_linux siptosis.cfg >/dev/null &
-------------------------------------------------- 

After executing it look in the asterisk console (asterisk -r) and try to call the Skype user! ;)

Hopefully this is a way for you to make it easier to understand the Connection between Asterisk and skype. 

Have phun :)

References:
SipToSis Website: http://www.mhspot.com/sts/siptosis_ata_howto.html
SipToSis Forum: http://www.mhspot.com/stsforum/index.php
older SipToSis Infos: http://www.vitki.net/v/soho/voip

Startup Script: here
SipIAX Informations: http://www.opennet.ru/base/net/skype2sip.txt.html (use google translator)

Windows XP says most time: 
“Not enough Storage is availible to Complete this command”

Windows 7 says:
 ”Naming information cannot be located because:

The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you.
Contact your system administrator to verify that your domain is properly configured and is currently online.”

Under Win7 even Outlook 2007 didn’t wanted to start!

Win7 Kerberos Problem

Here is the detailed cause and solution to the Problem:

Cause:
The user is not able to authenticate because the Kerberos token that is generated during authentication attempts has a fixed maximum size.

Transports such as remote procedure call (RPC) and HTTP rely on the MaxTokenSize value when they allocate buffers for authentication. In Windows 2000 (the original released version), the MaxTokenSize value is 8,000 bytes. In Windows 2000 Service Pack 2 (SP2) and Microsoft Windows Server 2003, the MaxTokenSize value is 12,000 bytes.

If a user is a member of more than 120 groups, the buffer that is determined by the MaxTokenSize value is not large enough. As a result, users cannot authenticate, and they may receive an “out of memory” error message. Before you apply the hotfix that is described in this article, every group that is added to a user account increases this buffer by 40 bytes.

NOTE: In many scenarios, Windows NTLM authentication works as expected; you may not see the Kerberos authentication problem without analysis. However, scenarios in which Group Policy settings are applied may not work as expected.

Solution:

A registry parameter is available after you apply this hotfix that you can use to increase the Kerberos token size. For example, increasing the token size to 65 KB allows a user to be present in more than 900 groups. Because of the associated SID information, this number may vary.

To use this parameter:

1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry: HK_Local_Machine\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters*
3. If this key is not present, create the key. To do so:
   • Click the following key in the registry: System\CurrentControlSet\Control\Lsa\Kerberos
   • On the Edit menu, click Add Key.
   • Create a Parameters key.
   • Click the new Parameters key.
4. On the Edit menu, click Add Value, and then add the following registry value:
   • Value name: MaxTokenSize
   • Data type: REG_DWORD
   • Radix: Decimal
   • Value data: 65535
5. Quit Registry Editor.

The default value for MaxTokenSize is 12000 decimal. We recommend that you set this value to 65535 decimal, FFFF hexadecimal. If you set this value incorrectly to 65535 hexadecimal (an extremely large value) Kerberos authentication operations may fail, and programs may return errors.