Hosts records not writen / Bug Reports / NetSetMan Support

NetSetMan Support

Search for already answered questions about NetSetMan (Pro) or ask new ones

You are not logged in.

#1 2018-12-05 20:26

brokengillou
Member
Registered: 2018-12-05
Posts: 3

Hosts records not writen

Hi,

     Hosts records can't be written, /etc/hosts disappeared...
Is it related to a Microsoft dns dll?

Best Regards,

Gilles

Microsoft Windows [version 10.0.17134.407]
NetSetMan 4.7.1
Kaspersky 10.3.0.6294 mr1.mr2
SpyBot 2.7.65.0
Ubuntu 18.04.1 LTS (Bionic Beaver)

Last edited by brokengillou (2018-12-05 21:12)

Offline

#2 2018-12-05 20:56

brokengillou
Member
Registered: 2018-12-05
Posts: 3

Re: Hosts records not writen

Need to get some sleep...
Fact i finally got it %WINDIR%\System32\drivers\etc\hosts
But it's empty my values are not written...
Confirms the fact that nothing to view when clicking on "Get Current Values".
Editing trough Ubuntu console ... overwrite ...
Editing through notepad admin ... ok
No effect in NetSetMan.

Last edited by brokengillou (2018-12-05 21:24)

Offline

#3 2018-12-11 11:22

NetSetMan Support
Administrator
Registered: 2005-08-06
Posts: 1,878

Re: Hosts records not writen

brokengillou wrote:

Need to get some sleep...

Have you tried it again after getting some sleep? wink

There's actually not much that could go wrong modifying the hosts file. So we're a bit clueless regarding your observations. The only possibility we see is that the hosts file is monitored or overwritten by another application.

If you think, NetSetMan is writing to a wrong location, you could use Windows Sysinternals Process Monitor to observe the activation process and see which hosts file is being accessed.

Offline

#4 2018-12-19 10:41

brokengillou
Member
Registered: 2018-12-05
Posts: 3

Re: Hosts records not writen

NetSetMan Support wrote:
brokengillou wrote:

Need to get some sleep...

Have you tried it again after getting some sleep? wink

There's actually not much that could go wrong modifying the hosts file. So we're a bit clueless regarding your observations. The only possibility we see is that the hosts file is monitored or overwritten by another application.

If you think, NetSetMan is writing to a wrong location, you could use Windows Sysinternals Process Monitor to observe the activation process and see which hosts file is being accessed.

As i said i managed to edit fine but netsetman doesn't, "Get Current Values" gives a blank list which is neither the current state or netsetman list.
     

Confirms the fact that nothing to view when clicking on "Get Current Values".

I carry on getting clues as you proposed.

So, clicking on "Get Current Values" gives:

2IWs6FGaeYqN.JPG

Thanks

Gilles

Last edited by brokengillou (2018-12-19 11:07)

Offline

#5 2018-12-20 18:08

NetSetMan Support
Administrator
Registered: 2005-08-06
Posts: 1,878

Re: Hosts records not writen

The "Get Current Values" button reads the settings from the hosts file that have been written by NetSetMan. It doesn't read any other lines from the hosts file. The lines are determined by start/end identifier lines.
In the hosts file it looks like this:

############################## NSM START ##############################
127.0.0.1 nsmtest
############################### NSM END ###############################

If you want, you can actually try it out yourself. Copy the sample code above manually into your hosts file and save it. Then use the "Get Current Values" button in NetSetMan to see if that line is read. Then at least you'll know if you're editing the same file that is accessed by NetSetMan.
To see if your manual edit was done correctly, you can open the command line (cmd.exe) and execute:

ping nsmtest

Does this return a ping from 127.0.0.1?

Your screenshot shows access to the registry, but no file access. Could you please doublecheck your configuration of Process Monitor?

Offline

#6 2019-04-30 12:57

Mourer
Member
Registered: 2019-04-29
Posts: 1

Re: Hosts records not writen

NetSetMan Support wrote:

The "Get Current Values" button reads the teeth whitening kits results settings from the hosts file that have been written by NetSetMan. It doesn't read any other lines from the hosts file. The lines are determined by start/end identifier lines.
In the hosts file it looks like this:

############################## NSM START ##############################
127.0.0.1 nsmtest
############################### NSM END ###############################

If you want, you can actually try it out yourself. Copy the sample code above manually into your hosts file and save it. Then use the "Get Current Values" button in NetSetMan to see if that line is read. Then at least you'll know if you're editing the same file that is accessed by NetSetMan.
To see if your manual edit was done correctly, you can open the command line (cmd.exe) and execute:

ping nsmtest

Does this return a ping from 127.0.0.1?

Your screenshot shows access to the registry, but no file access. Could you please doublecheck your configuration of Process Monitor?

Can you easily remove that piece of code the same way you added it into the hosts file? I am going to try this solution too.

Last edited by Mourer (2023-09-01 18:14)

Offline

#7 2019-04-30 15:49

NetSetMan Support
Administrator
Registered: 2005-08-06
Posts: 1,878

Re: Hosts records not writen

By applying an empty hosts list, NetSetMan removes that block from the hosts file completely.

Offline