win xp is not taking ip address from dhcp server

Originally Posted by Bender

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

Thats not my style see my PM

[amit_bngn]

Originally Posted by nash

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.

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

[nash]

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?

[gazzae]

Originally Posted by nash

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?

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

[mrmistoffelees]

Originally Posted by gazzae

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

Not true if network access control or similar is implemented

[Jon T]

Originally Posted by gazzae

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

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

[gazzae]

Originally Posted by mrmistoffelees

Not true if network access control or similar is implemented

Originally Posted by Jon T

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

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

[mrmistoffelees]

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

[amit_bngn]

Originally Posted by gazzae

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

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 ----------

Originally Posted by gazzae

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

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

[popper]

Originally Posted by amit_bngn

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.

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.