re: MSDRV Fault and ethernet problem
Wednesday, June 6, 2001 at 10:50 am
Windows 98 Annoyances Discussion Forum
Posted by Curt R
(1315 messages posted)
You can test your NIC by pinging the loopback address........this will tell you
if it's a TCP/IP problem. If the ping works no problem! Command syntax is as follows
(done in a a DOS window):
ping 127.0.0.1 If that returns an error "bad
address" or just a "time out" You have to uninstall and reinstall your TCP/IP protocol
stack. If however, it returns a proper ping reply then try pinging your IP address....this
will tell you if your NIC is working properly. If both of those come back with good
ping replies, then you know it's not your NIC. (Although, a hardware loopback device
plugged in on the NIC and test's run will verify that it is or isn't a NIC problem
as well) If pinging your IP address returns a positive result, try pinging your
DNS server. If you get no reply, then the problem is on your ISP's end and not your
NIC (providing both the loopback and pinging your own IP address return positive
results)
On Wed, 6 Jun, 2001 - 10:35, Brad wrote:
>About a week ago my internet stopped working, and I was getting an Msdrv error.
>Technical assistance at roadrunner told me to reload windows. That stopped the
Msdrv
>error but now the cable modem cannot find the network card. In the system icon
under
>device manager it says the card is running okay. The cable people say its a network
>card problem, and the Netgear people say its a cable proble. Any suggestions??????
>
|
All messages in this thread [show all]
 |  | re: MSDRV Fault and ethernet problem (Curt R: Wed, Jun 6, 2001, 10:50 am) |
|
