PC Review


Reply
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average.

ipconfig unable to contact DHCP server

 
 
Steve
Guest
Posts: n/a
 
      30th Aug 2004
I've got a couple of computers connected to a router - 2
wired, one wirelss. The router is connected to a cable
modem. One of the wired computers running Windows XP
(service pack 2) will not connect. It keeps setting the
IP address at 169.254.xxx instead of 192.168.x.x.
I release and renew iconfig and it gives me the
message "an error occurred while renewing interface Networ
Bridge: unable to contact your DHCP server." I've ruled
out the router and modem - as the other computers work.
I've switced mobo and network card. No difference. I
even reloaded Windows XP and that fixed it for about two
weeks and then it went out again. I can manually set the
IP address for 192.168.x.x and that lets the computer
communicate with the other two computers, but it still
won't connect to the internet.
Thoughts?
 
Reply With Quote
 
 
 
 
Guest
Posts: n/a
 
      30th Aug 2004

>-----Original Message-----
>I've got a couple of computers connected to a router - 2
>wired, one wirelss. The router is connected to a cable
>modem. One of the wired computers running Windows XP
>(service pack 2) will not connect. It keeps setting the
>IP address at 169.254.xxx instead of 192.168.x.x.
>I release and renew iconfig and it gives me the
>message "an error occurred while renewing interface

Networ
>Bridge: unable to contact your DHCP server." I've ruled
>out the router and modem - as the other computers work.
>I've switced mobo and network card. No difference. I
>even reloaded Windows XP and that fixed it for about two
>weeks and then it went out again. I can manually set the
>IP address for 192.168.x.x and that lets the computer
>communicate with the other two computers, but it still
>won't connect to the internet.
>Thoughts?
>.


Steve,
I think that this is most likely a connectivity problem.
A 169.254 address is called a "PIPA" or Private IP
Address. This happens when the comp cant find a DHCP
server to give it an IP address. Since the trouble
computer is a wired one, try swapping everything you can
with the one that works. NIC card and ethernet cable
first. If that doesnt work, make sure that your dhcp
client service is enable. Administrative Tools -->
Services. Shoot me an email and let me know how it goes.
Kyle
(E-Mail Removed)
 
Reply With Quote
 
 
 
 
Steve Winograd [MVP]
Guest
Posts: n/a
 
      30th Aug 2004
In article <27a901c48e4d$65f55760$(E-Mail Removed)>, "Steve"
<(E-Mail Removed)> wrote:
>I've got a couple of computers connected to a router - 2
>wired, one wirelss. The router is connected to a cable
>modem. One of the wired computers running Windows XP
>(service pack 2) will not connect. It keeps setting the
>IP address at 169.254.xxx instead of 192.168.x.x.
>I release and renew iconfig and it gives me the
>message "an error occurred while renewing interface Networ
>Bridge: unable to contact your DHCP server." I've ruled
>out the router and modem - as the other computers work.
>I've switced mobo and network card. No difference. I
>even reloaded Windows XP and that fixed it for about two
>weeks and then it went out again. I can manually set the
>IP address for 192.168.x.x and that lets the computer
>communicate with the other two computers, but it still
>won't connect to the internet.
>Thoughts?


If you don't have a specific need for the Network Bridge, right-click
and delete it. Then, run ipconfig again to get an IP address for the
local area network connection.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Reply With Quote
 
Steve
Guest
Posts: n/a
 
      30th Aug 2004
Neither idea worked. I should add that when this first
happened, I put in a new mother board with a new
integrated network card and put in a new network cable.
That did not fix the problem. The only thing that worked
was to put in a new hard drive, reformat it, and load
windows XP on it. Of course, that meant I had to reload
every program on my computer, so I really don't want to do
that again. So I'm pretty sure its a Windows issue, but
can't tell what. BTW, I tried to recover Windows to a
couple of days before the outage and that didn't do
anything either.

Steve

>-----Original Message-----
>
>>-----Original Message-----
>>I've got a couple of computers connected to a router - 2
>>wired, one wirelss. The router is connected to a cable
>>modem. One of the wired computers running Windows XP
>>(service pack 2) will not connect. It keeps setting the
>>IP address at 169.254.xxx instead of 192.168.x.x.
>>I release and renew iconfig and it gives me the
>>message "an error occurred while renewing interface

