Archive

Author Archive

Toughbook CF-30 MK2 Windows 7 x64 brightness

January 20, 2015 Leave a comment

Short Story

Change the brightness in the bios from “High Brightness” to “Normal Brightness”

Long Story

Like many organizations we try to get as much life out of our mobile equipment as we can.  This time around I was working on some Panasonic CF-30 toughbooks, upgrading them to windows 7 64 bit, installing SSDs and adding 8 gigs of ram to them.

When all the upgrades were complete it was like a new laptop!  Kudos goes to the great people over to toughwiki for making a great set of instruction for all the drivers I needed.

So with the software installed I’m sent the toughbooks into the field, only to have them come back the next day saying the back-light blinded the drivers at night.

I searched and searched and tried and tried and nothing worked.  Forum after forum, walk through after wiki and none of the “solutions” worked to allow either the keyboard or windows to dim the back-light.

We had it sitting on the bench for a while and ended up needing the power outlet that it was plugged into for another project.  My co-worker started working on the toughbook again with fresh eyes and that’s when we noticed it.  The back-light dimmed when on battery!  not only that it was controllable from the keyboard using the function keys!  We plugged it back in and sure enough we couldn’t control the back-light.  After some more searching with new information we landed at the bios.  There is a display setting for high brightness or normal brightness.  If its on high brightness the laptop cannot control the brightness level, normal it can be controlled either on battery or off.

VMware Workstation Server not starting “vmware failed to configure the workstation server”

September 13, 2013 Leave a comment

I have been doing some upgrades on my servers at home recently and decided it was time to ditch vmware server 2.0 and upgrade to workstation 8 (due to hardware limitations I’m not going esxi just yet)

I installed workstation and was going to start the shared VMs section of preferences.  This would allow me to start VMs on the Server start (instead of having to start them manually)

I configured a free port (7443) for the sharing server to run but it would not start.  I kept getting this error “vmware failed to configure the workstation server”.  I did some googling and found a few solutions referencing changing a xml file, or removing it all together.  All of the (very few) solutions I came across just wouldn’t fix the problem!  I even found a few walkthroughs on enabling logging to see if something jumped out in the log, nothing.

I had to fall back on my IT skills and look at the problem with fresh eyes.  I checked windows services and sure enough there is a service called “VMware Workstation Server” that wasn’t started.  I tried to manually start it, but it returned an error saying that one of the dependencies has failed on start up.

I opened up event viewer and sure enough there was an error with a dependency not starting.  The culprit was the VMware USB Arbitrator service!  I did some searching on a fix from vmware and found this page http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2043656 .  The solution was to

  1. Launch a command prompt on the host machine using an Administrator account.
  2. Run this command:
    • In a 32-bit host operating system:

      "C:\Program Files\VMware\VMware Workstation\vnetlib.exe" -- install hcmon

      In a 64-bit host operating system:

      "C:\Program Files (x86)\VMware\VMware Workstation\vnetlib64.exe" -- install hcmon

  3. Open the Windows service console and start the service manually. The service should now start successfully.

 

Now off to enjoy some linked clone goodness

Troubleshoting DDNS with zoneedit and nslookup

September 11, 2013 1 comment

zoneeditToday I was playing around with some remote services I installed on a server at home.  While using the software, I stared getting connection errors.  I opened up CMD and did a ping of my ddns hostname.  Sure enough I received a wrong IP address.  Now I have ran into a similar issue with zoneedit before when my IP address would renew with my ISP.  It might take a few minutes but DNS is eventually updated and everything would be working again.  This time though I wasn’t getting an IP from the range of my current ISP (lets say 172.x.x.x), I was getting an IP address from the range of my old ISP (142.x.x.x).

So after a few “What the hell is going on here?” ‘s I started going through scenarios.  Was the DNS server at work to fault?  or perhaps the ISP DNS server?  Perhaps it was zoneedit reporting incorrect IPs?

First off I checked my zoneedit account.  After logging in I found that all my ddns records were up to date with a 172.x.x.x IP, so that ruled zoneedit out.

