Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 5986 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IE Proxy - IP Address vs FQDN vs external domain name

ETFan

Maybe a simple question/answer, but just curious of the behavior we see using different options in IE proxy settings.

 

We use AD and standard web filtering. IE proxy is set with a GPO.

Our UTM (SG 330 9.31) has the following resolutions:

By IP: 192.168.0.15

By FQDN: utm.company.local

By External (and internally resolvable): utm.company.org

The FQDN and the external doamin name both resolve (when used internally) to 192.168.0.15. 

In internet explorer, only the FQDN (utm.company.local) will allow IE to find web pages. If I use the IP or the .org address of the utm IE returns a "Page not found" immediately when try to surf the web. What would cause this?

 

EDIT: Really I guess my question is, can I configure the device to accept any of these?



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to ThorstenSult

    I looked through that thread just now, we don't have problems resolving the FQDN (.org or .local) or the IP from any device. The clients resolve it perfectly, it's just that when IE goes to send the requests to the proxy, it doesn't make it for some reason if we use the .org FQDN or the IP. Only the .local FQDN works.

    Might be an authentication error I suppose, since our domain is .local (it wasn't me!) but I would think the IP address in the proxy should work. 

Children
Unfiltered HTML