unable to contact dhcp server,request has timed out

Hi,
Iam working in a tech support, over the past few weeks
we have been receiving several calls where, the ip address
is 169.254.x.y. When we try to renew and release the
ipaddress - it gets the same ipaddress. I have reset the
tcp/ip stack, when we do this the ipaddress becomes
0.0.0.0 when we release the ipadress. but when i renew the
ipaddress it gives the error "unable to contact dhcp
server,request has timed out". have tried to reinstall the
drivers, have tried to remove the winsock & winsock2 from
registry and reinstalled the tcp/ip protocol using the
nettcpip.ini file. Downloaded the winsock fix to no avail.
All of this still gives the same error when i renew the
ipaddress- any suggestions??? By the way other computers
connected to the router is able to get an ip address.

-Ritesh

Have you considered the possibility that your network card or cable may be
bad?

--
Richard G. Harper [MVP Win9x] rgharper@email.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Ritesh Das" <anonymous@discussions.microsoft.com> wrote in message
news:121201c4264b$d450e310$a601280a@phx.gbl...
> Hi,
> Iam working in a tech support, over the past few weeks
> we have been receiving several calls where, the ip address
> is 169.254.x.y. When we try to renew and release the
> ipaddress - it gets the same ipaddress. I have reset the
> tcp/ip stack, when we do this the ipaddress becomes
> 0.0.0.0 when we release the ipadress. but when i renew the
> ipaddress it gives the error "unable to contact dhcp
> server,request has timed out". have tried to reinstall the
> drivers, have tried to remove the winsock & winsock2 from
> registry and reinstalled the tcp/ip protocol using the
> nettcpip.ini file. Downloaded the winsock fix to no avail.
> All of this still gives the same error when i renew the
> ipaddress- any suggestions??? By the way other computers
> connected to the router is able to get an ip address.
>
> -Ritesh

I am having the almost identical issue with one of the
machines on my network. I think it may be a trojan virus
of some sort -- although I have virus and firewall
software on that machine. Have you checked your host file?
On my affected machine there were at least 100 web
addresses hardcoded into the file. Flushdns didn't get rid
of them. I had to delete them from the file. I don't think
it's a bad network card. Anyone else having these same
problems???

Jane
>-----Original Message-----
>Have you considered the possibility that your network
card or cable may be
>bad?
>
>--
>Richard G. Harper [MVP Win9x] rgharper@email.com
>* PLEASE post all messages and replies in the newsgroups
>* for the benefit of all. Private mail is usually not
replied to.
>* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>
>
>"Ritesh Das" <anonymous@discussions.microsoft.com> wrote
in message
>news:121201c4264b$d450e310$a601280a@phx.gbl...
>> Hi,
>> Iam working in a tech support, over the past few weeks
>> we have been receiving several calls where, the ip
address
>> is 169.254.x.y. When we try to renew and release the
>> ipaddress - it gets the same ipaddress. I have reset the
>> tcp/ip stack, when we do this the ipaddress becomes
>> 0.0.0.0 when we release the ipadress. but when i renew
the
>> ipaddress it gives the error "unable to contact dhcp
>> server,request has timed out". have tried to reinstall
the
>> drivers, have tried to remove the winsock & winsock2
from
>> registry and reinstalled the tcp/ip protocol using the
>> nettcpip.ini file. Downloaded the winsock fix to no
avail.
>> All of this still gives the same error when i renew the
>> ipaddress- any suggestions??? By the way other computers
>> connected to the router is able to get an ip address.
>>
>> -Ritesh
>
>
>.
>

I'm having a similar problem with a wireless connection.
It doesn't matter whether I use the built-in wireless on
the computer or a USB adapter. A wired connection works
perfectly. The wireless connection returns the same
169.254.x.y problem that Ritesh is experiencing. The
computer is XP Home.
>-----Original Message-----
>Have you considered the possibility that your network
card or cable may be
>bad?
>
>--
>Richard G. Harper [MVP Win9x] rgharper@email.com
>* PLEASE post all messages and replies in the newsgroups
>* for the benefit of all. Private mail is usually not
replied to.
>* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>
>
>"Ritesh Das" <anonymous@discussions.microsoft.com> wrote
in message
>news:121201c4264b$d450e310$a601280a@phx.gbl...
>> Hi,
>> Iam working in a tech support, over the past few
weeks
>> we have been receiving several calls where, the ip
address
>> is 169.254.x.y. When we try to renew and release the
>> ipaddress - it gets the same ipaddress. I have reset
the
>> tcp/ip stack, when we do this the ipaddress becomes
>> 0.0.0.0 when we release the ipadress. but when i renew
the
>> ipaddress it gives the error "unable to contact dhcp
>> server,request has timed out". have tried to reinstall
the
>> drivers, have tried to remove the winsock & winsock2
from
>> registry and reinstalled the tcp/ip protocol using the
>> nettcpip.ini file. Downloaded the winsock fix to no
avail.
>> All of this still gives the same error when i renew the
>> ipaddress- any suggestions??? By the way other
computers
>> connected to the router is able to get an ip address.
>>
>> -Ritesh
>
>
>.
>

Hi every one, thanx for ur response Richard, Jane and
David,

