A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » The Basics
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Conficker infection on network - advice wanted on removal/protection



 
 
Thread Tools Display Modes
  #1  
Old September 9th 10, 06:10 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
eggedd2k[_2_]
external usenet poster
 
Posts: 4
Default Conficker infection on network - advice wanted on removal/protection

I posted a few weeks ago but have done some further work/consideration
about this issue.

I've just taken on a new client whose network has been left in pretty
bad shape by their previous IT support provider. They have
approximately 11 XP workstations and 1 SBS 2003 DC.

To sum up the state they're in:

- No server or workstation Windows Updates installed for a very long
time (still on XP SP2)
- AVG Personal Edition on all workstations, AVG SBS on the server but
expired May 2010.
- No logon passwords needed/very poor passwords on workstations
- Conficker virus infection on all computers.

The previous IT firm seemed to give up on the client once they knew
they had a Conficker infection.


I want to rid them of the Conficker virus first of all. My plan of
attack is as follows:-

One workstation at a time:

1. Format the workstation. Reinstall Windows.
2. Install all available Windows Updates.
3. Install business class anti-virus software
4. Implement additional protection to prevent reinfection (see below)
5. Ensure complex logon password
6. Join the workstation back into the domain and configure for the
user.

By doing this I'm hoping to gradually one workstation at a time
eradicate the virus from the network and prevent reinfection once the
workstation is re-introduced to the network. Additionally doing one at
a time to prevent mass downtime.

The advice I would appreciate from you guys is:

1. I want to PREVENT re-infection. This is crucial. As well as updates
and AV software I plan on doing the following:

- Complex local admin password
- Block Autorun

Is there anything else I can do on the workstation before
reintroducing it to the network to PREVENT reinfection?

2. Is this the most effective method of removing the virus from the
whole network?




Thanks in advance.
Ads
  #2  
Old September 9th 10, 07:03 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Conficker infection on network - advice wanted on removal/protection

Part of the problem here is that by doing one at a time...when you reintroduce it to the network..it risks reinfection by another workstation
Is the server infected

You should go here http://support.microsoft.com/kb/962007 and follow the instructions
It may not be required to format each machine unless you think there is more going on.

After you've taken all the steps in the KB...run Malwarebytes at Malwarebytes.org and find out whatelse you've got to deal with

I'm not a big fan of expecting the virus to be dealt with once it gets into the network...I'd much rather it be dealt with by blocking it from ever getting to the network. A good UTM Firewall will do this...think of it as the Moat around the Castle

Then consider ForeFront Client Security on the workstations...can be updated by Windows Update or WSUS

--
Cris Hanna [SBS - MVP] (since 1997)
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"eggedd2k" wrote in message ...
I posted a few weeks ago but have done some further work/consideration
about this issue.

I've just taken on a new client whose network has been left in pretty
bad shape by their previous IT support provider. They have
approximately 11 XP workstations and 1 SBS 2003 DC.

To sum up the state they're in:

- No server or workstation Windows Updates installed for a very long
time (still on XP SP2)
- AVG Personal Edition on all workstations, AVG SBS on the server but
expired May 2010.
- No logon passwords needed/very poor passwords on workstations
- Conficker virus infection on all computers.

The previous IT firm seemed to give up on the client once they knew
they had a Conficker infection.


I want to rid them of the Conficker virus first of all. My plan of
attack is as follows:-

One workstation at a time:

1. Format the workstation. Reinstall Windows.
2. Install all available Windows Updates.
3. Install business class anti-virus software
4. Implement additional protection to prevent reinfection (see below)
5. Ensure complex logon password
6. Join the workstation back into the domain and configure for the
user.

By doing this I'm hoping to gradually one workstation at a time
eradicate the virus from the network and prevent reinfection once the
workstation is re-introduced to the network. Additionally doing one at
a time to prevent mass downtime.

The advice I would appreciate from you guys is:

1. I want to PREVENT re-infection. This is crucial. As well as updates
and AV software I plan on doing the following:

- Complex local admin password
- Block Autorun

Is there anything else I can do on the workstation before
reintroducing it to the network to PREVENT reinfection?

2. Is this the most effective method of removing the virus from the
whole network?




