What is connected to which?

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.newusers (More info?)

I posted yesterday but so far no answers. Maybe my post is too confusing.
Will try to clarify:

I am trying to find answers to a problem and to find whether the problem is
connected to downloading Service Pack 2 or if it connected to something else.

It began when I went to a site I visit daily and have no problems accessing
normally. However this time got a message that I was unable to connect to
server. It said that it is possible that I might 1) not be connected to the
internet - which I was, 2) not signed in - which I was and 3) had stale file
in my cache. This last I did not know what it meant so I came over to the
microsoft site to look up what that meant. Several files or articles talked
about updating service packs and since I had not done that yet with this new
XP I d/l service pack 2. It auto installed.

At some point during the night though I cannot recall if it was before or
after this d/l, I got a request from my firewall for LSA shell (export
version) to access the internet. Since I had never encountered this before
and did not know what LSA shell was, I denied access.

I put LSA shell into the microsoft search engine and came up with articles
telling me that it was a worm. I immediately updated my virus definitions and
did a scan of the system. It came back that there was no infection. A search
of my computer does show lsass.exe application in c:\windows\system32 as well
as the doc and settings folder (temp internet folder) sasser, sasser1,
sasser2 and another file with the same 'address' 199.239.233.2 calling itself
'virus removal utilities by
online...' I also went to my virus scan site to find out what the sasser
worm does and there was no information on it at the site.

I do not know why the anti virus program did not find these, nor do I know
if they are connected to the Service Pack d/l or to something else and if the
stale file in cache is connected in some way to all of this. Can any one help
me?

dazed and confused here.
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.newusers (More info?)

Thank you David for all the info. While I updated my live update and got the
latest definitions and ran a full system scan, the results did not come back
as possitive for the sasser worm. I do however know that there are files on
my system which are sasser files. Is it possible that because I denied access
through my firewall it did not trigger the worm? Why wouldn't the virus scan
show that I was infected? Symantec has been very uncooperative and I am
unable to get information from them as to whether the systemworks version I
have is working properly.

I will however, look for those file and delete them as noted below in your
info

K

"David Candy" wrote:

> There's lots of varients.
>
>
> W32.Sasser.Worm
> Discovered on: April 30, 2004
> Last Updated on: July 27, 2004 11:20:39 AM
Also Known As: W32/Sasser.worm.a [McAfee],
WORM_SASSER.A [Trend], Worm.Win32.Sasser.a [Kaspersky], W32/Sasser-A
[Sophos], Win32.Sasser.A [Computer Associates], Sasser [F-Secure],
W32/Sasser.A.worm [Panda]
>
> Type: Worm
> Infection Length: 15,872 bytes
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.newusers (More info?)

That's for the first sasser. There are lots of sasser (type it in symantec's site). Programs like this tend to interfere with AV programs. I've not ever caught sasser so I don't know it well. I posted that page (and deleted 50000 images from it) because viruses tend to block AV companies web sites.

Plus sasser is not the only lsa thingy.

Ensure you are sasser free first.

http://www.sarc.com/search/
This is norton's site. Just type sasser. Norton tends to have the best descriptions but a lousy search engine (it finds the same pages over and over again).
--
----------------------------------------------------------
http://www.uscricket.com
"kiadau" <kiadau@discussions.microsoft.com> wrote in message news:2EAA3302-9720-4FA4-B39E-3EACA5B36666@microsoft.com...
> Thank you David for all the info. While I updated my live update and got the
> latest definitions and ran a full system scan, the results did not come back
> as possitive for the sasser worm. I do however know that there are files on
> my system which are sasser files. Is it possible that because I denied access
> through my firewall it did not trigger the worm? Why wouldn't the virus scan
> show that I was infected? Symantec has been very uncooperative and I am
> unable to get information from them as to whether the systemworks version I
> have is working properly.
>
> I will however, look for those file and delete them as noted below in your
> info
>
> K
>
> "David Candy" wrote:
>
>> There's lots of varients.
>>
>>
>> W32.Sasser.Worm
>> Discovered on: April 30, 2004
>> Last Updated on: July 27, 2004 11:20:39 AM
> Also Known As: W32/Sasser.worm.a [McAfee],
> WORM_SASSER.A [Trend], Worm.Win32.Sasser.a [Kaspersky], W32/Sasser-A
> [Sophos], Win32.Sasser.A [Computer Associates], Sasser [F-Secure],
> W32/Sasser.A.worm [Panda]
>>
>> Type: Worm
>> Infection Length: 15,872 bytes
>