Rockey100 – Rockey200 Windows 7 Drivers problem solved.

November 23, 2011 1 comment

I have recently purchased a Rockey200 smart card reader for and I use it as SIM card editor. The interface is produced by The drivers are available for download at

The installation software tells you that you do NOT have to plug the card reader into the USB port until you have installed the driver. I didn’t and even so the card reader appeared as an unknown device and windows could not find the drivers for it and the software package is kinda badly designed as it does not come with any “.inf” (driver information file) file that you can select and install the driver separately.

The solution is to force the drivers manually. Open the Computer Management , select “Device Manager” and find the unidentified device under Card Readers. Right click it , properties, go to the Drivers tab and select “Update Driver”. At the next step select “Browse my Computer for driver software” , and then click “Let me pick from a list of device drivers on my computer”. On the list ion the left find “OEM” and select “USB CCID Smart Card Reader”. Next , next ok and it should be installed. Now you will see under the Smart Card Readers TWO times the “USB CCID Smart Card Reader”. One in working condition and one in non working condition. Let them as they are.

You can now start using the Rockey200 SIM Editor. This is the only way I could make it work under Windows 7 after a few unsuccessful attempts with other methods.

If you have a better way to do it and make it work properly please let me know as I am out of ideas.


Re-Flashing / Repairing a bricked Bufalo WZR-HP-G300NH

November 23, 2011 Leave a comment

Many ISP’s (Internet Service Provider) are today upgrading your internet connection for free , and you will get more bandwidth for the same price.
Many of you have old routers that are simply not capable to handle the speed of your newly internet connection and therefore you are forced to make some upgrades on
the hardware , like your cable modem or your router.

Most of the new routers are better in terms of performance and are Plug & Play and you won’t need to do anything beside plugging in the power , internet connection cable and your computer and you are ready to go !
But some of you are a bit more demanding and are not satisfied with the standard capabilities of the router and want to have better performance , more options , more functions
than the standard firmware offers and therefore you have decided to upgrade the router with a new firmware or a non standard firmware. Upgrading the firmware it’s pretty easy this
days and can be simply done from the web interface of the router and in a few minutes you will have the new firmware up and running.
But sometimes the things don’t go as planned and your firmware upgrade can fail and then you will have a so called “bricked” router and you don’t know what to do with it.

Most of the so called SOHO (Small Office/Home Office) routers are pretty hard to brick by accident but if this happen they can be fixed and I am going to show you how.
In our case we will take the new Buffalo WZR-HP-G300NH router.
The standard firmware that comes with the router can be the version 1.76 or 1.72 and in our case we will try to replace this firmware with a non standard firmware like the one
offered by DD-WRT and we can download the latest firmware from the DD-WRT website.
You can either download the firmware from or you can download it from here : DDWRT Wiki Buffalo WZR-HP-G300NH (I recommend the second one).

After downloading the firmware you will find detailed information on how to actually flash the new firmware within the ZIP file containing the firmware and the How-To manual.
The firmware upgrade it is pretty straight forward :

  1. Start up Windows.
  2. Please confirm that both the LAN adapter and the AirStation’s IP addresses are on the same network subnet. Refer to AirStation’s User Manual for instructions on changing IP address settings.
  3. Select [Run] from the Start Menu.
    Enter “” (the AirStation’s LAN side IP address) in the field and click “OK”.
  4. Navigate to the AirStation’s Web Admin interface. (If you haven’t created a account yet, enter a username and password. Click “Change Password”.)
  5. Click “Administration” from the upper menu.
    When the login prompt appears, enter your new username and password.
  6. Click “Firmware Upgrade”.
  7. Click “Browse” to the right of “Please select a file to upgrade” and navigate to the extracted firmware file. The file should be of the form “wzrhpg300nh-pro-***” where *** is the version number. Click “Upgrade”.
  8. During the firmware update, the Diag LED will flash for about 5 minutes. When the update is complete, the LED will turn off. Do not turn off the AirStation until the firmware update is complete. If the unit is unplugged while the Diag LED is still flashing, the AirStation may be damaged.