>Networ
>>Bridge: unable to contact your DHCP server." I've ruled
>>out the router and modem - as the other computers work.
>>I've switced mobo and network card. No difference. I
>>even reloaded Windows XP and that fixed it for about two
>>weeks and then it went out again. I can manually set

the
>>IP address for 192.168.x.x and that lets the computer
>>communicate with the other two computers, but it still
>>won't connect to the internet.
>>Thoughts?
>>.

>
>Steve,
> I think that this is most likely a connectivity problem.
>A 169.254 address is called a "PIPA" or Private IP
>Address. This happens when the comp cant find a DHCP
>server to give it an IP address. Since the trouble
>computer is a wired one, try swapping everything you can
>with the one that works. NIC card and ethernet cable
>first. If that doesnt work, make sure that your dhcp
>client service is enable. Administrative Tools -->
>Services. Shoot me an email and let me know how it goes.
>Kyle
>(E-Mail Removed)
>.
>

 
Reply With Quote
 
Virtuoso
Guest
Posts: n/a
 
      30th Aug 2004
"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> In article <27a901c48e4d$65f55760$(E-Mail Removed)>, "Steve"
> <(E-Mail Removed)> wrote:
> >I've got a couple of computers connected to a router - 2
> >wired, one wirelss. The router is connected to a cable
> >modem. One of the wired computers running Windows XP
> >(service pack 2) will not connect. It keeps setting the
> >IP address at 169.254.xxx instead of 192.168.x.x.
> >I release and renew iconfig and it gives me the
> >message "an error occurred while renewing interface Networ
> >Bridge: unable to contact your DHCP server." I've ruled
> >out the router and modem - as the other computers work.


I had the same issue after upgrading to SP2. I used a wireless
connection that refused to get an IP address after the upgrade. In my
case it was that I had disabled my local network adapter (since I did
not use it anyway). But for some reason this does not work. If you
local network adapter is disabled it might cause wireless adapters not
to obtain IP addresses after the SP2 upgrade.
 
Reply With Quote
 
Quaoar
Guest
Posts: n/a
 
      30th Aug 2004

"Steve" <(E-Mail Removed)> wrote in message
news:27a901c48e4d$65f55760$(E-Mail Removed)...
> I've got a couple of computers connected to a router - 2
> wired, one wirelss. The router is connected to a cable
> modem. One of the wired computers running Windows XP
> (service pack 2) will not connect. It keeps setting the
> IP address at 169.254.xxx instead of 192.168.x.x.
> I release and renew iconfig and it gives me the
> message "an error occurred while renewing interface Networ
> Bridge: unable to contact your DHCP server." I've ruled
> out the router and modem - as the other computers work.
> I've switced mobo and network card. No difference. I
> even reloaded Windows XP and that fixed it for about two
> weeks and then it went out again. I can manually set the
> IP address for 192.168.x.x and that lets the computer
> communicate with the other two computers, but it still
> won't connect to the internet.
> Thoughts?


Google for both lspfix.exe and winsockxpfix.exe. Both will repair the
TCP/IP stack.
Q


 
Reply With Quote
 
Steve Moore
Guest
Posts: n/a
 
      31st Aug 2004
Bingo! The moment I deleted it the Internet was up and
running. Thanks.

Steve Moore

>-----Original Message-----
>In article <27a901c48e4d$65f55760

$(E-Mail Removed)>, "Steve"
><(E-Mail Removed)> wrote:
>>I've got a couple of computers connected to a router - 2
>>wired, one wirelss. The router is connected to a cable
>>modem. One of the wired computers running Windows XP
>>(service pack 2) will not connect. It keeps setting the
>>IP address at 169.254.xxx instead of 192.168.x.x.
>>I release and renew iconfig and it gives me the
>>message "an error occurred while renewing interface

Networ
>>Bridge: unable to contact your DHCP server." I've ruled
>>out the router and modem - as the other computers work.
>>I've switced mobo and network card. No difference. I
>>even reloaded Windows XP and that fixed it for about two
>>weeks and then it went out again. I can manually set

the
>>IP address for 192.168.x.x and that lets the computer
>>communicate with the other two computers, but it still
>>won't connect to the internet.
>>Thoughts?

