re: Msdrv.exe problem
Thursday, June 7, 2001 at 10:12 pm
Windows 98 Annoyances Discussion Forum
Posted by Curt R
(1315 messages posted)
Like I pointed out on the previous thread initiated by this poster....testing
the NIC is a very simple procedure. Open a DOS window and type the following command:
ping 127.0.0.1 This pings the loopback address and will tell you if your
TCP/IP protocol stack is loaded and working properly (if a proper ping reply is returned,
it's working....if you get an error message, it's not...then you should unistall
and reinstall your TCP/IP) If this isn't the problem, the next step it to ping your
IP address. This will tell you if the NIC is functioning. As to the virus I can't
say but I do know Symantec is likely to have information on it as well as any other
number of anti virus manufacturers.
On Thu, 7 Jun, 2001 - 11:42, Rundll wrote:
>a virus can cause anything to happen. often where there is one, there are others...as
>the behavior of a user or the lack of proper security settings that cause one infection
>are an open door.
>
>due to the nature of viruses...not knowing what exactly they are doing, whether
there
>are multiple infections that you may be dealing with, etc. you can spin your wheels
>and never get anywhere. from a troubleshooting standpoint, it is important to know
>the machine is clean...lest you are like Sisyphus and never get that boulder to
the
>top of the hill.
>
>in the case of msdrv.exe/backdoor.ayslum, i would not expect it to break internet
>connectivity. it specifically uses internet connectivity and to break it would
be
>like shooting itself in the foot...but you never know...even microsoft can't always
>get the code writing right and the guys that created msdrv.exe are probably amateurs
>compared to them...it wouldn't supprise me if it had bugs.
>
>in my line of work, i never heard about the times when an over-the-top installation
>of windows fixed things...because...well...it worked :) i did however hear over
>and over how one of the troubleshooting steps someone took was to reinstall windows
>and things went from bad to worse. reinstalling windows on top of itself can cause
>mismatched files (though there are safeguards against this, they don't always seem
>to work) and can cause device renumeration...after an installtion, i have seen network
>cards jump onto irq 5, the same as the sound and now sound doesn't work and internet
>connectivity is inconsistant...just an example.
>
>do you have another pc that is part of a local area network? can we install the
>protocol NetBEUI and connect with other machines? that would help to isolate where
>the problem may be.
>
>if you have access to another machine over a LAN, we can test network connectivity
>with a very basic troubleshooting utility NET DIAG.
>
>do a search for wsock32.dll. note the entire line that has its size, and the modified
>date. sometimes viruses will infect this file to monitor your internet behavior...where
>you go...attempt to send emails on your behalf...if this file is the wrong size
it
>can definately break you ability to get on the internet.
>
>what version of windows do you have?
>
>have you tried cleanbooting the machine? do you have a firewall running that may
>be blocking internet access? what one?
>
>if cleanbooting and removing the firewall doesn't help, try this. there are two
>versions of the following steps. these are the least complicated. you will need
>your win98 cd to perform these steps. also, while they are straightforward steps
>tht involve only windows tools, take them at your own risk.
>1) backup the registry...start > run > scanreg...
>2) get into your network properties and remove everything except for the actual
>network adapter(s). click OK...the machine will do some file copying then prompt
>you to reboot...say no.
>3) go to control panel > add/remove programs > windows setup > communications >
>uncheck dialup networking...if it gives you a warning about dependent programs,
note
>what they are and then say OK...click OK again...the machine should prompt to reboot...say
>OK to reboot.
>4) go to control panel > add/remove programs > windows setup > communications >
>recheck dialup networking > click ok > click ok and reboot.
>5) go into network properties and reconfigure your connection to your isp. reboot.
>6) test internet connectivity.
>
>
>
>On Thu, 7 Jun, 2001 - 11:03, Brad wrote:
>
>>
>>Would an Msdrv.exe or backdoor.asylum virus cause my internet to stop working?
>Ever
>>since I reloaded windows to solve an Msdrv problem my internet can't find a server.
>>
>>When I called roadrunner we could not renew or reset my IP address. They also
could
>>not see my Network card. When I look in control pannel\system\device manager and
>>click on the card it says its working fine.
>>
>>I've tryed removing the card from the device manager and reloading it, but nothing
>>has worked. Any suggestions?
>>
>>Brad
>>
- Written in response to:
- re: Msdrv.exe problem (Rundll: Thursday, June 7, 2001 at 11:42 am)
There are presently no replies to this message.
|
| 
