My laptop has an annoying habit of ‘freezing” and requiring a manual power off and back on again to get it working (HP Probook 6560b).
A look in the system log yielded hundreds of event ID 62464 errors.
Log Name: System
Source: amdkmdag
Date: xx/xx/xxxx xx:xx:xx PM
Event ID: 62464
Task Category: DVD_OV
Level: Information
Keywords: Classic
User: N/A
Computer: xxxxxxxxx
Description:
UVD Information
Solution
It seems I’m not the only one, a quick internet search turned up a few people with the same problem. However all the other posts were advocating disabling the logging of the error. I’m not a fan of disabling error logging no matter how ‘Spammy’ it is.
It’s obviously being generated by my graphics driver, so a look there told me what version I was running. (Start > Run devmgmt.msc {Enter}).
I went to HP and downloaded the latest published AMD driver they had, and rebooted, problem solved.
Related Articles, References, Credits, or External Links
Seen on Windows Server 2008 R2 running on VMware ESX/ESXi 4.0 and 4.1
Solution
Firstly, I’m assuming you are running the latest version of VMware tools on the machine in question, this procedure was carried out with VMware tools version 8.3.2 and cures the problem.
1. On the affected VM Click Start > In the search run box type > devmgmt.msc {enter}
2. Expand “Display adapters” Right click the one in use > “Update Driver Software.”
3. Browse to ” C:/Program Files/Common Files/VMware/Drivers/wddm_video” > Next.
4. When finished it should say “VMware SVGA 3D” Drivers have installed successfully. > Close
5. You will be prompted for a reboot, do so.
Note: Also ensure that you have allowed at least 8MB RAM for the graphics card (machine needs to be powered off before you can edit this).
Related Articles, References, Credits, or External Links
I promised to take a quick look at one of my mum’s friends laptops the other evening, the brief was; they had a problem opening office attachments, and their wireless mouse was’nt working. I assumed they needed the document conversion pack and probably had a flat battery, so I downloaded the update, and slung some batteries in my laptop bag.
The attachment problem was sorted (by re-installing office and changing some file assocations). But the mouse (Which was bluetooth) was somewhat more “fun” to fix.
Basically the laptop had been rebuilt some time ago, and since then the bluetooth would not work, normally I’d just download the drivers but that would have been too simple. Before I could get the mouse to work I needed to enable bluetooth on the laptop.
Solution
1. Stop searchig the chassis there is no switch to enable blueetooth, it can only be enabled by software.
4. It will dump all its files in C:delldriversR140135, once the files have extracted navigate to the C:delldriversR1401353100_216 folder and run setup.exe.
5. At the end it will tell you to enable wireless by pressing fn&F2 – THIS WONT WORK, click cancel.
6. Back in the C:delldriversR1401353100_216 folder you need to open the Win32 folder if your on a 32 bit machine or the Win64 folder if you on a 64 bit machine. (I dont know).
7. Locate the Inst.exe file and run it.
8. At the end it will once again ask you to press Fn and F2 – Do nothing, but leave the install sat there waiting.
9. With the install still waiting, navigate to “C:Program FilesWIDCOMMBluetooth Software” and locate BTTray.exe
10. Double click BTTray.exe and after a few seconds the bluetooth icon should appear in the taskbar (bottom right). Right click it and turn it on.
11. At this point, the install will burst back into life and setup your bluetooth wireless.
Related Articles, References, Credits, or External Links
Before Server 2008 R2 when we needed to inject drivers into our WDS images we had to do it like this.
Now however the process is a lot more elegant! Simply import the drivers into WDS, then inject them into the boot images (Yes the boot images NOT the Windows Images you are deploying!)
Solution
Add Driver Packages to Image is “Greyed out”
If while attempting to add drivers, the option to “Add Driver Packages to Image” is grayed out.
Then you may need to update your boot images from Server 2008/Vista images to 2008 R2/Windows 7 Images. (or from version 6.0.6000 to 6.1.7600).
Related Articles, References, Credits, or External Links
I’ve seen this on both the Windows 8 (Consumer Preview), and the Windows Server 8 (Beta), whilst running them in VMware Workstation 8. They install fine, but if you install the VMware tools all you get is a black screen.
This is because the SVGA Driver than VMware Tools installs Windows 8 does NOT Like.
Note: This does not hppen on ESXi 5.
Solution
I knew this was going to happen, so I took a snapshot before I installed VMware tools, Then I had the luxury of reverting back. If you are reading this you probably didn’t! If that IS the case, then press F8 as the Virtual Machine starts to boot to launch Automatic Repair (be quick on the keys).
Installing VMware Tools in Windows 8
1. To stop this happening, when you install VMware tools select > Custom > Remove the SVGA Driver > Next > Finish > Yes (to reboot).
2. You will notice that the display driver that is uses, is the “Microsoft Basic Display Adaptor”.
Related Articles, References, Credits, or External Links
Problem reoccurs on a rough 5-7 days cycle, rebooting the server solves the problem.
You may also see
System Event Log:
Log Name: System
Source: Microsoft-Windows-GroupPolicy
Event ID: 1054
Level: Error
User: SYSTEM
Description:
The processing of Group Policy failed. Windows could not obtain the name of a
domain controller. This could be caused by a name resolution failure. Verify
your Domain Name System (DNS) is configured and working correctly.
DNS Server Event log:
Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Event ID: 408
Level: Error
Description:
The DNS server could not open socket for address 0.0.0.0.
Verify that this is a valid IP address for the server computer. If it is NOT
valid use the Interfaces dialog under Server Properties in the DNS Manager to
remove it from the list of IP interfaces. Then stop and restart the DNS
server. (If this was the only IP interface on this machine and the DNS server
may not have started as a result of this error. In that case remove the
DNSParameters ListenAddress value in the services section of the registry
and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
Log Name: DNS Server
Source: Microsoft-Windows-DNS-Server-Service
Event ID: 404
Level: Error
Description:
The DNS server could not bind a Transmission Control Protocol (TCP) socket to
address 0.0.0.0. The event data is the error code. An IP address of 0.0.0.0
can indicate a valid "any address" configuration in which all configured IP
addresses on the computer are available for use.
Restart the DNS server or reboot the computer.
When trying to Open the Exchange Management Console
You will see the following error,
get-ExchangeServer Failed
Error:
No suitable domain controller was found in domain {your domain name}
Errors:
An Active Directory error 0x51 occurred when trying to check server
{your servername and your domain name} :389 suitability. The LDAP server is
unavailable.
Solution
It’s caused by a driver using the Transport Driver Interface, If you see this problem install this hotfix.
Ordinary domain users cannot install printer drivers, because installing a printer driver requires “rights”. So unless you have installed the print driver as an administrator, the users cannot add a new printer, without logging on with administrative privileges, installing the printer and driver, then logging back on as the user, only at that point can they install the printer.
To stop this happening grant the users rights to install printer drivers, Note: this does have security implications, they can then install any printer they like, including ones that might have “dodgy” drivers.
Solution
This can be set in group policy either in local policy, or via domain GPO, you can locate the policy at,
Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options > Devices: Prevent users from installing printer drivers.
A while ago I spun up a CentOS server in VMware Workstation, and I could not get it connected to the network, I was in a bit of a hurry, so I blew it away and just built a new server with CentOS 6. This week I’ve been using VirtualBox and spun up a new CentOS 7 server and had the same problem.
Solution
1. Quite why CentOS 7 does this I’m not sure, My NIC is called enp0s3 (run ‘ip addr’ to find yours). Then take a look at;
Disclaimer: This article is for educational purposes only. Having the ability to pick a lock does not make you a thief. The main thing to take away from this article is, “DONT secure your wireless network with WEP“.
WEP, has been around for a long time now, its limited to an alpha numeric password, 0-9 and A-F (because its in hexadecimal), the password can be 40, 64 or 126 bits long. The flaw is, each bit of information is encrypted with the SAME key, If you can get enough packets (24 bit long packets called IV’s), you can mathematically work out what the key is.
Solution
To do this I’m going to use BackTrack 5 (R1) installed in a Virtual machine, the Network card I’m using is an ALFA AWUS036NH USB wireless card, I’m using this card because the Ralink RT2878/3078 chipset that’s inside it just works with airmon-ng, without the need to patch drivers or mess about.
Note: If your wireless card does not work please do not email me go the the Aircrack-ng forums.
1. After I’ve plugged the wireless card into the host machine, I’m going to present it to the virtual machine. VM > Removable Devices > Ralink 802.11 n WLAN > Connect.
2. To make sure BackTrack can see the card issue the following command;
[box] airmon-ng [/box]
Take note of the interface name (in the example below it’s wlan0). Then to change the MAC address of the card we are going to ‘spoof’ a false MAC address of 00:11:22:33:44:55 with the following commands. (Note: Your interface may not be wlan0, change accordingly);
Then to scan and see what networks the card can see issue the following command
[box] airodump-ng wlan0 [/box]
3. Airodump will continue to scan until you press CTRL+C. When you see the target network, take a note of its BSSID and its channel number. My target below is called PeteNetLive and the bssid is 00:16:B6:B4:66:46 and its on channel 1).
4. Now scan the target network with the following command;
Note: ‘-3’ denotes a client attack, if your data packets do not rise (you will understand in a minute), then try with ‘-4’ instead.
7. Back in the original terminal window the Data count should start to rise, do nothing further until its over 10,000 (that’s 10,000 IVs captured).
Reality Check!: In most tutorials (including my video above) this is a nice painless process, it relies on there being a decent quality signal, the router/access point not crashing because you are ‘battering’ it, and there being lots of healthy traffic around. You can get enough data packets without the ‘aireplay-ng -3’ command, but it will take a lot longer. You can stop and start the forcing of traffic by pressing CTRL+C, and then executing the command again (it just appends the data to the capture file). In this example I used about five attempts (the router froze and needed to be rebooted). So this is not a quick process. Someone passively attacking your wireless will need lot of patience. This took about an hour and I was right next to the router, and I rebooted it every time it locked up, (which I saw because the Data figure suddenly stopped rising).
8. In the example below I’m now over 10,000 IV’s captured, and I’ve stopped forcing traffic (CTRL+C).
9. By default your capture will be in your home folder, and it will be called filename-01.cap (where filename is the name you used in step 4).
10. To crack the key execute the following command;