No the network card is perfectly fine. When we assign
a static ipaddress to the nic on his office network, he is
able to get online. The problem exists only when he
connects to any network that assigns dynamic ip address.
By the way Jane, did deleting the hosts file work? does it
get a valid ipaddress now? By the way I had also tried -

http://support.microsoft.com/default.aspx?scid=kb;en-
us;822123&Product=winxp
and
http://support.microsoft.com/default.aspx?scid=kb;en-
us;169229

but to no avail. The suprising part is that we had calls
where the customer just bought his system and trying to
hookup to the internet for the 1st time and this
happens...Could this still be a trojan? Though i
personally feel it could be a virus or a trojan as this is
becoming a very common issue with most of the calls that
come in...

-ritesh



>-----Original Message-----
>I am having the almost identical issue with one of the
>machines on my network. I think it may be a trojan virus
>of some sort -- although I have virus and firewall
>software on that machine. Have you checked your host
file?
>On my affected machine there were at least 100 web
>addresses hardcoded into the file. Flushdns didn't get
rid
>of them. I had to delete them from the file. I don't
think
>it's a bad network card. Anyone else having these same
>problems???
>
>Jane
>>-----Original Message-----
>>Have you considered the possibility that your network
>card or cable may be
>>bad?
>>
>>--
>>Richard G. Harper [MVP Win9x] rgharper@email.com
>>* PLEASE post all messages and replies in the newsgroups
>>* for the benefit of all. Private mail is usually not
>replied to.
>>* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>>
>>
>>"Ritesh Das" <anonymous@discussions.microsoft.com> wrote
>in message
>>news:121201c4264b$d450e310$a601280a@phx.gbl...
>>> Hi,
>>> Iam working in a tech support, over the past few
weeks
>>> we have been receiving several calls where, the ip
>address
>>> is 169.254.x.y. When we try to renew and release the
>>> ipaddress - it gets the same ipaddress. I have reset
the
>>> tcp/ip stack, when we do this the ipaddress becomes
>>> 0.0.0.0 when we release the ipadress. but when i renew
>the
>>> ipaddress it gives the error "unable to contact dhcp
>>> server,request has timed out". have tried to reinstall
>the
>>> drivers, have tried to remove the winsock & winsock2
>from
>>> registry and reinstalled the tcp/ip protocol using the
>>> nettcpip.ini file. Downloaded the winsock fix to no
>avail.
>>> All of this still gives the same error when i renew the
>>> ipaddress- any suggestions??? By the way other
computers
>>> connected to the router is able to get an ip address.
>>>
>>> -Ritesh
>>
>>
>>.
>>
>.
>

Hi every one, thanx for ur response Richard, Jane and
David,

No the network card is perfectly fine. When we assign
a static ipaddress to the nic on his office network, he is
able to get online. The problem exists only when he
connects to any network that assigns dynamic ip address.
By the way Jane, did deleting the hosts file work? does it
get a valid ipaddress now? By the way I had also tried -

http://support.microsoft.com/default.aspx?scid=kb;en-
us;822123&Product=winxp
and
http://support.microsoft.com/default.aspx?scid=kb;en-
us;169229

but to no avail. The suprising part is that we had calls
where the customer just bought his system and trying to
hookup to the internet for the 1st time and this
happens...Could this still be a trojan? Though i
personally feel it could be a virus or a trojan as this is
becoming a very common issue with most of the calls that
come in...

-ritesh

>-----Original Message-----
>I am having the almost identical issue with one of the
>machines on my network. I think it may be a trojan virus
>of some sort -- although I have virus and firewall
>software on that machine. Have you checked your host
file?
>On my affected machine there were at least 100 web
>addresses hardcoded into the file. Flushdns didn't get
rid
>of them. I had to delete them from the file. I don't
think
>it's a bad network card. Anyone else having these same
>problems???
>
>Jane
>>-----Original Message-----
>>Have you considered the possibility that your network
>card or cable may be
>>bad?
>>
>>--
>>Richard G. Harper [MVP Win9x] rgharper@email.com
>>* PLEASE post all messages and replies in the newsgroups
>>* for the benefit of all. Private mail is usually not
>replied to.
>>* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>>
>>
>>"Ritesh Das" <anonymous@discussions.microsoft.com> wrote
>in message
>>news:121201c4264b$d450e310$a601280a@phx.gbl...
>>> Hi,
>>> Iam working in a tech support, over the past few
weeks
>>> we have been receiving several calls where, the ip
>address
>>> is 169.254.x.y. When we try to renew and release the
>>> ipaddress - it gets the same ipaddress. I have reset
the
>>> tcp/ip stack, when we do this the ipaddress becomes
>>> 0.0.0.0 when we release the ipadress. but when i renew
>the
>>> ipaddress it gives the error "unable to contact dhcp
>>> server,request has timed out". have tried to reinstall
>the
>>> drivers, have tried to remove the winsock & winsock2
>from
>>> registry and reinstalled the tcp/ip protocol using the
>>> nettcpip.ini file. Downloaded the winsock fix to no
>avail.
>>> All of this still gives the same error when i renew the
>>> ipaddress- any suggestions??? By the way other
computers
>>> connected to the router is able to get an ip address.
>>>
>>> -Ritesh
>>
>>
>>.
>>
>.
>