Thanks in advance.
  #3  
Old September 10th 10, 09:06 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
eggedd2k[_2_]
external usenet poster
 
Posts: 4
Default Conficker infection on network - advice wanted on removal/protection

thanks for your response on this.

Yes the server is infected.

Having thought this through it's clear that by doing one system at a
time there is a risk of reinfection when the cleaned workstation is
joined back into the network.

The Microsoft link you posted is of great help and this is clearly the
path to go down:

1. Stop Conficker from spreading via group policy.
2. Clean each system with AV/Malwarebytes/Malicious Software Removal
tool

thanks again for your help on this!
  #4  
Old September 10th 10, 04:24 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
SteveB[_2_]
external usenet poster
 
Posts: 7
Default Conficker infection on network - advice wanted on removal/protection

Especially with the server also infected how will you be sure that all
infections are totally removed without also reformatting the server and
reinstalling SBS?

"eggedd2k" wrote in message
...
thanks for your response on this.

Yes the server is infected.

Having thought this through it's clear that by doing one system at a
time there is a risk of reinfection when the cleaned workstation is
joined back into the network.

The Microsoft link you posted is of great help and this is clearly the
path to go down:

1. Stop Conficker from spreading via group policy.
2. Clean each system with AV/Malwarebytes/Malicious Software Removal
tool

thanks again for your help on this!



  #5  
Old September 10th 10, 04:52 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Conficker infection on network - advice wanted on removal/protection

I have to agree If server and workstations are infected...I'd flatten everything and start over...or you risk just reinfecting all over again

--
Cris Hanna [SBS - MVP] (since 1997)
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"SteveB" wrote in message ...
Especially with the server also infected how will you be sure that all
infections are totally removed without also reformatting the server and
reinstalling SBS?

"eggedd2k" wrote in message
...
thanks for your response on this.

Yes the server is infected.

Having thought this through it's clear that by doing one system at a
time there is a risk of reinfection when the cleaned workstation is
joined back into the network.

The Microsoft link you posted is of great help and this is clearly the
path to go down:

1. Stop Conficker from spreading via group policy.
2. Clean each system with AV/Malwarebytes/Malicious Software Removal
tool

thanks again for your help on this!



  #6  
Old September 12th 10, 02:30 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Susan Bradley
external usenet poster
 
Posts: 12
Default Conficker infection on network - advice wanted on removal/protection

On 9/9/2010 10:10 AM, eggedd2k wrote:
I posted a few weeks ago but have done some further work/consideration
about this issue.

I've just taken on a new client whose network has been left in pretty
bad shape by their previous IT support provider. They have
approximately 11 XP workstations and 1 SBS 2003 DC.

To sum up the state they're in:

- No server or workstation Windows Updates installed for a very long
time (still on XP SP2)
- AVG Personal Edition on all workstations, AVG SBS on the server but
expired May 2010.
- No logon passwords needed/very poor passwords on workstations
- Conficker virus infection on all computers.

The previous IT firm seemed to give up on the client once they knew
they had a Conficker infection.


I want to rid them of the Conficker virus first of all. My plan of
attack is as follows:-

One workstation at a time:

1. Format the workstation. Reinstall Windows.
2. Install all available Windows Updates.
3. Install business class anti-virus software
4. Implement additional protection to prevent reinfection (see below)
5. Ensure complex logon password
6. Join the workstation back into the domain and configure for the
user.

By doing this I'm hoping to gradually one workstation at a time
eradicate the virus from the network and prevent reinfection once the
workstation is re-introduced to the network. Additionally doing one at
a time to prevent mass downtime.

The advice I would appreciate from you guys is:

1. I want to PREVENT re-infection. This is crucial. As well as updates
and AV software I plan on doing the following:

- Complex local admin password
- Block Autorun

Is there anything else I can do on the workstation before
reintroducing it to the network to PREVENT reinfection?

2. Is this the most effective method of removing the virus from the
whole network?




Thanks in advance.

Call Microsoft security at 1-800-Microsoft and ask for their CSS
security team for Conficker and they will help you with what to do.

Apologies for this... but please repost to www.sbsforum.info this
newsgroup is closing tomorrow.
  #7  
