- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Win2003 static IP problem with DHCP
ProLiant Servers - Netservers
1753884
Members
7546
Online
108809
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
05-04-2006 09:31 PM
05-04-2006 09:31 PM
Win2003 static IP problem with DHCP
Hi,
I have a ProLiant BL25p running Windows 2003 Standard SP1 that has an unusual network problem. Two of the four NIC's are teamed together (TLB, TCP method) and have a static IP address assigned to the team. At the moment only one of the NIC's is connected to the network as a new network is currently being provisioned (i.e. not ready yet).
The problem is that the machine will work fine for a while, and then it will drop off the network. Connecting to the console via iLO, I can see (via the icon in the task bar) that the machine is performing a DHCP request. Doing an ipconfig /all shows that the team isn't configured for DHCP and that it's currently got an IP address of 0.0.0.0 (i.e. not what I set it to). Doing an ipconfig /release says that the command is not supported as none of the interfaces are configured for DHCP.
If I disable the (virtual) teamed NIC and then enable it again all is fine. The old IP is back and everything works fine. I've tried breaking the team and assigning static IP addresses to the two physical NIC's and then recreating the team (on the off chance it was one of them making the DHCP request) but the problem still persists.
I have over fifty machines that are all identical and have been deployed via an RDP image, but this is only a problem on three of them. Hardware is identical, OS image is identical.
Any ideas would be appreciated!
Julian.
I have a ProLiant BL25p running Windows 2003 Standard SP1 that has an unusual network problem. Two of the four NIC's are teamed together (TLB, TCP method) and have a static IP address assigned to the team. At the moment only one of the NIC's is connected to the network as a new network is currently being provisioned (i.e. not ready yet).
The problem is that the machine will work fine for a while, and then it will drop off the network. Connecting to the console via iLO, I can see (via the icon in the task bar) that the machine is performing a DHCP request. Doing an ipconfig /all shows that the team isn't configured for DHCP and that it's currently got an IP address of 0.0.0.0 (i.e. not what I set it to). Doing an ipconfig /release says that the command is not supported as none of the interfaces are configured for DHCP.
If I disable the (virtual) teamed NIC and then enable it again all is fine. The old IP is back and everything works fine. I've tried breaking the team and assigning static IP addresses to the two physical NIC's and then recreating the team (on the off chance it was one of them making the DHCP request) but the problem still persists.
I have over fifty machines that are all identical and have been deployed via an RDP image, but this is only a problem on three of them. Hardware is identical, OS image is identical.
Any ideas would be appreciated!
Julian.
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