PDA

View Full Version : SpyBot's immunize doesn't see Windows 2000 SP4's hosts anymore.



antdude
2008-12-11, 08:23
Hi.

I noticed SpyBot's immunize no longer sees my old updated Windows 2000 SP4's global hosts file. I have to use its Tools -> Hosts File to add the lines to my c:\winnt\system32\drivers\etc\hosts file. And this is the original hosts file from 2002. Any ideas what happened to this immunize feature?

Thank you in advance. :)

md usa spybot fan
2008-12-11, 15:04
antdude:

Check the following registry key:


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
Make sure that the ValueName "DataBasePath" points to the path of your HOSTS file:
%SystemRoot%\System32\drivers\etc

antdude
2008-12-15, 01:40
antdude:

Check the following registry key:


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
Make sure that the ValueName "DataBasePath" points to the path of your HOSTS file:
%SystemRoot%\System32\drivers\etcYes, it's there. Sorry for not replying so fast since I got busy. :(

md usa spybot fan
2008-12-15, 07:12
antdude:

If that registry entry is pointing to the correct location and the file is named HOSTS (without any file extention), Spybot should be able to find it.

antdude
2008-12-15, 07:24
antdude:

If that registry entry is pointing to the correct location and the file is named HOSTS (without any file extention), Spybot should be able to find it.Well, only immunize feature doesn't see it. If I use Tools -> Hosts, then it sees it. So weird.

PepiMK
2008-12-15, 16:25
This (http://forums.spybot.info/project.php?issueid=164) is the reason. Unless the DNS Client Service is disabled, immunizing the hosts file on 2000 might slow down the machine, so to avoid that problem, hosts file immunization is disabled if the DNS Client is active.

This can be overridden through this tweak (http://wiki.spybot.info/index.php/Registry_Tweaks#ImmunizeHostsOn2000) if you are sure you want it and do not want to disable the DNS Client.

antdude
2008-12-15, 18:56
This (http://forums.spybot.info/project.php?issueid=164) is the reason. Unless the DNS Client Service is disabled, immunizing the hosts file on 2000 might slow down the machine, so to avoid that problem, hosts file immunization is disabled if the DNS Client is active.

This can be overridden through this tweak (http://wiki.spybot.info/index.php/Registry_Tweaks#ImmunizeHostsOn2000) if you are sure you want it and do not want to disable the DNS Client.Interesting. When was this checking feature added? I will have to look into this.

PepiMK
2008-12-15, 21:42
The bugtracker says 1.5.2 final as "Implemented version". As long as the hosts file was still immunized, it still showed up though to allow users to undo a previously made immunization.

antdude
2008-12-15, 21:51
The bugtracker says 1.5.2 final as "Implemented version". As long as the hosts file was still immunized, it still showed up though to allow users to undo a previously made immunization.Yeah, I think I overinstalled v1.5.2 over v1.5.1 when it came out months ago.

I wonder if this issue is related to the old unresolved issue: http://forums.spybot.info/showthread.php?t=35391 :( ....

antdude
2008-12-15, 21:54
This (http://forums.spybot.info/project.php?issueid=164) is the reason. Unless the DNS Client Service is disabled, immunizing the hosts file on 2000 might slow down the machine, so to avoid that problem, hosts file immunization is disabled if the DNS Client is active.

This can be overridden through this tweak (http://wiki.spybot.info/index.php/Registry_Tweaks#ImmunizeHostsOn2000) if you are sure you want it and do not want to disable the DNS Client.XP has this service too, so how come it is supported for enabled service?

PepiMK
2008-12-15, 22:40
Because on XP, we didn't notice that slowdown on any machine. Guess Microsoft did update the service between the two versions ;)

There are - very few - reports that there is a slowdown on XP as well, but those are very rare compared to nearly everyone having the slowdown on 2000.

antdude
2008-12-15, 22:56
Because on XP, we didn't notice that slowdown on any machine. Guess Microsoft did update the service between the two versions ;)

There are - very few - reports that there is a slowdown on XP as well, but those are very rare compared to nearly everyone having the slowdown on 2000.Ah. So what is this DNS Client Service? Windows has its own DNS to use? I thought OS were looking up on remote DNS'.

md usa spybot fan
2008-12-16, 00:17
antdude:

Does the following reference answer your question?
Blocking Unwanted Parasites with a Hosts File
http://mvps.org/winhelp2002/hosts.htm

Editors Note: in most cases a large HOSTS file (over 135 kb) tends to slow down the machine. This only occurs in W2000/XP/Vista. Windows 98 and ME are not affected.

To resolve this issue (manually) open the "Services Editor"

Start | Run (type) "services.msc" (no quotes)
Scroll down to "DNS Client", Right-click and select: Properties/[b]
Click the drop-down arrow for [B]"Startup type"
Select: Manual, or Disabled (recommended) click Apply/Ok and restart. [more info]

antdude
2008-12-16, 00:35
antdude:

Does the following reference answer your question?
Blocking Unwanted Parasites with a Hosts File
http://mvps.org/winhelp2002/hosts.htm"If your machine is part of a "Domain", check with your IT Dept. before applying this work-around. This especially applies to Laptop users who travel or bring their machines home. Make sure to reset the Service (if needed) prior to connecting (reboot required) to your work Domain ..." helped. :) I will try disabling it since it is an old desktop at home's LAN (no domain and no IPCOP).

antdude
2008-12-19, 08:43
"If your machine is part of a "Domain", check with your IT Dept. before applying this work-around. This especially applies to Laptop users who travel or bring their machines home. Make sure to reset the Service (if needed) prior to connecting (reboot required) to your work Domain ..." helped. :) I will try disabling it since it is an old desktop at home's LAN (no domain and no IPCOP).Cool, it worked in this old W2K SP4. :) Hopefully, disabled DNS Client service didn't break anything!