Old September 12th 10, 08:06 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Barry Schwarz[_2_]
external usenet poster
 
Posts: 373
Default Conficker infection on network - advice wanted on removal/protection

On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote:

snip

Apologies for this... but please repost to www.sbsforum.info this
newsgroup is closing tomorrow.


While some servers may drop the newsgroup (you didn't identify which
of the three you meant), it will have no affect on the other servers
that carry it.

--
Remove del for email
  #8  
Old September 12th 10, 10:48 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Susan Bradley
external usenet poster
 
Posts: 12
Default Conficker infection on network - advice wanted on removal/protection

On 9/12/2010 12:06 PM, Barry Schwarz wrote:
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote:

snip

Apologies for this... but please repost to www.sbsforum.info this
newsgroup is closing tomorrow.

While some servers may drop the newsgroup (you didn't identify which
of the three you meant), it will have no affect on the other servers
that carry it.

The reality is that many of us will not find another nntp server, so if
you want the largest pool of helpers, this is the reality.
  #9  
Old September 12th 10, 11:35 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Paul
external usenet poster
 
Posts: 18,275
Default Conficker infection on network - advice wanted on removal/protection

Susan Bradley wrote:
On 9/12/2010 12:06 PM, Barry Schwarz wrote:
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote:

snip

Apologies for this... but please repost to www.sbsforum.info this
newsgroup is closing tomorrow.

While some servers may drop the newsgroup (you didn't identify which
of the three you meant), it will have no affect on the other servers
that carry it.

The reality is that many of us will not find another nntp server, so if
you want the largest pool of helpers, this is the reality.


http://www.aioe.org/

nntp.aioe.org is available, with no registration required.

You can start using it immediately.

I'm posting from it right now.

The reason the owner can afford to do it, is his NNTP server
does not support binaries or movie downloads.

Paul
  #10  
Old September 13th 10, 12:13 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Barry Schwarz[_2_]
external usenet poster
 
Posts: 373
Default Conficker infection on network - advice wanted on removal/protection

On Sun, 12 Sep 2010 14:48:46 -0700, Susan Bradley
wrote:

On 9/12/2010 12:06 PM, Barry Schwarz wrote:
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote:

snip

Apologies for this... but please repost to www.sbsforum.info this
newsgroup is closing tomorrow.

While some servers may drop the newsgroup (you didn't identify which
of the three you meant), it will have no affect on the other servers
that carry it.

The reality is that many of us will not find another nntp server, so if
you want the largest pool of helpers, this is the reality.


If you are using a newsreader (as opposed to a web browser), there are
several servers that are either free or have one time fees of less
than US $10.

--
Remove del for email
  #11  
Old September 13th 10, 03:52 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
SteveB[_2_]
external usenet poster
 
Posts: 7
Default Conficker infection on network - advice wanted on removal/protection

Sure we could switch to something else but why bother? As Susan points out
you will receive only very limited responses to questions and most of the
pool of well qualified respondents such as SBS MVPs and Microsoft personnel
will all be using the new forum. That forum is also easily accessed by an
NNTP reader using the community bridge.

Steve

"Barry Schwarz" wrote in message
...
On Sun, 12 Sep 2010 14:48:46 -0700, Susan Bradley
wrote:

On 9/12/2010 12:06 PM, Barry Schwarz wrote:
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote:

snip

Apologies for this... but please repost to www.sbsforum.info this
newsgroup is closing tomorrow.
While some servers may drop the newsgroup (you didn't identify which
of the three you meant), it will have no affect on the other servers
that carry it.

The reality is that many of us will not find another nntp server, so if
you want the largest pool of helpers, this is the reality.


If you are using a newsreader (as opposed to a web browser), there are
several servers that are either free or have one time fees of less
than US $10.

--
Remove del for email



  #12  
Old September 13th 10, 03:58 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Leythos[_2_]
external usenet poster
 
Posts: 976
Default Conficker infection on network - advice wanted on removal/protection

In article 162fae21-bed4-4d67-93ff-
, says...

I posted a few weeks ago but have done some further work/consideration
about this issue.

