win xp is not taking ip address from dhcp server
 

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.

Re: win xp is not taking ip address from dhcp server
 

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.

Re: win xp is not taking ip address from dhcp server
 

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

Re: win xp is not taking ip address from dhcp server
 

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

Re: win xp is not taking ip address from dhcp server
 

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.

Re: win xp is not taking ip address from dhcp server
 

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.

Re: win xp is not taking ip address from dhcp server
 

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!!!! ;)

Re: win xp is not taking ip address from dhcp server
 

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.

Re: win xp is not taking ip address from dhcp server
 

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

Re: win xp is not taking ip address from dhcp server
 

already advised reducing the lease to 2 hours or so.

Re: win xp is not taking ip address from dhcp server
 

Aah sorry bender :)

Wonder if NAC has somehow got itself implemented perhaps ?

Re: win xp is not taking ip address from dhcp server
 

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

Re: win xp is not taking ip address from dhcp server
 

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.

Re: win xp is not taking ip address from dhcp server
 

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)

Re: win xp is not taking ip address from dhcp server
 

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.

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

Re: win xp is not taking ip address from dhcp server
 

Thats not my style see my PM;)

Re: win xp is not taking ip address from dhcp server
 

This is the first time I am trying to add my laptop in the network.And Its a wired connection.

Re: win xp is not taking ip address from dhcp server
 

1: You need to create a user account on the Domain Controller.
2: Add the same user account to your laptop.
3: Make sure DHCP is set to auto.
As this laptop has not joined the domain then it is only logging on locally, hence the 169 ip address.
This should change as you join to the domain.
At what point are you checking the ip address?
Are you doing any of the above?

Re: win xp is not taking ip address from dhcp server
 

How are you going to join the domain with a 169 address?

Plus a DHCP server will give an address to whatever requests one, not just members of a domain

Re: win xp is not taking ip address from dhcp server
 

Not true if network access control or similar is implemented

Re: win xp is not taking ip address from dhcp server
 

That depends on if the network uses some form of pre-IP level authentication, such as NAC or Radius on the DHCP servers.

Re: win xp is not taking ip address from dhcp server
 

Is this the OPs setup? I must have missed it. I assumed he would be using the standard windows DHCP server

Re: win xp is not taking ip address from dhcp server
 

Not sure but he has not ruled it out yet so it's a possible

Re: win xp is not taking ip address from dhcp server
 

I am trying to log in with Administrator account.Now how can i join my laptop in the domin if its only getting a 169 ip whereas my network runs on 192 ip.
and if u say that put an static ip in the laptop and then join it in the domain and then again check whether i am getting ip automatically or not.
Let me inform you that i alredy perform this step but trying to get a ip automatically from dhcp server is not resolved

---------- Post added at 13:15 ---------- Previous post was at 13:09 ----------

I m simply using a dhcp server on win 2003 nothing more than that no nac no authentication no firewall nothing.

Re: win xp is not taking ip address from dhcp server
 

so your saying (as a test), you have manually assigned them a static IP ,gateway,DNS address etc and THEY THEN WORK FINE?
you can then get on the LAN and do as you expect etc.....you need/want them to also work with DHCP as they should do already.

right, its not possific to your problem as such, but iv seen this work for the VM cable modem to wired ethernet MAC No.s that are set for a generic 00.00.00.00 and getting this windows OS 192 ip problem every time, so it will potentially work as a fix for your windows domain problem too.

the windows OS has some form of errata as related to this wired 00.00.00.00 MAC, iv never worked out exactly why, but heres potentially a simple fix you can try.

check your problem cards(s) are of the generic 00.00.00.00 MAC type and simply give/assign them another MAC No. instead.

some wired ethernet cards than are using 00.00.00.00 as their generic MAC dont seem to talk in the official spec, it only seems to effect wired Ethernet cards as all the 00.00.00.00 USBto ethernet bridges sticks iv tryed perfectly work fine with the VM cable modem in gettign a valid DHCPd given IP No etc.

its assumed this windows DHCP/d problem goes far deeper, so just change the base MAC No. in the registry to something better but valid and report back if it fixed this problem for you?, if it did, then MS need to work out why their code is breaking DHCPd requests and fix it.

you can boot and use a simple Slax liveCD with these RTL 8139 for a quick test, and you should see them connect to your domain, send the Multicast request and get it given back with your valid DHCP packets etc.

and the slaxCD will give you a valid new MAC to use at the same time as it overrides/replaces the default wired 00.00.00.00 MAC No. as a default action so you dont have to make your own up.

boot, log in as root, password as toor

http://www.slax.org/

iv mentioned this VM CM problem many times before and changing its default MAC has never failed me yet to resolve the very common windows OS 169 ip problem, perhaps it will also solve your windows faulty app/OS code problem.