Isolating XP from the net

[meebers]

When MS finally pulls the plug on XP, how can I isolate it from the web. I still want to be able to turn it on and work with it, but I want to stop all the programs that search for updates etc. I still want it to be part of my internal network though.

 

[windude99]

To answer your question, I would not recommend using it for anything related to the internet. Just disconnect the network cable or (if it has wifi) disconnect it from your wireless network.

 

[3D Jed]

clearing the default gateway should do it

 

[alphanumeric]

You should be able to do that in your router. Set a static IP on that PC and then block Internet Access for that IP address. It should still have LAN access but be blocked from WAN access (the internet). Another way to do it is to block the MAC address of that PC's NIC in the router from accessing the Internet.

 

[UsernameIssues]

You should be able to do that in your router. Set a static IP on that PC and then block Internet Access for that IP address. It should still have LAN access but be blocked from WAN access (the internet). Another way to do it is to block the MAC address of that PC's NIC in the router from accessing the Internet.

What alphanumeric said...
...but with a picture
http://www.sevenforums.com/network-...ternet-access-not-connection.html#post2708603

 

[margrave]

Wiping out the default gateway is a good (and simple) solution ... so long as the user only needs to "see" his own subnet. But he won't be able to cross over to another, local subnet.

That's fine at home where there's likely only one subnet. But not so good in a business environment with multiple subnets.

 

[whs]

But isn't all that an overkill. Program updates should not really be a problem and if you think so, throw all the update services out of the startups. And MS updates (if there are still any) can be blocked in the Windows update settings.

Just stay away from the net with XP and use a virtual Linux machine to access the web. That gives you 100% security for the XP system and if the virtual machine crashes, just roll in the backup folder. 5 minutes later you'll be up and running again.

Besides, it is not a bad idea to make periodic images of the whole XP system. Really no need to cripple your system beyond recognition.

 

[alphanumeric]

Wiping out the default gateway is a good (and simple) solution ... so long as the user only needs to "see" his own subnet. But he won't be able to cross over to another, local subnet.

That's fine at home where there's likely only one subnet. But not so good in a business environment with multiple subnets.

You have to be careful setting what static IP you use to. You'll want to use one that is outside of the scope your router uses to avoid having two PC's with the same IP address.