Bug1: Leash32 from 2.6Beta7 crashes when starting on a Windows 2000 machine when attached to a remote network with no VPN connection. Error message (note memory addresses changes): "The instruction at 0x77fcca36" referenced memory at "0x000c0100" the memory could not be written". This does not occur on Windows XP boxes, and leash32 runs fine after the vpn connection is established. Bug2: It appears that for some reason that Leash32 likes to disable the AFS Status setting. It appears to happen when it can not contact the cell for some reason. Can this be changed or over ridden? Possibly with a registry key. We are trying to support remote users, and run leash32 on startup (in the task tray) and it is very inconvenient for them to have to enable the afs properties frequently. Bug3: When obtaining tickets via ms2mit.exe and when they expire you receive an error message that says: Ticket expired (Kerberos error 32) krb5_get_renewed_creds() failed. However, clicking ok, and then using the renew button in leash it works. Feature Reqest1: Add options like -aklog to leash32 to be used in conjunction with -ms2mit. Also add -persistent to leash32 to be used in conjunction with -ms2mit, so it does the -ms2mit then stays in the task tray. I would like to be able to call something like "leash32 -ms2mit -aklog -persistent" from the command line. Feature Request2: Make ms2mit optionally run as a service. It would be nice if it ran in the background (or through leash32) and automatically extracted tickets from the ms lsa cache when they were renewed. Thanks, Matt