Skip navigation
This discussion is archived
8221 Views 5 Replies Latest reply: Aug 24, 2009 8:49 AM by phoffmann RSS
Rookie 3 posts since
Aug 21, 2009

Has received 1 of 9 achievements.
Currently Being Moderated

Aug 21, 2009 6:04 PM

LMS generated line in client hosts-file

Hi guys, we experience a strange issue with proxy-autoconfig (proxy.pac).

The JavaScript-function myIpAddress() which should return the clients IP-address always returns 127.0.0.1.

This function is used to determine when the client should use the corporate proxy or go directly to the internet based on which subnet its on.

 

We tracked down the problem to be caused by the following lines which the LANDesk-agent appends to the client computers hosts-file:

 

# 127.0.0.1   localhost

127.0.0.1      computername # LMS GENERATED LINE

 

Please notice that the original line is commented out by the LANDesk agent.

If we remove the line Landesk added, the proxy.pac-script works just fine.

What is the purpose of Landesk changing the clients hosts-file like this? Is there a way to work around this issue?

 

Cheers

Rolf

  • Apprentice 42 posts since
    Apr 15, 2008

    Has received 2 of 9 achievements.
    Currently Being Moderated
    1. Aug 23, 2009 2:47 AM (in response to morbo)
    Re: LMS generated line in client hosts-file

    Hello,

    I haven't solution for your problem, but in my company, when a HP computer have Intel AMT activated, the line below is add in the host file:


    127.0.0.1 HPSystem # LMS GENERATED LINE

     

    I hope that can help you

     

    Regards

     

    Pleix

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    3. Aug 24, 2009 2:20 AM (in response to morbo)
    Re: LMS generated line in client hosts-file

    I suspect that this might be a HP-specific workaround to be able to AMT-provision the devices well. A few of the OEM's have folks jump through a few unusual hoops when it comes to AMT I've come to learn over the time, and this looks like one of them (I don't have HP systems, so this is theorizing at this point, but if the AMT provisioning works, and we forcibly do this for HP-systems, it stands to reason that this is so).

     

    - Paul Hoffmann

    LANDesk EMEA Technical Lead

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    5. Aug 24, 2009 8:49 AM (in response to morbo)
    Re: LMS generated line in client hosts-file

    It wasn't a dig at HP per se - it was more of an explanation that I've seen various OEM's do apparently "strange" things when it comes to AMT that don't seem to be documented anywhere, and then end up with stuff like this resulting in the scratching of heads .

     

    In general, AMT seems to be particularly prone to "special workarounds" or whatnot, for one reason or another. Maybe just someone got burned on version 1 of AMT, and whatever workaround was in place then is still in place now? Historical artifacts like that could explain a fair bit ...

     

    - Paul Hoffmann

    LANDesk EMEA Technical Lead.

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 20 points
  • Helpful Answers - 10 points
LANDESK Community powered by Jive SBS® 4.5.7.1  |  Legal Notices  |  Privacy Policy  |  Icon 

TweeterOn Twitter  |  Icon FacebookOn Facebook © 2007 LANDESK Software