Rob Steinmetz wrote:
I have a remote site. The people at that site cannot access a internal
website we use at another location. I have had the users clear their
cache and try to access the site. Chrome on the same machines can access
the site. They can ping the ip address.
I'm looking for a way to figure out what is causing SeaMonkey to not
load the website.
Please define "can't access." Do they get a DNS error, a 404 error, a
SeaMonkey certificate error, a blank page, or what? I assume DNS is fine
if Chrome can access it and they can ping it. But you need to give the
experts here some clues to work with.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
