New
#11
Ok, attached is one of my problem child laptops ms32 info. I've uploaded as a txt file, because it did not like the .nfo format to upload
Ok, attached is one of my problem child laptops ms32 info. I've uploaded as a txt file, because it did not like the .nfo format to upload
We are seeing identical "funkiness" on windows 2008 R2 servers. All have latest patches. Firmare on newest is latest and greatest from IBM, but older serves may be up to 6 months behind on firmware, not patches. We notice the funkiness starts at different times, but generally the most common problem occues after a reboot for patches (that happoens monthly). My latest problem occurred on a brand new server, with all of the latest patches from Microsoft and firmware/drivers form IBM, using Sophos as the AV and using a standard IBM image we use again and again. Most of the time there is no issue. Then, without warning, our application folks call is to say their app is not working and names do not resolve in DNS. Fix works every time running netsh windsock reset and a reboot. If it was our image or our procedure for building these servers, then I would expect it to happen on all of these. But it hits randomly and on different servers across different subnets with different firewalls. Sure smells like a winsock issue and not our configuration. Common pieces of the puzzle are Windows 2008 R2, reboots, Sophos AV, latest patches and firmware.