DHCP

0 pts.
Tags:
Networking
I've got a machine that has been autoconfiguring its IP to a default 169.254.x.x 255.255.0.0 address. I have verified that it has a good connection to our network and DHCP is running on the server. Any ideas?
ASKED: September 13, 2004  9:51 AM
UPDATED: September 13, 2004  12:50 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Rmartinez78,

169.254.x.x is the APIPA feature in windows that is used when a client cannot contact a DHCP server. Can other clients on your network receive IP addresses?

Are you able to ping your DHCP server? Is your DHCP service up and handing out IPs? Do you have a host file that could be interfering w/ the route?

Discuss This Question: 7  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • KajBre
    You don't say which oper. system you are running ? If you have a Win NT/2000/XP workstation, you could first start checking the problem by issuing command "ipconfig /all" at command prompt, and then look for reference for DHCP and DNS servers (if you have DNS server) and also check that DHCP is actually in use. Which network services or servers are trying to access: - Internet connection via xDSL ? - Internal (Windows)server ? - Other ? Kaj Bredenberg
    0 pointsBadges:
    report
  • Tinners
    Make sure that the Default Gateway has been set correctly in the TCP/IP Advanced Properties.
    0 pointsBadges:
    report
  • Bridgeman
    You do not say how you have checked the connection to state that this is not the problem. You could try assigning a fixed IP address to start with and pinging the DHCP Server. This will confirm that the connection is indeed OK. Have you also checked that the DHCP Server is actualy running and handing out new IP Addresses. If all this fails then try different cables Network cards Etc. to try and illiminate the problem
    25 pointsBadges:
    report
  • Rmartinez78
    Thank you for your prompt responses. Here is the environment: The problematic machine is running W2K Pro. I have 3 domains with 3 NT DC's(ancient) with a trust set up between the 3. However, DHCP is only running on one DC, but we have not had problems in the past. I have tested the network connection with a siemon cable tester connected to a remote module. I have verified that DHCP is running on our DC and handing out IP's because all of my other clients are able to obtain an IP. I have verified that the default gateway is set; checked ipconfig /all, DHCP and DNS are both in use. The client is connecting to an internal Windows NT DC. I am unable to ping the server because the client is on a different network (169.254.x.x). Your thoughts?
    0 pointsBadges:
    report
  • Duduspace
    I have had a similar problem which I have not been able to solve. It involved a Windows XP machine CompaQ laptop with an integrated NIC (National Semiconductor Corp DP83815/816 10/100 MacPhyter PCI). All other PCs on the network segment obtained IP Addresses from the DHCP server apart from the laptop in question (All were connected to a 3 Com switch). I ultimately had to move the laptop to another network segment, it just just refused to communicate on that network segment. I also checked Duplexing and Media type on the Network Card properties. I ended up fiddling with the packet buffer settings to no avail before giving up and moving the PC to another segment which had a 3 Com Superstack II hub. I have not verified this, but I feel it might have to do with the Ethernet implementation on the card.
    0 pointsBadges:
    report
  • Duduspace
    I have had a similar problem which I have not been able to solve. It involved a Windows XP machine CompaQ laptop with an integrated NIC (National Semiconductor Corp DP83815/816 10/100 MacPhyter PCI). All other PCs on the network segment obtained IP Addresses from the DHCP server apart from the laptop in question (All were connected to a 3 Com switch). I ultimately had to move the laptop to another network segment, it just just refused to communicate on that network segment. I also checked Duplexing and Media type on the Network Card properties. I ended up fiddling with the packet buffer settings to no avail before giving up and moving the PC to another segment which had a 3 Com Superstack II hub where it worked just fine. I have not verified this, but I feel it might have to do with the Ethernet implementation on the card. I would recommend you turning off Auto-negotiation on the NIC and being specific about your duplexing settings before concluding. It is very obvious, the client is not communicating with the DHCP server. Remember also that if the client is not on the same segment with the DHCP server, you might need to configure a DHCP Relay Agent on that segment.
    0 pointsBadges:
    report
  • JSilveira
    Several months ago I had a problem similar to yours. The PC was a brand new IBM working find one week then...nothing. The way the problem was resolved was to changed the link speed of the NIC card from Auto to 10 full duplex. I had to try different link speeds before finding the one that worked. Some NIC cards just can't auto-negotiate well with a switch. JSilveira
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following