Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » Up and Running » Security » Wireless Security » Securing shared wireless network with infected PC
Uniqs:
685
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
« How-to: Active Directory and PEAP / EAP-TLS / PEAP-TLS  
cardlady

join:2006-08-31
Kansas City, KS

Securing shared wireless network with infected PC

I plan on reformatting 2 computers on my wireless network that may be infected and there is a third computer on the network the user of which will not allow reformatting. If I clean those 2 is there any way to prevent being reinfected by the third computer when I connect back to the network? My wireless router has an A and a G network. Would keeping them on separate networks keep the other 2 safe?
docrice

join:2008-03-31
Fremont, CA

Re: Securing shared wireless network with infected PC

I somewhat doubt your access point has a way to bridge 802.11a and 802.11g networks separately through some sort of partitioning mechanism (separate VLANs, for example). Most home devices don't have that level of functionality.

Since the AP will more than likely bridge everyone on a common collision domain, the easiest way to reduce your risk exposure is by using a software firewall on each of your reformatted stations.

Or you can be a bit cruel and just change the access key to the Wi-Fi network (assuming you're running WPA or WPA2 via pre-shared key mechanism) and tell that owner of the third machine that until s/he sterilizes the machine with rubbing alcohol, soap, and various anti-malware software, he stays off your network. It's a bit tricky if he has physical access to your router and a spare Ethernet cable.
cardlady

join:2006-08-31
Kansas City, KS

Re: Securing shared wireless network with infected PC

Thanks.

Angelo_
The Network Guy
Premium
join:2002-06-18

Re: Securing shared wireless network with infected PC

i dont know how complex your network is but you can jail or deny internet access to the infected pc from the rest of network.

tipstir

join:2004-11-14
Enfield, CT
·Cox HSI

said by cardlady See Profile :

I plan on reformatting 2 computers on my wireless network that may be infected and there is a third computer on the network the user of which will not allow reformatting. If I clean those 2 is there any way to prevent being reinfected by the third computer when I connect back to the network? My wireless router has an A and a G network. Would keeping them on separate networks keep the other 2 safe?
Outbound network flood attacks sensor
Forums » Up and Running » Security » Wireless Security« How-to: Active Directory and PEAP / EAP-TLS / PEAP-TLS  


Wednesday, 25-Nov 07:28:48 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [103] New AT&T Ad Campaign Hits Back At Verizon
· [85] New Bill Takes Aim At Higher Verizon ETFs
· [85] Apple Joins AT&T Verizon Snark Fest
· [40] In-Flight Internet Headed For Bumpy Landing?
· [32] Senators Want ACTA Made Public
· [30] Earthlink Suffers From Major E-mail Outage
· [30] AT&T Offers New Prepaid Wireless plans
· [28] Frontier Increases Modem Rental Fee
· [20] Despite Billions In USF Fees, U.S. Libraries Lack Bandwidth
· [16] Vivendi In Way Of Comcast's NBC Desires
Most people now reading
· Windows 7 boot manager editing questions [Microsoft Help]
· Mysterious $800 Cash Deposit? [General Questions]
· [Rant] Damn Sermons through my speakers! [Rants, Raves, and Praise]
· Climate Change Scandal Erupts After Email Hack. [Security]
· Opening a file download dialog from a JavaScript function. [Webmasters and Developers]
· What to use while demonoid is down? [Filesharing Software]
· "ISP owners could face jail under child porn bill" - CBC [Canadian Broadband]
· HOW-TO: QoS and Tomato (fixes "choppy voice") [MagicJack]
· Getting ready to pull the trigger, still have cold feet. [VOIP Tech Chat]
· Several MS Updates today (11/24/2009). [Security]