Cannot connect to IP via DSL w/Windows 2000 - sudden problem

  • Thread starter Thread starter Michael Haverty
  • Start date Start date
M

Michael Haverty

Been using same DSL provider/modem for 18 months, same PC
and laptop (I swap out ethernet cables on the modem from
one to the other, never been a problem before). All of a
sudden today I have no IP connectivity on the desktop (Win
2000). DSL works fine when I plug the cable into the
laptop (same OS). Tried uninstalling/reinstalling SIS 900
Ethernet adapter, Protocols and Clients, drivers, etc.
Tried MS support site no help yet. Tried ping commands in
MS-DOS. Appears that the DHCP server is unreachable so
assuming something is screwed up in the TCP/IP settings
but can't nail it. Any other suggestions (dll files,
winsock, etc.?). I've spent too many hours already and am
exasperated (anybody else been there can lift my spirits?)
 
: Been using same DSL provider/modem for 18 months, same PC
: and laptop (I swap out ethernet cables on the modem from
: one to the other, never been a problem before). All of a
: sudden today I have no IP connectivity on the desktop (Win
: 2000). DSL works fine when I plug the cable into the
: laptop (same OS). Tried uninstalling/reinstalling SIS 900
: Ethernet adapter, Protocols and Clients, drivers, etc.
: Tried MS support site no help yet. Tried ping commands in
: MS-DOS. Appears that the DHCP server is unreachable so
: assuming something is screwed up in the TCP/IP settings
: but can't nail it. Any other suggestions (dll files,
: winsock, etc.?). I've spent too many hours already and am
: exasperated (anybody else been there can lift my spirits?)

Did you try a different NIC? They do go bad.
Ping what? Name or IP?
If you cannot ping by IP can you ping localhost? Yes? Try another cable.
No? Try another card. Another cable also bad? Try another card.
I've seen cards ping localhost, Windows lie and say, "Oh, ya'. This card is
the bomb. Works perfectly." Changed out the NIC and called it a day.
Uninstalling a driver on a bad NIC will give you the same results if it's
not the driver.
Perhaps showing your ipconfig /all here will help if you think it's really a
TCP/IP setting...
If you cannot see DHCP, then set the IP address manually and see if that
helps.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
 
thanks roland I'll give it a try, tried most of what u
suggest to a degree short of changing out the NIC card,
I'll post what happens for others to benefit.
 
: thanks roland I'll give it a try, tried most of what u
: suggest to a degree short of changing out the NIC card,
: I'll post what happens for others to benefit.

You're welcome. It's a process of elimination. If it's not software, then
it may be hardware (NIC, cabling...). I've actually had a batch of bad
patch cables. I've also replaced a bad card with a NEW bad card. S**t
happens sometimes. If you feel like you've exhausted all efforts, you
probably haven't. You can try putting that NIC, cabling on different system
that currently works. If the hardware works, then it might be a driver or
something else software related.

I have seen TCP/IP not work, on an NT 4 Server after adding some services.
I had to reapply the latest service pack and then reapply Compaq OEM
drivers, respectively. If it was on Exchange Server, I then had to reapply
Exchange SPs. Seems like one update would overwrite a shared file of
another. Would have been nice if the OS would notify you of overwriting
shared files and allow you to choose, instead of leaving it up to the OEM,
like it does with Array Controller drivers. ~sigh~

Keep us updated and good luck.

Roland
 
Back
Top