Archive for the ‘Errors’ Category

Now this was one of those stupid things that Microsoft decided to add to their new OS, Vista. The UAC, or User Account Control. Man, what crap…. makes my job as a technician more annoying now.

I worked on a laptop with Vista Business installed. After introducing the pc to the windows domain, I proceeded to add the Domain Admins network group to the local Administrators group of the laptop. Nice!

After which, I noticed I could not access the windows updates through Internet Explorer. I did not have permissions. What!!??!?? I just added it… ok.

Then I noticed that Internet Explorer 7 would always start at the Runounce screen where I have to choose my default search engine. Ahhhhhhhhh!!

So what is the issue….. UAC!!!

This can actually be an easy one.

This is how I was able to fix and there are other solutions!

1. I was able to turn UAC off.

2. Go to start and type msconfig  and hit enter.

3. Select tools from the above tabs and select ‘disable UAC’ and reboot.

That was it… man, I hate this!

I was working on a client’s Microsoft Server 2003 box, when I added some MS patches and then recieved the following error:

“MMC cannot open the file C:\WINDOWS\system32\rrasmgmt.msc.

This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file. ”

Ah nooooooooooooooo… I screwed the server. Well, before I almost decided to reload Service Pack 2, I decided to do a little research first. Turns out that the file indeed exists and file permissions are correct.

Well, how did I fix it…. it was so easy I got scared.

You have to follow the path: C:\Documents and Settings\Administrator\Application Data\Microsoft\MMC

and fom there you can either rename or delete the file of the corresponding Snap-in. Use the profile of the user, which starts the Snap-in.

In may case I just renamed the “rrasmgmt.msc”  and then I was good to go. Easy, peezy!

So I was at a clients and btw, forgot my laptop, and I had to configure their Cisco ASA 5505 series router with the new IP address of their satellites office’s ASA router. You see, they had a site-to-site VPN.

Problem was when I telnet into the ASA I get an “Could not open connection to the host, on port 23.Connect failed” error.

I could ping the router’s ip however, and also when I tried to login using the Cisco ASDM Launcher,  I would get “Unable to launch ASDM Connection Timed out” error. What the heck?!?!!?!?!?!?

Well, the problem was that the router was never configured to accept any other IP for management.  See, the router was set for an IP range of 10.0.X.X. But the router was only configure to allow a range of 192.168.X.X.

It took about 2 hours to figure this out, so I post it here to help relieve you of a future headache, and to remind me as well.

This is how to solve:

You’re going to have to use the console cable to establish a connection to the ASA since it appears that your HTTPS/SSH access lists are not configured correctly.

Use the blue console cable to establish a connection to the ASA and from the command line interface, go to enable mode and issue the following commands:

conf t

http server enable
http 192.168.1.0 255.255.255.0 inside - where the IP has to be the inside IP scope assigned.

Once I did this using the 10.0.X.X IP, I was then able to use ASDM to configure the VPN settings.

Hope this helps…. comment if you have any questions.

Apparently the Event ID 21 for VolSnap seems to be a bug within the SP2 created for the Server OS. What else should we expect…. it’s a Microsoft product.

Anyway, after a little research I found the link to the hotfix provided by Microsoft to take care of this issue. Keep in mind that the server would need to be restarted after the hotfix is applied.

Here’s the link: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=940239&kbln=en-us

Well, I almost goofed up again…. well, actually I did, but I was just trying to fix it. I worked on a PC and attempted to install Internet Explorer 7, but the dang thing screwed up the PC. What else is new about Microsoft!?!?

The icon on the desktop resembled that of Internet Explorer 6, and when I would try to open the browser, it would just create a new shortcut on the desktop. What?!?!?

Well, after a few tries, this is what I did, and in these steps:

1. Right-click on IE icon and select to delete. Just click ‘OK’ at the next message to confirm.

2. From the Control Panel, open the ‘Add & Remove Programs’ list and from the list on the left of the window select ‘Add/Remove Windows Components’. At the Windows Components Wizard, uncheck Internet Explorer, and hit ‘Next’. This will go through the process of removing IE.

3. Run the Dial-a-fix tool, which you can find a link to here ->

4. Restart the PC. (So you may want to add this page to your favorites to come back to easily ; ) )

5. Download Internet Explorer 7 here, then proceed with install.

That is exactly what I did to resolve this issue. If you are having problems with installing the updates that you have downloaded for Windows XP, you can find a quick solution here - >

That’s it.