After flashing the router with the new firmware please wait for at least 5 minutes or until you see the green lights on the router and the DIAG led stopped flashing.
You are done.

Now the tricky part after this is that IF you want to go back to the original firmware you will have to DOWNGRADE the firmware to version 1.65 , 1.66 or similar before
you can actually re-flash the router to another version.
You can download the standard firmware from the Buffalo website here :

Now the router has some kind of built in fail-safe mechanism that will not let you downgrade from the web interface and when you try to re-flash the router to a previous version , the firmware upgrade process will fail. The only way to re-flash the router is then by TFTP (Trivial File Transfer Protocol).
This method can also be used if your initial firmware upgrade failed by some reason and the only light you can see on the router is the DIAG led that flashes constantly.

In order to flash the router by TFTP you will have to know a few things :
– The Buffalo WZR-HP-G300NH can only be flashed when the router has its factory default IP address that is :
So if you changed this , please change it back to the factory defaults. This can be simply made by pressing the reset button on the bottom of the router for more than 3 seconds.
– You will need to know the MAC address of the router. You can find that on the web interface of the router or on the router itself on the white sticker.

Now , you can either do this from the Windows or Linux.

A. Windows
As your router is dead , your machine will not have any IP address assigned so you will need to assign it manually.
1) Go to Start and click on Control Panel.

2) Control Panel window will appear. Double click on Network Connections.

3) Network Connections window will appear. Right click correct Local Area Connection by identifying correct network card and click Properties.

4) Select Internet Protocol (TCP/IP). Click on Properties.
You can now manually type in the IP address, Subnet mask, Default gateway and DNS servers.
Assign the following IP address : and SubnetMask :

Locate the firmware file you want to have it flashed on your computer. Let’s say you have saved it on your C:  drive in a folder called BUFFALO.
Please note the name of the BIN file you have there , it will be something like : wzrhpg300nh-176.bin
Download Linksys TFTP utility

Now , power off the router and leave it connected to your machine by the network cable plugged into one of the 4 black Ethernet ports.
Open a command prompt and type ” route print” in order to get a list of your network card adapters. Write down the number of your network card.
My list looks something like :

Network Adapter
12…00 1b fc 6b 3f d8 ……Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
11…00 1b fc 6b 36 d4 ……Realtek PCI GBE Family Controller
26…00 50 56 c0 00 01 ……VMware Virtual Ethernet Adapter for VMnet1
27…00 50 56 c0 00 08 ……VMware Virtual Ethernet Adapter for VMnet8
1………………………Software Loopback Interface 1

My active network card it is number 12
Now you will need to bind the interface number 12 with the routers MAC address and you can do this by going back to the command prompt and type :

netsh interface ipv4 add neighbors 12 xx-xx-xx-xx-xx-xx

Where xx-xx-xx-xx-xx-xx it’s the actual MAC address of your OWN router and replace the number 12 with your own interface number.
Run Linksys TFTP utility that you downloaded earlier .
Put in the Server address. Password field let it empty and the file is the firmware file you downloaded wzrhpg300nh-176.
Set retry time to 60 just in case so you have time to power on the router.

Now hit the  “Upgrade” button in the TFTP utility and power on the router.
The flash process should start now
Wait until the flashing process is complete.
The router will reboot itself when the upgrade is done. This can take up to 10 minutes so please be patient until your router reboots by itself.
Now the green lights are ON and the DIAG led stopped flashing.

You can now open a browser and navigate to to see your router interface.

B. Linux

If you do not have a Linux running you can just download the Ubuntu from here and burn the image on a CD or put it on an USB flash drive.
You can download it from here :
On the same page you can also find out how to make a bootable CD or USB flash drive.
Save the firmware on a USB Flash drive.

Now that you are all set , boot the machine with the Ubuntu and choose to TEST the Ubuntu and not install it on your machine.
The machine will come booted in the graphic mode and you will need a shell in order to perform the tftp firmware upgrade.
When the Ubuntu booted up press : CTRL+ALT+F1
This will take you to a shell prompt.
While in the shell type :

