I recently had to setup many Epson TM-T88V receipt printers for a POS installation and out of the box they are configured with a static address of 192.168.192.168. Pressing the reset button for 3 seconds prints out the status of the printer including the MAC address so I though I would just use arp –s to configure the printers but I received an error. So after a some googling with Bing I turned up this article that pointed me to the the fact that you need to use netsh with recent versions of Windows.
First you need to get the name of the interface that the device is connected to. Then you execute the netsh interface ipv4 add neighbors command.
netsh interface ipv4 show interfaces
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
3 10 1500 connected Ethernet
1 50 4294967295 connected Loopback Pseudo-Interface 1
63 10 1400 connected vowire hosting
10 5 1500 connected vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Sw
29 10 1500 connected vEthernet (VirtualBox Host-Only Ethernet Adapter Virtual Switch)
netsh interface ipv4 add neighbors "Ethernet" 10.1.10.45 xx-xx-xx-xx-xx-xx
This weekend we were migrating a Hyper-V cluster form Windows Server 2008 R2 to Windows Server 2012. Our hosts were HP DL360p Gen 8 servers connected to a HP P2000 G3 MSA iSCSI storage array.
After getting our hosts all configured and connected to the SAN we were ready to install the cluster. When we ran the Cluster Validation Wizard we received some warnings. One of warnings seemed quite troubling.
Test Disk 0 does not support SCSI-3 Persistent Reservations commands needed to support clustered Storage Pools. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.
This appears to be a big problem because SCSI-3 Persistent Reservations are very important to the cluster working correctly.
Well, I finally got around to figuring out why I could not install the Windows 8 Release Preview on my Lenovo ThinkPad W520. Every time I went to install the OS it would hang during boot. That issue turned out to be that I needed to install on a GPT disk using the UEFI bios.
Before doing that I installed the latest bios from the Lenovo site.
After upgrading the Bios and backing up the little data I wanted to save, I proceeded to install the OS. I went through the boot process fine, installed the installation files reboot and then hung at 90% when configuring devices. After fiddling with the video driver settings Optimus, Integrated and Discrete, I tired disabling the wireless card and the install completed successfully.
After the installation was complete, I installed the Lenovo Windows 8 beta drivers turned the wireless adapter back on, crossed my fingers and rebooted and I am finally running Windows 8 on my Lenovo W520!
Update: After installing all the Windows 8 drivers there was one unknown device. Turns out it was the ThinkPad Power Management Device. I downloaded the Windows 7 driver from the Lenovo site and everything seems good.