Pulse making changes to local host file

[NatashaW_]

Hi Guys,

Has anybody come across this issue whereby you are on the LAN, and edit the host file with, say, a manual server entry. Then go home, connect via Pulse, and the entry is gone?

I've had a report of this from a subset of users with local admin access. The entry in question is the loopback address of 127.0.0.1    localhost

I have been unable to replicate this issue myself and the full hosts file should look like this:-

Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#    127.0.0.1       localhost (this is the entry being removed)
#    ::1             localhost

Any ideas?

Thanks

Natasha

[spuluka]

The host file is modified during use of the tunnel by pulse or network connect as documented in KB19294

http://kb.pulsesecure.net/InfoCenter/index?page=content&id=KB19294

But this is related to dns resolution for the end point of the tunnel not the local host home address.

[NatashaW_]

Many thanks for the reply Spuluka.

Turns out it was AnyConnect making the change, not Pulse.

Cheers,

Natasha