how a new client can get an IP addresse from DHCP ?


i have windows server 2003 which has DHCP server and three computers are attached to this server.

i added another computer to this domain.
the new computer has windows xp pro and to join the domain i gave it manually an IP address and DNS address. and it joined the domain. but the new computer does not get IP address automatically from the DHCP server why?

what should i do for the new computer to get automatically an IP address from DHCP server?
mkhalidmnAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Big5250Commented:
If you manually set the ip to join the domain it's still set to a static address unless you went back in and changed the interface to DHCP.  If you have done that, verify that you have enough IP addresses in your lease pool.
mkhalidmnAuthor Commented:

i went back and changed it to automatically address but it doesnt help and i get the private address which is 168.156.0.0 or somthing like that.....and i have plenty of addreses in the scope.
Big5250Commented:
It's most likely 169.x.x.x which is the range which is auto assigned by MS when a DHCP server doesn't respond in the alloted time.  If you drop to a command line and do an "ipconfig /release" then do an "ipconfig /renew"  what happens?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

mkhalidmnAuthor Commented:

i will try this when i go home ... right now i m in the libarary, if it works u will get ur point :) but tommorrow
Big5250Commented:
good luck
JacquesKrugerCommented:
Did you authorize the DHCP server to issue addresses?
mkhalidmnAuthor Commented:

JacquesKruger.

yes and it gives address to other PCs
JacquesKrugerCommented:
Are you using wireless lan?
Are you using any internet security suit? If you are make sure that the firewall component on this will allow DHCP transmissions.
mikeleebrlaCommented:
just to clarify if it is 169.254.x.x then it is an APIPA (Automatic Private IP Addressing) address which means your workstation can't "see" a DHCP server. There are many 169.x.x.x that are valid PUBLIC addresses however, only 169.254.0.0 - 169.254.255.255 is the APIPA range.

when you assign it statically to an address on your network, can you ping the IP address of your DHCP server?
mkhalidmnAuthor Commented:

mikeleebrla.

yes i ping it without any problem when i assign it statically ... i mean i ping the domain name and the IP address of it without any problem
mkhalidmnAuthor Commented:
JacquesKruger

i dont use wireless land or internet security suites
mikeleebrlaCommented:
thats odd, b/c all that happens when a workstation requests a DHCP address is it sends a broadcast out on your networking looking for any DHCP server, the first one that responds back assigns the workstation the DHCP address.  what OS is this workstation?  does it have any firewall turned on? if it does disable it b/c it might be blocking the DHCP "offer" and/or "acknowledgment"
mkhalidmnAuthor Commented:

mikeleebrla

as i said the workstation is windows xp pro and there is no firewall to be turned on
2hypeCommented:
Is your DHCP Server setup so only clients which you have registered there MAC Addresses and Set up particular IP Addresses to be assigned?
ragnarok416Commented:
Check in the DHCP configuration and make sure that there is no screwups to do with address reservation.  I have had this same problem when someone on my network was screwing around and manually assigned a reserved IP address to his computer.  You will get something that says BAD_ADDRESS in the reservation area on the DHCP server.
JacquesKrugerCommented:
Another thing, make sure you have enough available addresses in your scope.
rikke_vpCommented:
Hi,

its a real problem on a 2003 server. Most of the time this is a corrupt DHCP database is corrupt. Try flushing the DHCP or just delete the database...

Note that you need to stop your dhcp server
and please make a BACKUP of the database!!

net stop dhcpserver or via services.msc
then delete the database
net start dhcpserver or  via services.msc

when you restart the server dous a rebuild of the database. what I should do afterworths is rebooting my systems. See that you get a ip then.


Regards,

Rikke

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.