Next I opened up CMD and ran nslookup.  Now nslookup is a pretty handy tool for those who havn’t used it.  Microsoft’s discription of the tool is “Nslookup.exe is a command-line administrative tool for testing and troubleshooting DNS servers” (http://support.microsoft.com/kb/200525).

I started with typing my domain name into the nslookup prompt. Lone behold my correct IP (172.x.x.x) was resolving.  Hold on a second….  I opened another CMD window and pinged my dns address. Sure enough it resolved the proper IP (127.x.x.x).  Always love problems that fix themselves!

Sadly this wasn’t to be the case for long.  I started up the software again but after a while I stared getting disconnects.  “That was too easy” I thought as I pinged my ddns hostname and sure enough it was showing up as 142.x.x.x.

This time I jumped right into nslookup and this time my ddns hostname was resolving to 142.x.x.x.  So I typed in lserver to get a list of the DNS servers my PC is using to resolve IP addresses.  I then typed in lserver 192.x.x.x (the ip of my first DNS server) and tried resolving my dns name, same 142.x.x.x IP.  I went through the list and got the same IP each time.  I then typed in lserver 8.8.8.8 (google’s publicly available DNS server) and tried resolving my ddns name, and I got my 172.x.x.x IP.

So now I though it was a local dns problem.  I changed the order of my dns servers to include google as first reference and went back to my software.  After a little while longer though more disconnects!

Back to nslookup and sure enough setting lserver 8.8.8.8 and then typing in my ddns name was returning the dreaded 142.x.x.x!  The only thing I could think of now was to go back to zoneedit.

Zoneedit uses 2 name servers with your account for redundancy.  I set  lserver server1.zoneedit.com in nslookup and tried resolving my ddns name and got my correct 172.x.x.x.  I then set lserver server2.zoneedit.com and sure enough got back the 142.x.x.x record.  I fired up the support page on zoneedit.com and sent in a trouble ticket explaining that server2 was keeping a cached record for my ddns account.  Hopefully I get a reply soon!

 

UPDATE

 

I did get a reply and zoneedit fixed their server.  I did however had to republish my domain on their web portal to update the problem server with the correct information.

Disable the android lock screen password with VPN enabled (stored credentials)

April 15, 2013 24 comments

android lock screenWhile I was out the other night and playing around on my phone.  I started wondering if the Home Automation app I made over the last few months would work over VPN (The home automation back-end is only available through the local network… don’t want joe blow turning my speakers on at 3am!).  So I jumped into the Settings of my android phone and then into the VPN section.

I was surprised to see that I needed a password protected lock screen to have a VPN account set up.  I can understand if you were going to store the password on the phone, but I had planned to type it in when connecting (I really wouldn’t be using it much).  So I set up a pattern password and connected to my VPN.  The app worked fine!

I put my phone down and later came back to it, but GASP!  I had forgotten my pattern.  After a few wrong tries the unlock screen had a “Forgot Password” button on the bottom right.

Google’s forgot password function for android phones uses your Google ID and password set up on the phone.  If you can produce these credentials your phone will load into the lock screen password setup section.  I swiped in the new pattern the first time, then on the confirmation I screwed it up.  Instinctively I hit cancel to go back and try it again…  But the home screen came up.

I powered off  my phone and turned it back on and sure enough I had my old unprotected lock screen back.

So to re-cap,

To Remove a password lock screen with VPN/Stored Credentials on Android

  1. Set up VPN
  2. Add pattern unlock screen
  3. lock phone and swipe the wrong password 3-5 times
  4. tap “forgot password”
  5. log in with your Google account
  6. Cancel on the confirm password

And with that you have stored credentials without a password protected lock screen.

New Job!

August 3, 2012 Leave a comment

No Longer am I a Dealership SysAdmin, I am now an Airport SysAdmin!  Thing are just taking off for me 🙂

Categories: Uncategorized

VMware Fault Tolerance Setup Error

August 3, 2012 Leave a comment

I was recently tasked with configuring VMware Fault Tolerance on a pair of hosts in our network.  I checked out the VMware documentation and followed the steps/best practices but still had a bit of trouble getting FT to work.

Both hosts showed configured for FT and I could enable FT on the VM, but every time I tried to start the VM it would come back with an error “Could not start the secondary VM“. Checking the details in the “Recent Tasks” window I found the error description, “Virtual machines in the same Fault Tolerance pair cannot be on the same host“.  This error description a little boggling as both VM and duplicate were on different servers.  At least I had an error that I could research, so off to Google I went!

Sadly, the few articles I did find that referenced this error were very little help. I tried the troubleshooting steps from forum posts (resetting FT, live migrating a VM (and it working successfully), etc) but still got the same error when trying to start the VM.  I finally found the solution while testing the FT interfaces on both hosts.

What I decided to do was create a test VM and vSwitch.  The vSwitch would be set to my FT vlan (1000) and the test VM (WinXP) would have its nework interface set to the test vSwitch.  With a PC on my FT network I tried pinging both of my VM hosts.  Sure enough I didn’t receive a reply from either host.  So I checked the configuration on the swtiches each host was connected to and found there was no way the two hosts would communicate on vlan 1000.  I reconfigured the switches and did my ping test from the test VM, this time successfully.  I then started a FT enabled VM and voila, FT worked!
Hopefully this post will save someone a few days of troubleshooting!

Windows XP restore Virus/Malware Start menu shortcuts

June 9, 2011 28 comments

Recently we have been getting a few copy’s of the “Windows XP Restore” virus going around.  This one is a nasty bit of kit.  It changes all your files on C:\ to hidden and throws in a bunch of popup crap.  I have been using malwarebytes anti-malware to get rid of the bugger but this virus leaves a parting gift of a hours worth of cleanup for the user profile.  So far my process has been to rename the users profile folder under c:\documents and settings.  I just rename the user folder to user.old.  Then I log in as the user which creates a new profile.  I then migrate the data back over manually.

Another pain in the ass with this virus is start menu shortcuts.  Even after un-hiding the “All Users” start menu and the profile start menu all the shortcuts were still missing,  So I went on the hunt and found that the virus moves them to C:\Documents and Settings\user\Local Settings\Temp\smtmp\1.  It also seems to have moved quick launch to C:\Documents and Settings\user\Local Settings\Temp\smtmp\2.

NOTE: Recover these files before you run your AV software as they have started removing the files as part of the virus.

Hope this little bit of info helps!