sudo apt-get update
sudo apt-get install tftp-hpa
sudo /etc/init.d/networking stop
sudo ifconfig eth0
sudo ifconfig eth0 netmask
sudo arp -s xx:xx:xx:xx:xx:xx
# where xx:xx:xx:xx:xx:xx is your router MAC address.
#If you booted on a CD you will need to find the firmware on the USB flash drive.
# that would be something like /media/127648279256 (you will see what I am talking about)
cd /
cd media
#note the long number , that is your USB drive
cd 127648279256
#from now you are at the tftp command prompt, the “tftp>”  Your prompt will look something like “tftp>” so the commands you need to give are after the prompt.
tftp> verbose
tftp> binary
tftp> trace
tftp> rexmt 1
tftp> timeout 60
tftp> put wzrg300nh-176.tftp

Now power on the router and wait. You will see the firmware being sent to the router.
Wait until the flashing process is complete.
The router will reboot itself when the upgrade is done. This can take up to 10 minutes so please be patient until your router reboots by itself.
Now the green lights are ON and the DIAG led stopped flashing.

You are done and can reboot the machine and enjoy your new un-bricked router.

This guide has been made with information from the DD-WRT Forum.

Categories: IT Tags: , ,

Backup Exec 2010 can not view DAG, Exchange 2010

November 23, 2011 Leave a comment

Some people are currently faced with the following problem :

You are unable to access my Exchange 2010 DAG from Backup Exec 2010 for backup.
The DAG is visible from the selection list but fails authentication.

There are many people who as this quetsion on the net, but no expert from any forum the anwser yet.
The Backup Exec server has a Windows Server 2008 R2 OS and has the Exchange Management Tools installed.

My backup guy was fighting with this problem a few days and then finally asked my opinion.
After looking around the setup for a few minutes I found the problem and fixed it within seconds !

The solution is simple actually.
When you are faced with such a problem make sure that your DAG Cluster it’s OK and does not have any failed state.

Please check your DAG Cluster via the “Failover Cluster Management” in control panel.
I bet your DAG has the Cluster name / IP address in the Failed state.

Bring that resource up and everything should be ok.

Google suggest … why not ?

November 23, 2011 Leave a comment

I made an interesting discovery today.
You know how Google will try to suggest your search query ? Go for example at and start typing in the search field “breaking” ..  and you will see that Google will suggest the next words and show you the approximation of the results found..

Well , try to start your query with “uncensored” … and surprise, surprise ….. no suggestions from Google ? Why ? When you perform the search the results would be about 6,2mil …
So , why no suggestions here ? Is this a bug or is just no one that made that search before ?

Interesting huh ?

An error occurred with error code ‘2147504141’

November 23, 2011 Leave a comment

I have decided to try and install / test the new Exchange 2010. I have downloaded the Beta from the MS site , prepared a Vmware environment with Windows 2008 Enterprise version.
Installed Windows , patched everything , promoted the machine to a DC and I started Exchange 2010 installation.
After promoting to DC , I remembered the computer name was something like : “PC2hjCJS-blablaxxx22x2” and would not be nice when I will have to test OWA and other stuff so I renamed the DC into something more easy to type and started Exchange installation.
All the preparation tasks were complete now and Exchange started installing the roles and checking the perquisites for the roles installation.
When it came to the HUB installation I got a strange Error.

The execution of: “$error.Clear(); install-ExsetdataAtom -AtomName SMTP -DomainController $RoleDomainController”, generated the following error: “An error occurred with error code ‘2147504141’ and message ‘The property cannot be found in the cache.’.”.

An error occurred with error code ‘2147504141’ and message ‘The property cannot be found in the cache.’.

After digging a while on the web I saw that the error is generated because the IPV6 was ENABLED but did not had an IP address assigned.
You can read a bit more about this on this Technet post :

I have then tried to manually assign an IP address to the IPV6 – Did not help
I have tried to totally disable IPV6 – it did not help
Tried to follow the instructions on the K952842 – did not help

So on Exchange 2007 the install did not work without IPV6 enabled and now on the Exchange 2010 will not work without disabling it ?

Well after a while of trying all kind of stuff I just gave up.

