networking / connectivity issues

I work in a call centre for DSL , we have been recieving
lots of calls for the past 2-3 days with customers having
connectivity issue related to Network cards in XP.
their NICs cannot communicate with any networking device
(routers , modem). device Manager showing no issues with
NIC. NIC always on a win default ip 169.X.X.X, not
grabbing the ip for any networking device.
restacking tcp/ip , uninstalling reinstalling network
card, disabling enabling doesnot fix, even tried system
restore no good, in some cases their antivirus prog was
automatically disbaled and we were unable to reenable it .
on the release renew ip command mostly getting " error
occured while renewing .....that is not a socket ".

quoted from http://www.ChicagoTech.net
Can't obtain/renew IP addresses from the DHCP server

Symptoms: 1) you have a DHCP client which may not be able to obtain/renew IP
addresses from the DHCP server intermittently. 2) after setup a workstation
to obtain an IP address from DHCP, the machine can't ping others and
ipconfig /all shows Autoconfiguration IP Address. . . : 169.254.x.x.

Resolutions: 1) If this is XP, obtain the latest service pack for Windows
XP.
2) Use the Network Diagnostics tool to identify any failed settings. To do
this, go to Help and Support>Use Tools to view your computer information and
diagnose problems>Network Diagnostics>Scan your system. When the process
finishes, check for any items marked "FAILED" in red, expand those
categories, and view the additional details about what the testing showed.
3) Assign a static ip on the client and ping the DHCP server. If you can't
ping the DHCP server, check the connection and hardware.
4) If you can ping the DHCP after assigning static ip, check the DHCP
settings.
5) Make sure no firewall is running on your LAN.
6) Run Repair this connection if it is XP. Or use netsh to reset TCP/IP
configuration.
7) If it is win98/w2k, remove and reinstall TCP/IP.
8) Try to upgrade the new NIC driver.
9) Make sure you don't run out of IPs in the DHCP scope.


--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"JQ" <anonymous@discussions.microsoft.com> wrote in message
news:16fa701c44898$816a4230$a301280a@phx.gbl...
>I work in a call centre for DSL , we have been recieving
> lots of calls for the past 2-3 days with customers having
> connectivity issue related to Network cards in XP.
> their NICs cannot communicate with any networking device
> (routers , modem). device Manager showing no issues with
> NIC. NIC always on a win default ip 169.X.X.X, not
> grabbing the ip for any networking device.
> restacking tcp/ip , uninstalling reinstalling network
> card, disabling enabling doesnot fix, even tried system
> restore no good, in some cases their antivirus prog was
> automatically disbaled and we were unable to reenable it .
> on the release renew ip command mostly getting " error
> occured while renewing .....that is not a socket ".
>

Is there any chance that they could have identical MAC address's?

I also work as a technician for a DSL network, and have had
the same types of calls in the past few days. ...always
winXP. Nothing i have seen will work, we have tried
changing out the equipment, changing their DHCP server
entirely. We just are not seeing any communication from
their PC to the DHCP server at all. that ****ed 169 IP...
Most fo the time firewalls and routers are the culprit,
but i have seen this w/out them. There are certain viruses
that create and leave an unrepairable proxy route which
once the virus is gone, windows cannot repair. Format
time. If you find out something, please post it here and
let us know as well. good luck.
>-----Original Message-----
>I work in a call centre for DSL , we have been recieving
>lots of calls for the past 2-3 days with customers having
>connectivity issue related to Network cards in XP.
>their NICs cannot communicate with any networking device
>(routers , modem). device Manager showing no issues with
>NIC. NIC always on a win default ip 169.X.X.X, not
>grabbing the ip for any networking device.
>restacking tcp/ip , uninstalling reinstalling network
>card, disabling enabling doesnot fix, even tried system
>restore no good, in some cases their antivirus prog was
>automatically disbaled and we were unable to reenable it .
>on the release renew ip command mostly getting " error
>occured while renewing .....that is not a socket ".
>
>.
>

HI,

This is the exact problem I am having at work on one
computer only. Do you find it strange that it is
happening to so many people all of a sudden? Could it
perhaps be a virus or along those lines?

Thanks

Tina

>-----Original Message-----
>I work in a call centre for DSL , we have been recieving
>lots of calls for the past 2-3 days with customers having
>connectivity issue related to Network cards in XP.
>their NICs cannot communicate with any networking device
>(routers , modem). device Manager showing no issues with
>NIC. NIC always on a win default ip 169.X.X.X, not
>grabbing the ip for any networking device.
>restacking tcp/ip , uninstalling reinstalling network
>card, disabling enabling doesnot fix, even tried system
>restore no good, in some cases their antivirus prog was
>automatically disbaled and we were unable to reenable it .
>on the release renew ip command mostly getting " error
>occured while renewing .....that is not a socket ".
>
>.
>

Yes, it is very possible. However, im more inclined to
believe that it is remnants of a viruses damage, rather
than an active one. There are Microsoft KB articles which
state that there are newer viruses that are leaving an
unrepairable proxy route which once the virus is gone,
windows cannot repair it. ...unless of course you format
and re-install.
>-----Original Message-----
>HI,
>
>This is the exact problem I am having at work on one
>computer only. Do you find it strange that it is
>happening to so many people all of a sudden? Could it
>perhaps be a virus or along those lines?
>
>Thanks
>
>Tina
>
>>-----Original Message-----
>>I work in a call centre for DSL , we have been recieving
>>lots of calls for the past 2-3 days with customers having
>>connectivity issue related to Network cards in XP.
>>their NICs cannot communicate with any networking device
>>(routers , modem). device Manager showing no issues with
>>NIC. NIC always on a win default ip 169.X.X.X, not
>>grabbing the ip for any networking device.
>>restacking tcp/ip , uninstalling reinstalling network
>>card, disabling enabling doesnot fix, even tried system
>>restore no good, in some cases their antivirus prog was
>>automatically disbaled and we were unable to reenable it .
>>on the release renew ip command mostly getting " error
>>occured while renewing .....that is not a socket ".
>>
>>.
>>
>.
>

In article <16f9d01c448ca$3d5a2c90$a601280a@phx.gbl>, "Druss"
<anonymous@discussions.microsoft.com> wrote:
>Yes, it is very possible. However, im more inclined to
>believe that it is remnants of a viruses damage, rather
>than an active one. There are Microsoft KB articles which
>state that there are newer viruses that are leaving an
>unrepairable proxy route which once the virus is gone,
>windows cannot repair it. ...unless of course you format
>and re-install.

I can't find any mention of "proxy route" in the KB. What are the
numbers of those articles, Druss? I'd like to see them.
--
Thanks,
Steve Winograd, MS-MVP (Windows Networking)

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

I saw this the other day at a church with an xp machine and fixed it
at the last minute with an article found somewhere on the internet
that day. Also saw it yesterday with an xp machine at a realtor.
Wont get dhcp, plug in another laptop and it works fine.

I backed up registry and deleted some winsock entries but not sure of
the exact process. Search for the error message you get when you do
an ipconfig /renew ..

greg_bunch@hotmail.com (Greg Bunch) wrote in message news:<26ebef05.0406090337.7192c263@posting.google. com>...
> I saw this the other day at a church with an xp machine and fixed it
> at the last minute with an article found somewhere on the internet
> that day. Also saw it yesterday with an xp machine at a realtor.
> Wont get dhcp, plug in another laptop and it works fine.
>
> I backed up registry and deleted some winsock entries but not sure of
> the exact process. Search for the error message you get when you do
> an ipconfig /renew ..

and re-installed tcp/ip