>
>If you don't have a specific need for the Network Bridge,

right-click
>and delete it. Then, run ipconfig again to get an IP

address for the
>local area network connection.
>--
>Best Wishes,
>Steve Winograd, MS-MVP (Windows Networking)
>
>Please post any reply as a follow-up message in the news

group
>for everyone to see. I'm sorry, but I don't answer

questions
>addressed directly to me in E-mail or news groups.
>
>Microsoft Most Valuable Professional Program
>http://mvp.support.microsoft.com
>.
>

 
Reply With Quote
 
Guest
Posts: n/a
 
      31st Aug 2004
Thanks for the suggestion. Before I tried, it, I tried
someone elses suggestion to delete my bridge connection
and it worked. I downloaded the fix program and will keep
it in mind if I have more problems.

>-----Original Message-----
>
>"Steve" <(E-Mail Removed)> wrote in

message
>news:27a901c48e4d$65f55760$(E-Mail Removed)...
>> I've got a couple of computers connected to a router - 2
>> wired, one wirelss. The router is connected to a cable
>> modem. One of the wired computers running Windows XP
>> (service pack 2) will not connect. It keeps setting the
>> IP address at 169.254.xxx instead of 192.168.x.x.
>> I release and renew iconfig and it gives me the
>> message "an error occurred while renewing interface

Networ
>> Bridge: unable to contact your DHCP server." I've ruled
>> out the router and modem - as the other computers work.
>> I've switced mobo and network card. No difference. I
>> even reloaded Windows XP and that fixed it for about two
>> weeks and then it went out again. I can manually set

the
>> IP address for 192.168.x.x and that lets the computer
>> communicate with the other two computers, but it still
>> won't connect to the internet.
>> Thoughts?

>
>Google for both lspfix.exe and winsockxpfix.exe. Both

will repair the
>TCP/IP stack.
>Q
>
>
>.
>

 
Reply With Quote
 
New Member
Join Date: Oct 2007
Posts: 1
 
      14th Oct 2007
I am having the same problem that Steve had stated in the first post.

I have a desktop PC and my laptop on the same Linksys router. Both have worked fine for the past year. Now, the laptop is have the problem listed by Steve. The desktop PC is still connected through the router and having no issues. I did an ipconfig /release and /renew and got the same error message as Steve. I do not have a bridge set up and i tried multiple ways of renewing/repairing the tcp/ip stack. I tried lspfix.exe and it returned no errors. I have an IBM thinkpad T60 and am running windows XP

Thanks for any help you can give!
 
Reply With Quote
 
New Member
Join Date: Jun 2008
Posts: 1
 
      15th Jun 2008
Same problem here. Damn Vista's black heart.
After following many peoples suggestions on other forums to reset the TCP/IP stack:
1. Click on Start button.
2. Type Cmd in the Start Search text box.
3. Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as Administrator. Allow elevation request.
4. Type netsh int ip reset in the Command Prompt shell, and then press the Enter key.
5. Restart the computer.

I found that this DIDNT work. Bummer.

Uninstalling the driver for the netcard didnt work either. I had to uninstall the driver and check the box to delete the driver from the system. After restarting it installed the standard driver and all is well again. I guess if this ever pops up again ill just have to keep doing the same. So much for my first week with Vista - even after SP1. Pretty much regretting the shift from XP if life is going to be like this.

Hope someone else finds this helpful.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: ipconfig unable to contact DHCP server Malke Windows Vista General Discussion 3 10th Nov 2008 12:23 AM
XP KILLED IPCONFIG!!!!!! ...Please Help....Re: ipconfig doesn't execute I'm Ted Jones Dammit!!! Windows XP Networking 24 19th Mar 2005 04:29 PM
ipconfig and ipconfig /all MarcusB Windows XP General 13 9th Mar 2004 02:06 PM
broadband performing as dialup. cant repair connection, ipconfig cannot contact DHCP server =?Utf-8?B?TXIuIFBpbms=?= Windows XP Help 3 12th Feb 2004 08:11 AM
unable to contact your DHCP server (from: ipconfig /renew) DaveF Windows XP Networking 2 5th Feb 2004 02:35 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 03:36 PM.