DHCP server unreachable

  • Thread starter Thread starter Vicente
  • Start date Start date
V

Vicente

I have a network (workgroup)running W2K server and
W2KSP4. One workstation is acting diferent, the others are
working fine, can connect to the internet and see each
other.
The computer with problems cannot connect to the internet
but can ping the others computers (but no the server),
when type ipconfig /release I got the message "All
adapters bound to DHCP do not have DHCP addresses. The
addresses were automatically configured and cannot be
realeased" and with ipconfig /renew "The following error
ocurred when renewing adapter local area connection: DHCP
server unreachable".
I looked the setings of the adapters in the others
computers and are the same.
Thanks in advance for your help.
 
Vicente said:
I have a network (workgroup)running W2K server and
W2KSP4. One workstation is acting diferent, the others are
working fine, can connect to the internet and see each
other.
The computer with problems cannot connect to the internet
but can ping the others computers (but no the server),
when type ipconfig /release I got the message "All
adapters bound to DHCP do not have DHCP addresses. The
addresses were automatically configured and cannot be
realeased" and with ipconfig /renew "The following error
ocurred when renewing adapter local area connection: DHCP
server unreachable".
I looked the setings of the adapters in the others
computers and are the same.
Thanks in advance for your help.
Click to expand...

Your IP address is manually assigned so IPCONFIG /release wont work. If all
the PC's on the network use DHCP then set the faulty one to obtain it's IP
by DHCP.

You can get all the help you need to do this if you aren't sure by typing
DHCP in the Help box found at Start-Help

Jud
 
It sounds like it may be an automatically configured 169.* address. These
are configured in the event that the workstation cannot reach a DHCP Server
to obtain an address.

If this is the case, can you determine for sure that the DHCP Discover
packets are reaching the DHCP Server ?

--
==============================
Chris Edson
(e-mail address removed)

This posting is provided "AS IS" with
no warranties, and confers no rights.
===============================
 
I am having the same problem, what should I do?
My IP Address is now within that 169.* range, when
normally the computer takes it from the DHCP.
My Mask is now 255.255.0.0 all my settings change and even though the computer is set up to automatically choose the IP address, It does not work.
I have one PC acting this way, the rest are fine.
 
I have the same problem, 3 computers all with XP, all configured the same, one stopped being able to get at DNS/IP address and can not connect but the rest work normally....I have tried everything from reintalling XP to new nic, even reset bios... HELP

(e-mail address removed)
 
Capture the network traffic at your DHCP Server to determine if the DHCP
request messages (Discovers, Requests) are reaching the DHCP Server. That
is the first step in troubleshooting these problems...

Then post your results here (I'm back from vacation, so I'll try to watch
this group more closely now!)

--
==============================
Chris Edson
(e-mail address removed)

Upcoming Tech Chat !
August 24, 1:00-2:00p Pacific
DHCP: Configuring and Deploying DHCP with Windows Server 2003 Part 2
Join the DHCP test team as we talk about any questions, concerns, or
recommendations you might have for DHCP Server in Windows Server 2003.
Chat Room:
http://communities2.microsoft.com/home/chatroom.aspx?siteid=34000015

Transcript of previous chat:
http://www.microsoft.com/technet/community/chats/trans/network/net1120.mspx

This posting is provided "AS IS" with
no warranties, and confers no rights.
===============================
 
It turns out it was the ISP with the problem in my case, unfortunately this
was after I completely disassembled and reformated my entire system LOL.
Anyway, the ISP did a "line check" and said the line was "noisy" and "cleaned
it up" whatever that means, and now all 3 computers work fine. I wish they
would have done a more comprehensive check before i tore my whole system
appart, but they kept pointing the finger saying "if one can connect the
problem is not us, it's on your end" (which obviously was not the case).

PEACE
 
Back
Top