win xp is not taking ip address from dhcp server

amit_bngn · 27-10-2008, 16:03

I am using winxp SP2 in my laptop and i am using Realtech 8139 nic driver.again i am using a dhcp server which is on windows 2003 server.now
whenever i assigned to take ip address automatically it takes 169 range ip address whereas i am using 192 range ip address. now we have got more than 70 client pc using XP.
I face this problem particularly on laptops.
As I am the system admin of my organisation i have a good knowledge in windows.and I try almost everything but cant find any solution.Even in windows support also there is not any exact solution.

nash · 27-10-2008, 17:05

Have you previously joined these laptops to the Domain, and set up DNS? And now theyr'e failing. Or are you trying to join them? More details please.

SimpleSimon · 27-10-2008, 22:51

Are you using wired or wireless network connections?

If you are using wired then a 169 address means you have a good network connection to the switch but the machine could not find a DHCP server.

What scope have you set up on the DHCP server?

Does it have enough IP addresses to give out to the number of machines you have?

Simon

27-10-2008, 23:08

If its : 169.xxx.xxx.xxx = PC issue. Could be USB / NIC drivers, or TCP/IP corruption

idi banashapan · 28-10-2008, 00:19

Quote:

Originally Posted by whydoIneedatech

If its : 169.xxx.xxx.xxx = PC issue. Could be USB / NIC drivers, or TCP/IP corruption

not really... an APIPA address merely means that a DHCP server cannot be contacted whilst the machine is set to automatically obtain an address from a DHCP server. It could be for any number of reasons, not necessarily a PC issue. the machine will then assign itself an address with the 169.254.0.1 through 169.254.255.254 range on a subnet of 255.255.0.0. The machine will continue checking for a DHCP server and if it finds one, will reassign an IP to what it is given.

---------- Post added at 23:19 ---------- Previous post was at 23:07 ----------

simplesimon is right to suggest checking your scope to ensure there are enough IPs free, but that should not really give you an APIPA address assignment without an error stating the DHCP is out of scope addresses. all the same, try reducing the lease time of your scoped IP range to something like 2 hours (i think default is something like 8 days). This means if a renewal request is not sent for that IP in that time, the IP will be free for another device to use.

have you looked in the event log for any further info?

check your network settings to ensure you have configured your DHCP addresses correctly on the machine in question. it may be looking for the DHCP on the wrong IP, or indeed, not at all.

trya different cable and port too - preferably using a physical connection from a known working device.

28-10-2008, 01:20

Quote:

Originally Posted by Bender

not really... an APIPA address merely means that a DHCP server cannot be contacted whilst the machine is set to automatically obtain an address from a DHCP server. It could be for any number of reasons, not necessarily a PC issue. the machine will then assign itself an address with the 169.254.0.1 through 169.254.255.254 range on a subnet of 255.255.0.0. The machine will continue checking for a DHCP server and if it finds one, will reassign an IP to what it is given.

---------- Post added at 23:19 ---------- Previous post was at 23:07 ----------

simplesimon is right to suggest checking your scope to ensure there are enough IPs free, but that should not really give you an APIPA address assignment without an error stating the DHCP is out of scope addresses. all the same, try reducing the lease time of your scoped IP range to something like 2 hours (i think default is something like 8 days). This means if a renewal request is not sent for that IP in that time, the IP will be free for another device to use.

have you looked in the event log for any further info?

check your network settings to ensure you have configured your DHCP addresses correctly on the machine in question. it may be looking for the DHCP on the wrong IP, or indeed, not at all.

trya different cable and port too - preferably using a physical connection from a known working device.

The computer is Autoconfiguring its own IP so it is not able to talk to the internet or it would get a 192 IP or a public IP.

idi banashapan · 28-10-2008, 13:11

Quote:

Originally Posted by whydoIneedatech

The computer is Autoconfiguring its own IP so it is not able to talk to the internet or it would get a 192 IP or a public IP.

please read up on this. APIPA addresses are private addresses on a specific subnet. only APIPA adresses can talk to APIPA adresses. the reason the machine is using one of these is because it is set to determine it's IP from a DHCP server or distributer. the internet will not distribute the machine with an IP. the ISP will give the modem an IP which then allows the internal network to connect to the net through it. A DHCP server will distribute any IP specified in its scope. It will not necessarily be a class C address.