Installed a new Windows 2008 (this time I did a standard edition , just to have some variation) and disabled IPV6 BEFORE I started the Exchange installation.
Patched with all the patches.
Renamed the machine.
Installed IIS and .Net 3.0
Disabled IPV6 on the network adapter and in the registry.
Promoted the machine as DC on a new forest.
Started installation and everything went ok.

So my theory is : You need to disable the IPV6 BEFORE you even start the Exchange 2010 setup and BEFORE the exchange perorms all the test and the pre installation tasks and/or Install IIS after you renamed the machine.

So my theory is correct , at least for my environment.

IPV6 needs to be disabled BEFORE you start exchange 2010 installation tasks or Exchange / IIS does not like the fact that I renamed the  machine after IIS was installed ?

Feel free to come with any arguments and let’s discuss this further if you feel different.

Topology discovery failed, error 0x80040a02

November 23, 2011 Leave a comment

I needed a new test bench for testing the Exchange 2007 for someone and I did not wanted to use some of the enw hwrdware so I installed Windows 2008 on an old HP ML350 server , patched everything promoted the machine to a DC and started installing Exchange 2007.

Well , first thing it will start bitching over that you are running with a dynamic IP configuration so I went and double checked but I remembered correctly. The IP was set to static.
Went and started the setup again and again started bitching about dynamic IP.
Well , it was only one way to make it stop , as on the IPV4 was running static , I just DISABLED the IPV6 Protocol as I was not using it.

Started Exchange installation and after performing the pre installation test it installed the management tools and started the Hub Transport role.
After a few minutes the installation stopped with an error but nothing was actually specified.
Started digging trough events and I discovered this error :

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3608). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.


Checked all the configurations , checked DNS , checked the LDAP , everything was actually ok.
Tried to reboot the server and re-start the installation process but still the same error.

After hours of debugging and checking configuration , changing DNS and all kind of stuff I found an article that suggested enabling IPV6.

I did  so and the error is gone. After rebooting the machine I was able to install the rest of the server roles and everything was ok.

So question is : Why in the bloody hell will MS have IPV6 installed by default and why would Exchange start bitching about Dynamic IP allocation on IPV6 if I don’t use it ? Why would an Exchange installation STOP without the damn IPV6 ??
MS Works in misterious ways.

So if you guys are trying to install Ex2k7 on 2008 remember to have IPV6 enabled !!

OCS Edge Server errors

November 23, 2011 Leave a comment

I decided to start blogging this deployment as it might help others.

A few months ago we decided to implement OCS 2007 and we had setup a test environment.
We installed OCS 2007 standard edition with a front end machine and an edge machine.
We tested the setup for a month or so and we decided to implement it in production.

Now , the initial setup was on a single domain and everything worked perfect. The production environment it is a bit more complicated with a forest and 6 subdomains.

Installation was performed and everything worked fine until we started testing when some strange errors started to show up :

Failed to process data received from the client

Timed out waiting for client to present validation cookie

Over the past 0 minutes Office Communications Server has disconnected client(s) 1 time(s) because of timing out waiting for cookie to be presented. The last such client which was disconnected is “xx.xx.xx.xx:22851”
Cause: This can occur if client does not present a validation cookie within 20 seconds of getting connected
Check to make sure that the connection came from a trustworthy client. This could indicate an attack being mounted by a rogue client.

After digging a bit we also found the solution.
Due to the fact that we used our own intern ROOT CA to issue the SSL certificate for the INTERNAL Edge interface the clients were trying to connect to the internal Root CA to verify the SSL.

There are 2 solutions to this problem.
1. Open the firewall on port 80 towards the root CA .. which I do not recommend or

2. Use a SSL issued by an external Root CA.

Also a thing never documented by Microsoft.

We were using 1 SSL certificate with 3 different alternative names for all the interfaces : Edge , AV , Web conferencing but looks like this setup is not supported and if you are using one SSL with different alternate names on all the interfaces it seems that the clients can connect to the OCS server without any authentication … also the EXTERNAL users without a domain account can connect . So I suggest using different SSL’s for the interfaces.

Categories: IT Tags: , ,