In some of our isa profiles, web client can't see images on some web sites.
All you see is text and red x's as images. How can I fix that? Rules are set
in a way that all destination is blocked except selected set which of cours
include the sites. http content is set to All content groups
--
Thanks in advance.
Steve Amirault
> In some of our isa profiles, web client can't see images on some web
> sites.
> All you see is text and red x's as images. How can I fix that? Rules are
> set
> in a way that all destination is blocked except selected set which of
> cours
> include the sites. http content is set to All content groups
perhaps these images are from off-sites-destinations? check the source code
of the sites if that's the problem.
--
greets, jens mander...
www.aixperts.de
www.forefront-tmg.de
www.hentrup.net
|<-|
Thanks
--
Thanks in advance.
Steve Amirault
"Jens Mander" wrote:
> .
>
Thanks in advance.
Steve Amirault
"Jens Mander" wrote:
> .
>
> I noticed it is a https site. Could it be something wrong in the config
> that
> will prevent images and javascript menus to be properly shown? One of the
> site si www.toro.com. That one is fine till you click on links taht will
> redirect to a https site. Thats' where you can't see anything but plain
> text.
do you allow https? if not - no pix! ;-)
Thanks in advance.
Steve Amirault
"Jens Mander" wrote:
> .
>
> Well I guess I d oallow those https sites since uses can access hotmail or
> banking sites with no problem. Anyways, I do I make sure I allow https?
a look in your logfiles will give you the answer.
Thanks in advance.
Steve Amirault
"Jens Mander" wrote:
> .
>
Please define "doesn't work".
What exactly do you see?
What is the exact error seen in the browser when it fails?
This is looking more and more like a browser security settings issue in the
Internet Zone and not an ISA issue.
Try the same sites with Firefox.
--
Phillip Windell
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
I mean that on the same computer, using controled ISA client profile, I
can't access the site. ISA blocks it event if the site is authorised On the
same computer using another profile which is allow to browse Internet with
less restrictions, I can access the Web site. So there is something with the
other profile and it has nothing to do with the browser or th security. I
just can't access it.
--
Thanks in advance.
Steve Amirault
"Phillip Windell" wrote:
> .
>
Thanks in advance.
Steve Amirault
"Jens Mander" wrote:
> .
>
That does not change things much. Browser security settings are part of the
user profile,...so they are based on the user, not the machine,...so that is
where you should look.
The ISA Access Rule could potentially be the cause,...but it is certainly
not the first place I would look.
You need to test using the same user account from multiple
workstations,...unless you are forcing browser settings with GPOs,...then
that wouldn't help much because the same problem would be "pushed" to all
the machines.
> Where in the log files and how shoud I see whether or not https is
> allowed?
you can "see" the logfiles in the monitoring-area. just adjust the filter
pointing to your client and try to access the website(s). than you should
see what happens.
look at your firewallrules, if https is allowed or not.
"Phillip Windell" wrote:
> .
>
I added the IP adresse of the domain name and it works??? Does it means an
issue between the ISA and DNS?
Thanks for your time and support.
"Phillip Windell" wrote:
> .
>
Thanks for your time and support.
"Jens Mander" wrote:
> .
>
No,..it probably means that the Site developers empeded links in the site
that use IP Numbers instead of the name. It could also mean that parts of
the Site may use a Java Applet running off of a locally installed Java JRE
which can cause a situation where the user's machine is doing it's own DNS
Resolution before sending the request from their browser to the ISA which
causes ISA to only see the IP# and be unaware of the Name which results in
the access failing. It could also be any circumstance which would cause the
client machine to operation as a Firewall Client or a SecureNat instead of a
Web Proxy Client for portions of the Site. Only Web Proxy Clients can work
with Domain Sets or URL Sets.
Domain Sets and URL Sets are only partially effective. It doesn't matter if
it is an "allow" or a "deny" situation. They almost always need to be
backed up with Address Sets as well in the same Rule.
> Got it! I coud find another domain name that needed to be added to the
> access
> list. It works fine now.
nice. whitelisting is a lot of work. ;-)
> Thanks for your time and support.
you are welcome!