The ,machine cannot contact a DHCP server, but is configured to do so. that is the problem. the cause of the issue could be a cable, DNS server configuration locally, DNS cache locally, DHCP server itself, a router, a switch...

Guess you're learning why you do need a tech!!!!

Jon T · 28-10-2008, 13:16

Quote:

Originally Posted by whydoIneedatech

The computer is Autoconfiguring its own IP so it is not able to talk to the internet or it would get a 192 IP or a public IP.

Too little information to say anything for deffinate. I wouldn't say that the PC can't talk to the network, more that the DHCP server hasn't replied to a request, now that could be because 1) It's never been asked for anything 2) It has replied but the client device isn't recieving the replies. 3) It won't reply because the device isn't allowed to request an IP.

Easiest way of proving this would be to give one of the affected machines a static IP address outside of the DHCP scope, and then try and ping the DHCP server by it's IP address, if the ping times out, you may wantt to try pinging another statically adressed device on your network, if this works then you have basic IP unreachability issues on your DHCP server.

If pinging the DHCP box works, then I would strongly sugesst that you look at the configuartion of your DHCP server for any mac exclusions that may have been set, or maybe it's set to only hand out IP's to domain PC's and the PC's requesting the IP aren't on the domain. Also, have you authorised the DHCP server, have you accidentally got two DHCP servers on you network set to the same IP scope.

mrmistoffelees · 28-10-2008, 15:46

Whats the lease time for addresses being issued via DHCP and how many are being used in the scope ?

idi banashapan · 28-10-2008, 16:31

Quote:

Originally Posted by mrmistoffelees

Whats the lease time for addresses being issued via DHCP and how many are being used in the scope ?

already advised reducing the lease to 2 hours or so.

mrmistoffelees · 28-10-2008, 16:36

Quote:

Originally Posted by Bender

already advised reducing the lease to 2 hours or so.

Aah sorry bender

Wonder if NAC has somehow got itself implemented perhaps ?

idi banashapan · 28-10-2008, 16:45

possible that NAC is involved I suppose if pre-admission is set for something like antivirus signatures. good point!

28-10-2008, 17:32

Quote:

Originally Posted by Bender

please read up on this. APIPA addresses are private addresses on a specific subnet. only APIPA adresses can talk to APIPA adresses. the reason the machine is using one of these is because it is set to determine it's IP from a DHCP server or distributer. the internet will not distribute the machine with an IP. the ISP will give the modem an IP which then allows the internal network to connect to the net through it. A DHCP server will distribute any IP specified in its scope. It will not necessarily be a class C address.

The ,machine cannot contact a DHCP server, but is configured to do so. that is the problem. the cause of the issue could be a cable, DNS server configuration locally, DNS cache locally, DHCP server itself, a router, a switch...

Guess you're learning why you do need a tech!!!!

Quote:

Originally Posted by whydoIneedatech

If its : 169.xxx.xxx.xxx = PC issue. Could be USB / NIC drivers, or TCP/IP corruption

So I said that above, which is along the the lines of what is now in bold and you say no to that and now you say yes, very strange.

I have read up on APIPA addresses and they do follow what you say but also that it can be as I said, I just had a look at a few different articles, which were very interesting and food for thought, thanks.

mrmistoffelees · 28-10-2008, 17:49

Quote:

Originally Posted by whydoIneedatech

So I said that above, which is along the the lines of what is now in bold and you say no to that and now you say yes, very strange.

I have read up on APIPA addresses and they do follow what you say but also that it can be as I said, I just had a look at a few different articles, which were very interesting and food for thought, thanks.

There are times to advise. Then there are times to listen, this for you my friend is a time to listen

(or read in this instance)

idi banashapan · 28-10-2008, 18:00

Quote:

Originally Posted by whydoIneedatech

So I said that above, which is along the the lines of what is now in bold and you say no to that and now you say yes, very strange.

The only reason I pulled up on this was because the comment I was initially referring to implied that the issue was with the PC, but that is not necessarily the case. although possible the issue could be local on the client, I didn't want to OP to look no further than the client when the issue could be any part of the network from client to DHCP.

Quote:

Originally Posted by whydoIneedatech

I have read up on APIPA addresses and they do follow what you say but also that it can be as I said, I just had a look at a few different articles, which were very interesting and food for thought, thanks.

We're all here to help each other. I'm glad you read up instead of posting retaliatory 'my-knowledge-out-does-yours' stuff!!