- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: NC3163 Network Adpater
ProLiant Servers (ML,DL,SL)
1748108
Members
4977
Online
108758
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2001 04:00 PM
06-03-2001 04:00 PM
NC3163 Network Adpater
Windows 2000 still detects and activates the onboard NC3163 when I install Windows 2000 server, even though I disable the adapter during the SMARTstart phase. This is causing problems with the unattended installation as it applies the IP settings to that adapter instead of the NC3134 I want to use. I also see the same problem on ML370s
Any way round this ?
Chris O'Neill
Any way round this ?
Chris O'Neill
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2001 04:00 PM
06-04-2001 04:00 PM
Re: NC3163 Network Adpater
I have had similar problems with the DL360 and SMARTSTART. The DL360 has dual integrated NC3163 and the second controller always came up first and applied the settings I gave to it. My only solution was to use Manual Assist mode of SmartStart. Plus doing this allows me to let the W2K install create my large boot partitions >4095. SmartStart in AUTO mode puts the disk partition in non-extended <4096. In the W2K install make sure to select custom settings when it comes time to setup the network otherwise you'll experience the same problem. In my case the second controller still comes up, but now I can uncheck the protcol(s)/service(s) running on that controller (don't uninstall otherwise they will be uninstalled on the other controllers as well), then go on the next one which happens to be the first controller.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP