Don't all rush but win2kSP3 available from here

[LvR]

Yeah - if all else fails that is the way to do it, and Im doing it that way too in addition to refusing to install auto update(in the past that is )with Norton4.

Victorian - why not just export that key for possible restoration, and then delete the thing - tell us what you see happen.

[Victorian]

Originally posted by KvHagedorn
Here's how I do it. Not only for W2k but for other software that might try and phone home.. I have Sygate installed and refuse NTkernel permission to access the internet when it wants to.

So it's the NTkernal that runs auto update? I thought that it would be something along the lines of a 'dedicated' function with it's own *.exe

edit:

Just thought of something, the function could be built into a dll file instead of an exe couldn't it?

[Marshmallowman]

even easier

find the upload address, (as long is not a simple IP number)
and put it your hosts files as a loopback

eg
C:\WINNT\system32\drivers\etc\hosts
add something like

127.0.0.1 update.microsoft.com

also works to stop adds and popups in web pages

[Victorian]

Originally posted by LvR
Yeah - if all else fails that is the way to do it, and Im doing it that way too in addition to refusing to install auto update(in the past that is )with Norton4.

Victorian - why not just export that key for possible restoration, and then delete the thing - tell us what you see happen.

Only problem is, I might not actually see anything happen if that key isn't what actually controls the function.

As I'm not all that knowledgeable about the registry I have a quesion regarding the key that I found. In the 2nd string (is that what it's called? or is it a value?):

AUOptions Reg_DWORD 0x00000000 (0)

that last 0 in brackets is a yes/no value isn't it?If the 0 means yes and I change it to 1 for no that would appear to take care of auto update would it not? If the 0 stands for no then I can just leave it as is and it should be ok?

Only problem is, I have no idea if the 3 lines in question actually control the auto update function or not....

[Victorian]

Originally posted by Marshmallowman
even easier

find the upload address, (as long is not a simple IP number)
and put it your hosts files as a loopback

eg
C:\WINNT\system32\drivers\etc\hosts
add something like

127.0.0.1 update.microsoft.com

also works to stop adds and popups in web pages

Doesn't that have the potential to screw up manual updates though as you wouldn't be able to access the Windows Update site?

[KeiFront]

You can still use download.microsoft.com to download updates and hotfixes.

[RobP]

Or you could just disable the automatic updates service in the management console

[Victorian]

Ok, discovered that you don't have to have automatic updates after all. I just had a window pop up that asked me if I wanted to configure auto updates and one of the options is to not have it auto update at all.

Looking at the help file for the function informs you that you can change your settings at any time by going into the control panel\settings and clicking on the automatic updates icon.

So, after all that fuss it seems like everything is cool after all.

[LvR]

There are those people that would have you believe that to be the case, and Bill is one of them. I would monitor my firewall very closely after installation of SP3 just to be sure

[Victorian]

Originally posted by LvR
There are those people that would have you believe that to be the case, and Bill is one of them. I would monitor my firewall very closely after installation of SP3 just to be sure

I always do but realistically if Microsoft really wants a 'back door' there's not a lot we can do about it because it could, I suspect, be coded into any part of the OS that needs to be allowed access to the 'net. The same goes for any other OS I guess.

BTW. I checked the keys that I noted before and the value for AUOptions Reg_DWORD 0x00000000 (0) has been changed to AUOptions Reg_DWORD 0x00000000 (1) since I checked *not* to access updates automatically.

[Wombat]

I always do but realistically if Microsoft really wants a 'back door' there's not a lot we can do about it because it could, I suspect, be coded into any part of the OS that needs to be allowed access to the 'net. The same goes for any other OS I guess.

No, there are things you can do about it. Somebody mentioned firewalls, and that's the way to do it. Remember, corporations use this software too, and they can't be bothered with 10000 machines bitching about not being able to access a site.

[GNEP]

Can't you just keep the computer offline?



Easy enough for me - I am still on pay-by-the-minute 56k at home!

gnep

[Victorian]

Originally posted by Wombat
No, there are things you can do about it. Somebody mentioned firewalls, and that's the way to do it. Remember, corporations use this software too, and they can't be bothered with 10000 machines bitching about not being able to access a site.

No, I understand using a firewall, what I was saying that if Microsoft (or any other OS company) really wants a 'back door' could they not code it into a part of the OS that *has* to be granted access to the net? If that's the case, how would using a firewall be of any use in preventing the 'back door' being used?

If it can't be done, then everything's peachy keen.

[High_Jumbllama]

They could block the specific address/port combination for the update mechanism as long as some other function does not go through the same address/port combination. This would not block all traffic from one executable or Dynaic Link Library.

[Wombat]

No, I understand using a firewall, what I was saying that if Microsoft (or any other OS company) really wants a 'back door' could they not code it into a part of the OS that *has* to be granted access to the net? If that's the case, how would using a firewall be of any use in preventing the 'back door' being used?

No. There's no way MS could release the OS so that it "had" to talk to MS. That's too much of a security risk. Besides, the hardwrae firewalls would block it.