Error with secured sites on Intranet

[joegz]

Has anyone ever run across this issue before.

Client is using IE5 and can connect to secured Internet sites with no problem. Connecting to secured Intranet sites comes back with an error that the page is unavailable.

Since Internet secured sites work so I kind of doubt that it is a secuity channel problem with the browser. It is not DNS either because I will get the same error if I just enter the IP address for the web site rather than the URL. and the DNS is pingable.

We have the domain listed in the exception list so the browser knows not to use the proxy for the address. The only other error I could produce was I added the URL address to the exception list and got an error that the security certificate is invalid before it starting pulling the same unavailable web site message.

In contrast Netscape on the same machine works without a problem. Also tried clearing the IP information and starting over just to make sure it was not a binding issue with the protocol.

Because this is in a corporate envrionment there is no "Repair" feature that I can use without having to reload the whole OS. (I know kind of dumb but that is how the application was integrated by the parent company...they do lots of dumb things like this.)

Any ideas is appreciated. joegz
"Sometimes you just need to find out what it's not first to figure out what it is."

 

[cdogg]

Is the browser being routed through a proxy server? Check LAN Settings under Connections. Try clearing any checkmarks, hit OK and restart IE.

If that doesn't work (because pc's can be manually directed through Proxies), you may need to have the SA clear cache out on the network firewall or proxy server, whatever they have.

~cdogg

 

[joegz]

Thanks for the info. Because this is an Intranet site there is no proxy server involved in order for the client to reach the site (this is what is puzzling me the most as most problems I face are when the clients try to get to an Internet site through the proxy).

The domain is listed as an exception so the browser knows not to try to look for the site via the proxy server. joegz
"Sometimes you just need to find out what it's not first to figure out what it is."

 

[Tech4U]

Oddly enough this is somewhat the same problem that I am dealing with right now. Normally, I would have the user rename or replace the Wintrust.dll file. This usually works without a hitch. Now though when I do that I get the same error. I have also tried to repair the internet explorer installation. This also did not work. Hopefully someone has some more information concerning this problem.

So my suggestion to you is to look towards the Wintrust.dll file as a possible problem. I would just try to rename it or copy it from another machine. Hopefully, someone has an answer for me

Thanks!

-T

 

[cdogg]

I know this seems very basic, but did you already check the following:

Under Tools->Internet Options->Security, is the slider for Local Intranet set to "Low"

Under Tools->Internet Options->Advanced, is SSL 2.0 and SSL 3.0 selected?

If you go to

http://www.verisign.com,

click the "Secure Site" icon in the lower-right corner (gold medal icon), does another window pop up and tell you "Status Valid"?

If you go to the Help->About Internet Explorer, does the cipher strength say 128-bit?


If all these check out, then I'm stumped. If you find another answer, please let all of us know!

~cdogg

 

[joegz]

Thanks for the tips. I'll check on the Wintrust.dll file.

As far as the security settings and SSL setings those were also checked and changed just to test and those did not make a difference to the issue. The cipher strength does read 128 kb.

I have not tried the verisign site but will do so and see what I find.

Secured sites do work when they are Internet sites and going through the proxy server. It is more like the browser can't find the secured sites on the Intranet.

This is just the strangest behavior I have ever experienced. joegz
"Sometimes you just need to find out what it's not first to figure out what it is."

 

[RedTech]

Just out of curosity is the local intranet site in the 192.168.1.x net?

 

[joegz]

No the address is not in that IP range. joegz
"Sometimes you just need to find out what it's not first to figure out what it is."

 

[cdogg]

Just a few more questions...

What's the Intranet URL look like?
When, if ever, did this last work for the Client?
You cleared all temp int files & cookies?
Do other clients work fine with same version of IE?


~cdogg

 

[Tech4U]

Well, the problem that I was experiencing was because of a router. Someone broke into one of our offices and stole the router. They replaced it and that caused everyone's problem. So that may be something else to look at for your intranet. Not sure what they did to the router to fix the problem at the moment, but I will try to find out.

-T