I've just taken on a new client whose network has been left in pretty
bad shape by their previous IT support provider. They have
approximately 11 XP workstations and 1 SBS 2003 DC.

To sum up the state they're in:

- No server or workstation Windows Updates installed for a very long
time (still on XP SP2)
- AVG Personal Edition on all workstations, AVG SBS on the server but
expired May 2010.
- No logon passwords needed/very poor passwords on workstations
- Conficker virus infection on all computers.

The previous IT firm seemed to give up on the client once they knew
they had a Conficker infection.


I want to rid them of the Conficker virus first of all. My plan of
attack is as follows:-

One workstation at a time:

1. Format the workstation. Reinstall Windows.
2. Install all available Windows Updates.
3. Install business class anti-virus software
4. Implement additional protection to prevent reinfection (see below)
5. Ensure complex logon password
6. Join the workstation back into the domain and configure for the
user.

By doing this I'm hoping to gradually one workstation at a time
eradicate the virus from the network and prevent reinfection once the
workstation is re-introduced to the network. Additionally doing one at
a time to prevent mass downtime.

The advice I would appreciate from you guys is:

1. I want to PREVENT re-infection. This is crucial. As well as updates
and AV software I plan on doing the following:

- Complex local admin password
- Block Autorun

Is there anything else I can do on the workstation before
reintroducing it to the network to PREVENT reinfection?

2. Is this the most effective method of removing the virus from the
whole network?


You can't do this one at a time, you need to down all workstations, keep
them off the network, and then do as follows:

Download the Avira Antivir Server product, it will run for 30 days,
install it on the server, reboot, make sure it updated, run a full scan.

Download Avira Antivir and put it on a USB stick, download the manual
updates.

Now, take one of the XP workstations, assuming the company was smart
enough to purchase all the same systems around the same time - wipe it,
reinstall from scratch, install Avira Antivir, connect to the network,
do all the updates, DO NOT JOIN THE DOMAIN YET. Now, SYSPREP the
computer making it ready to clone to the other computers...

http://support.microsoft.com/kb/302577

Now, clone the computer's HD to the other machines that are the same
type/model.

Bring them all online, rejoin them to the domain, install a Enterprise
type AV solution that is managed by the server, don't make local
workstation users LOCAL ADMINISTRATORS.

Next, get them a firewall appliance that can inspect email and HTTP
traffic and remove malware - like the www.watchguard.com units.


--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)
  #13  
Old September 13th 10, 03:59 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Leythos[_2_]
external usenet poster
 
Posts: 976
Default Conficker infection on network - advice wanted on removal/protection

In article ,
says...

On 9/12/2010 12:06 PM, Barry Schwarz wrote:
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote:

snip

Apologies for this... but please repost to
www.sbsforum.info this
newsgroup is closing tomorrow.

While some servers may drop the newsgroup (you didn't identify which
of the three you meant), it will have no affect on the other servers
that carry it.

The reality is that many of us will not find another nntp server, so if
you want the largest pool of helpers, this is the reality.


I think the reality is that Usenet was around long before MS even
learned about email or the Internet and will be around long after it.

The forums are a bad way and cumbersome.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)
  #14  
Old September 13th 10, 07:55 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.hardware,microsoft.public.windowsxp.basics
Jim[_21_]
external usenet poster
 
Posts: 7
Default Conficker infection on network - advice wanted on removal/protection

On Sun, 12 Sep 2010 14:48:46 -0700, Susan Bradley
wrote:

On 9/12/2010 12:06 PM, Barry Schwarz wrote:
On Sat, 11 Sep 2010 18:30:11 -0700, Susan Bradley
wrote:

snip

Apologies for this... but please repost to www.sbsforum.info this
newsgroup is closing tomorrow.

While some servers may drop the newsgroup (you didn't identify which
of the three you meant), it will have no affect on the other servers
that carry it.

The reality is that many of us will not find another nntp server, so if
you want the largest pool of helpers, this is the reality.


Not find another nntp....compared to which? I'm guessing you conect to
a Microsoft NNTP server, but I bet most don't.

I personally do not like the Microsoft forums, I prefer NNTP.


Jim
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 01:32 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.