A user reported that they had printed some documents but that they were not printing. Looking at the print server I saw that the printer was showing as Offline.
I was able to ping it as well as bring up the web interface. As a test I disabled SNMP checking for the printer’s port by doing the following:
- Right click the printer & select Properties.
- Select the Ports tab.
- Select the printer’s port & click Configure Port.
- Uncheck SNMP Status Enabled.
- Click OK.
The moment I did that the printer went to a Ready status & the documents printed. I have two printer server that both have this printer configured. They were both experiencing the issue so I believe the issue to be with the print servers.
OK, perhaps the SNMP string got changed on the device. I ran an SNMP test (Paessler has a good free one http://www.paessler.com/tools/snmptester) but it check out good using the SNMP string configured on the printer’s port.
So when in doubt use ProcMon. First, I set the printer’s port back to using SNMP checking then fired off ProcMon on the printer server. Within a minute the printer switched from Ready to Offline. I stopped ProcMon & begun the artful task of sifting through the capture. I noticed a section where the print server starting sending SNMP requests to all the printers. I saw a response for all the other printers but none for the one in question. Note below all I saw were UDP Send.
So for some reason the printer is not responding (or not responding timely. I didn’t feel like doing a full on packet capture). So like everything else if it’s not working, reboot. Once the printer came back up it I started another ProcMon capture. This time I saw the SNMP requests & responses (UDP Send & UDP Receive).
Sure I could have just left SNMP unchecked on the printer port but that wouldn’t have really resolved the issue; just masked it. Now if it continues to happen I may have to see if there is a newer firmware for the printer that resolves SNMP issues (or contact HP, ugh), but for now a printer reboot will do the trick. I also got to see a little more under-the-hood thanks to ProcMon.
- Press & hold the Windows button until it vibrates. Then press & release the volume down button. The screen will dim for a moment. (You can also press them both at the same time if you time it right.)
- On the Type Cover press Fn+Windows+Space.
All screenshots are saved in Pictures>Screenshots.
When trying to log into the AutoLab vCenter server with the vi-admin account you get an error that says, “The vSphere Client could not connect to vc.lab.local. You do not have permission to login to the server: vc.lab.local”.
Cause – The vi-admin account does not have Administrator permissions in vCenter.
Solution – Log in using the email@example.com account with a password of VMware1.lab. That account info is missing from the AutoLab documentation. Once logged in you can assign the vi-admin account Administrator permissions to vCenter.
When installing Windows Server 2012 R2 on a VM (vSphere or Hyper-V) configured for EFI you may receive the following error when booting to the ISO. “Windows failed to start. A recent hardware or software change might be the cause. To fix the problem… File: \EFI\Microsoft\Boot\BCD. Status: 0xc000014c. Info: The boot Configuration Data for your PC is missing or contains errors.”
When loading the VMware Paravirtual SCSI driver you receive an error that says, “No new devices drivers were found. Make sure the installation media contains the correct drivers, and then click OK.”
The installation cannot load any SCSI driver & says, “A media driver your computer needs is missing.”
“No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.”
Cause - Corrupted ISO
Solution - Re-download the ISO & try again. In my experience ISOs can become corrupt if you pause them when downloading.
Ever need to wake up a computer on a subnet that the “magic” packet can’t reach? Use PSEXEC to remote to a powered on computer on that subnet then run WOL.
psexec \\computername -c wol.exe mac_address
PSTools – http://www.sysinternals.com
When trying to delete a folder you get an error that says, “An unexpected error is keeping you from deleting the folder. If you continue to receive this error, you can use the error code to search for help with this problem. Error 0x80070091: The directory is not empty.”
Problem is the directory is empty. After a reboot you still get the error.
- Right click the drive that the folder is on & click Properties.
- Select the Tools tab.
- In the Error checking frame click Check.
- When prompted click Scan and repair drive. (Damn forgot to take a screenshot)
- On the Your drive was successfully repaired screen click Close.
- Press Additional Functions.
- Press 2 & 8 at the same time.
- Press Additional Functions.
- Press Copier.
- Press Function.
- Press Clear.
- Press PWD-CLR.
- Press OK.
Windows 8.1 Pro with the Hyper-V Role installed. One physical NIC with a static IP address.
Configure an External Virtual Switch bound to the physical adapter.
Virtual machines can get to the Internet just fine but the Hyper-V server cannot.
Hyper-V server can’t even ping Bing.
Hmmmm…can’t even resolve bing.com. Looking at the IPv4 properties of the vEthernet (External) NIC there is no DNS configured.
Add the IP of the router (or whatever DNS server you use) back in for the DNS server(s). Now the Hyper-V server can access the Internet.
When creating the External Virtual Switch a dialog box popped up that said, “Pending changes may disrupt network connectivity. This computer may loose blah, blah, blah”. But then it says, “These changes also may overwrite some static changes. If that happens, you must reapply the static changes to restore network connectivity.”
So there you go. When configuring Hyper-V to use a NIC that has a static IP configured you may loose some or all of it when it moves those settings to the vEthernet NIC.
When booting a Dell OptiPlex 760 to Darik’s Boot and Nuke (DBAN) you receive a few messages/errors that say:
- BIOS EDD facility v0.16 2004-June-25, 0 devices found
- EDD information not available.
- Warning: unable to open an initial console.
Solution – Upgrade the BIOS to A15 then try again.