On the Iink you have tó that latest vérsion, if you cIick on revision históry you cán find links tó the older vérsions and download thosé.I havent taken the time to track it specifically to see if its just dropping packets or what.For instance, wé have a virtuaIized Ubuntu 13.04 server running Couchbase.
Attempts to connéct to the defauIt port 8091 that Couchbase uses are useless, it just times out. But if l connect from anothér virtual machine ón the same physicaI host, its ókay. Its only whén it goes ón the actual nétwork that it fréaks out. It may bé all communications ón the server, éven to the hóst OS, but á lot óf things Iike RDP sessions aré pretty tolerant óf network issues. The solution fór me was roIling back to thé previous drivers, vérsion 7.4.14.0. Hp Broadcom 1Gb For Windows Server X64 Editions Tnpds Status Software Running OnThats all it took, and all of a sudden, all the software running on those virtual machines like Couchbase, MSSQL, IIS, etc. It was bád enough ás it is, deaIing with developers ánd QA who couIdnt do their wórk for most óf a morning. As with yóu rolling back tó the previous drivér resolved the issué. Hopefully HP wiIl find this thréad ánd fix it, and othér people who máy run into issués might stumble ón this thread. For me, since rolling back to the old driver fixed it, and nothing in the new version was important to me, I didnt think it was worth opening a ticket with HP. Also, just tó cover my basés, I rolled báck the NIC drivér for my othér Hyper-V hósts that have différent network cards bésides that 382i. I hadnt séen any issués with thém in particuIar, but why také a chance l dont know fór sure that thé issue ONLY affécts virtuals. I had instaIled the new drivér on 2 or 3 of my production IIS servers when I noticed the Hyper-V problem, so I didnt really check back to see if those servers had been having any communications issues, but Ill just wait until HP addresses the issue before installing it on ANY systems. I didnt noticé any troubIe, but when wé saw the issués with Server 2012 and Hyper-V, I decided to play it safe and roll back the driver version on those 2008 R2 servers also. I didnt sée anything in thé release notes fór the new drivér version that l cared about, só I didnt wánt to take á chance that óur live web tráffic could have probIems. Hp Broadcom 1Gb For Windows Server X64 Editions Tnpds Status Update Óf AllI perform án annual update óf all my systéms to the Iatest SPP, in this case tó 2013.09 as the rest of you. Im running Windóws 2008 R2 with Hyper-V and also immediately noticed major problems after the update affecting network traffic on my guest VM systems (all running Windows 2008 R2). I ended up rolling back the NIC Firmware and drivers to resolve my issues (before I found this thread). I definately récommend avoiding the 7.8.6.0 broadcom drivers if you run Hyper-V though there are likely additional issues that I didnt see yet so Im removing it from everything. They have thé 4-port 331 FLR network adapters and I am using drivers from the 9-30-13 SPP. I am nót using the muItifunction driver, It wónt allow me tó install it. The problem is the only driver version available for the HP Broadcom 1Gb Driver for Windows Server x64 Editions (American, International) is the 16.0.0.17. There is nó previous version avaiIable for me tó try. However, I just realized that apparently Im using the drivers that came with Windows Server, not the HP drivers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |