- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Intel PRO 1000/MT has (today ?) no "full support" in Windows Server 2008 R2 ; that is : each NIC est recognized by OS and functionnal, but we can't built a team, because Intel Advanced Network Software (ANS) is not available.
More, on my DELL PowerEdge 2850 (with 4 PRO 1000/MT), no PCI-express slot, then i can't install more recent NIC which has full support (like 1000/PT).
A server hardware with server software and with server NICs but no server teaming functionality ?
Does it means I have to replace all my Intel NIC with Broadcom NIC which has teaming support in 2008 R2 ?
Thanks for your help
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you try the latest NIC driver? http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17910&ProdId=2248&lang=eng
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, of course.
But as you can see in doc, the PRO 1000/MT (model with PCI or PCI-X bus) is not supported (the 1000/PT, with PCI-express bus, is)
I verified that.
Anyway, thanks for your help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately the http://www.intel.com/support/network/adapter/1000mtserver/index.htm Intel® PRO/1000 MT Server Adapter will not be supported for initiating ANS teaming in Windows* 2008 R2. You can only team this adapter in a team that is initiated from an adapter that does have support for ANS teaming. See http://www.intel.com/support/network/sb/CS-030614.htm Is my Intel® Ethernet Adapter supported in Microsoft Windows Server 2008 R2*? for related information.
Since ANS teaming in Windows 2008 R2 is supported in the http://www.intel.com/network/connectivity/products/server_adapters.htm# s1=Gigabit%20Ethernet&s2=all&s3=PCI%20Express* PCI-Express* based adapters, if you have a PCI-Express* slot you could install one of those adapters for teaming, and you could include your older ports in the team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your response
But as you can see in my original post, my server hardware (Poweredge 2850, 2/3 years old) has no PCI-express slot.
So the question could be :
- will Intel release ANS software for 1000/MT in 2008R2 ?
- or should I change the NICs for another brand, like Broadcom, which has support
I don't understand why Intel will not support such current server config ...
Are the PRO1000/MT considered as obsolete (why is it sold then ?)
What is the strategy ?
Thanks for your job
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
Nothing new about my problem ?
Digest :
- Windows Server 2008 R2
- several Intel Pro 1000/MT single or dual ports
- those NICshave "in-box" only support ; each works fine with microsoft in-box driver
- need to make a team as I did with Windows Server 2003R2
- because of no "full-support", I can't install Intel ANS
- no PCI-Express slot on motherboard (then no xx/PT card possible to initiate a team)
What can i do ?
Thanks for your response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry for not answering sooner. Unfortunately, Intel has no plans to add teaming support for your adapters in Windows Server 2008 R2.Teaming is only supported in Windows Server 2008 and earlier for your adapters. There is nothing you can do to make teaming work with your adapters in Windows Server 2008 R2 with your server hardware. No Intel Ethernet adapters for PCI-x slots have teaming support for Windows Server 2008 R2.
From you earlier postings I understand your servers are only 2 to 3 years old. You might not have not given much thought to upgrading your server hardware, because the hardware is fairly new. But you might want to estimate the cost of keeping your old servers and buying new NICs compared to buying new servers with up-to-date technology. This kind of analysis is outside of my area of expertise, but I know our IT department calculated a big savings for Intel by upgrading to new servers versus keeping the old servers. The IT@ Intel site, http://www.intel.com/it/ http://www.intel.com/it/ has resources for explaining the reasons behind our upgrade decision including video (scroll down to the latest content) and a http://download.intel.com/it/pdf/Staying_Committed_to_Server_Refresh_FINAL.pdf whitepaper. A link to a savings estimator tool is included in the whitepaper.
As far as what NICs you can buy for your existing servers, I do not have any recommendations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes you CAN team Pro 1000 MT adapters. There is just a trick.
Download latest PROVISTAX64.exe & PROWIN7X64.exe from intel
Extract contents of both to separate directories.
Go to device manager and update drivers and select browse and point to the folder you had PROVISTAX64 extracted to (make sure seach subfolders is on) and the drivers will be updated.
Then go to the PROWIN7X64 directory/apps/prosetdx/win7_x64/ and run prosetdx.msi
Teaming will now be available. After you create a team allow it a minute to initialize before you assign a static IP.
Works great.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank You for this meathod. I have been trying to do this with my Dell Poweredge 2850 for months, now have a 6GB/s link
And on my Acer G330 Mk2 aswell (2GB/s Link )
Great tutorial, just wanted to say thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520092929 1073786111 9 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} a:link, span.MsoHyperlink {mso-style-noshow:yes; mso-style-priority:99; color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {mso-style-noshow:yes; mso-style-priority:99; color:purple; mso-themecolor:followedhyperlink; text-decoration:underline; text-underline:single;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {mso-style-priority:34; mso-style-unhide:no; mso-style-qformat:yes; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:.5in; mso-add-space:auto; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst {mso-style-priority:34; mso-style-unhide:no; mso-style-qformat:yes; mso-style-type:export-only; margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.5in; margin-bottom:.0001pt; mso-add-space:auto; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle {mso-style-priority:34; mso-style-unhide:no; mso-style-qformat:yes; mso-style-type:export-only; margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.5in; margin-bottom:.0001pt; mso-add-space:auto; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {mso-style-priority:34; mso-style-unhide:no; mso-style-qformat:yes; mso-style-type:export-only; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:.5in; mso-add-space:auto; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} span.EmailStyle16 {mso-style-type:personal; mso-style-noshow:yes; mso-style-unhide:no; mso-ansi-font-size:11.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; color:# 1F497D; mso-themecolor:dark2;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1632201765; mso-list-type:hybrid; mso-list-template-ids:-489772998 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;} @list l0:level1 {mso-level-tab-stop:none; mso-level-number-position:left; text-indent:-.25in;} @list l0:level2 {mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level3 {mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level4 {mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level5 {mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level6 {mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level7 {mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level8 {mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level9 {mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} -->
SOLUTION FOUND
1. Download the Intel Networking solutions CD v15.3 from here: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=879&DwnldID=19002&lang=eng http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=879&DwnldID=19002&lang=eng
2. Extract the files
3. Use device manager to update the drivers for the Intel Pro1000 MT NICs. I had to do each independently.
4. You can now run the ProSet install from V15.3_CD\APPS\PROSETDX\Winx64\ProSetDX.msi and it will succeed.
5. You will now see the TABS for Teaming etc in the properties of the NIC via Device Manager.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are a genious. The version numbers have changed, but everything worked exactly as anticipated.
pro*.exe /f /e
This will get the files extracted to where you need them.
Updated each adapter individually - If I remember, the changes I saw for the driver went from MS driver to Intel, the version number went down, but the release date was newer...not that it matters to me as long as it works and is stable.
Ran the ProSetDX.msi.
Thank you for your awesome post on how to get this going. I thought we'd not be allowed to roll any of our servers forward because of the loss of the teaming capability!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That CD doesn't exist on Intel's site anymore (shame on you Intel ).
After much searching I was able to find it at the link below. The files are clean and I was able to update the my drivers and team the NICS on R2. Sweet success!
http://www.lostmydrivers.com/driver/download/25242/Intel/Network-Drivers/INTEL-PRO-1000-MT-DRIVER-15.3-WINDOWS-XP-32-64-2003-32-64-VISTA-32-64-7-32-64-WINDOWS-VISTA-WIN20. http://www.lostmydrivers.com/driver/download/25242/Intel/Network-Drivers/INTEL-PRO-1000-MT-DRIVER-15.3-WINDOWS-XP-32-64-2003-32-64-VISTA-32-64-7-32-64-WINDOWS-VISTA-WIN20.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for this solution. Everything worked except I had to do a different step to install it. When I tried installing using the "ProSetDX.msi" I was getting permission issues and the GUI was a little messed up. Instead, I used the "DxSetup.exe", located in the same folder, and it worked perfectly. I'm running Server 2008 R2 Enterprise on a Dell PowerEdge 1850 with two integrated IntelPRO 1000MT NIC's.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page