- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Microsoft
- >
- DHCP failure
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО11-24-2002 07:40 PM
тАО11-24-2002 07:40 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2002 09:29 PM
тАО11-24-2002 09:29 PM
SolutionWhat do you see when you do a
netstat ???r
What does the device manager have to say about the stratus of the NIC?
Lance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2002 09:38 PM
тАО11-24-2002 09:38 PM
Re: DHCP failure
http://support.microsoft.com/default.aspx?scid=kb;en-us;313896
MS also had a good article on installing and working with static addresses with ICS that might be helpful.
http://support.microsoft.com/default.aspx?scid=kb;en-us;309642
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2002 05:37 PM
тАО11-25-2002 05:37 PM
Re: DHCP failure
I don't think it's the NIC itself, since it works when I use a static IP address (e.g. 192.168.0.2). The fact that the loopback ping doesn't work is still a mystery, but I don't think that's a reason to suspect the NIC, since loopback pings are usually just returned within the IP stack. The fact that ICS also uses the 192.168.0 network sounds interesting. I'm supposedly not using ICS anymore, but I'm thinking that there is some remnant around and there's a conflict with the router. On this theory, I tried assigning 10.1.0.1 to the router, but I still get the same result when I try to use DHCP. BTW, I have another XP machine where DHCP works fine, but I also can't ping 127.0.0.1. I'm going to check the XP service pack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2002 05:41 PM
тАО11-25-2002 05:41 PM
Re: DHCP failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2002 06:27 PM
тАО11-25-2002 06:27 PM
Re: DHCP failure
ipconfig /all
would still work. Go to the one which works and get the results of ipconfig /all. Then go to the bad one and put the same info into the TCP/IP setup but add one to the last octave of the IP address and don't forget the DNS, mask, and gateway. That should work. If it doesn't then remove TCP/IP, reboot and then reinstall TCP/IP.
I assume you are uptodate on your patches. XP needs a lot of them. http://windowsupdate.microsoft.com
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2002 09:00 PM
тАО11-25-2002 09:00 PM
Re: DHCP failure
Lance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 07:42 AM
тАО11-26-2002 07:42 AM
Re: DHCP failure
The 169.254.x.x is just the default number that Windows uses when it doesn't get a reply from a DHCP server.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 10:18 AM
тАО11-26-2002 10:18 AM
Re: DHCP failure
Lance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 10:44 AM
тАО11-26-2002 10:44 AM
Re: DHCP failure
Actually, tho they never said so in networking class I've ever taken, 169.254 is a legal address for just this purpose. From RFC 3330:
169.254.0.0/16 - This is the "link local" block. It is allocated for
communication between hosts on a single link. Hosts obtain these
addresses by auto-configuration, such as when a DHCP server may not
be found.
If you do a whois on it it comes up as blackhole and refers you to RFC 3330.
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 11:27 AM
тАО11-26-2002 11:27 AM
Re: DHCP failure
Lance