https not running on Internal IP address.

So there are a few things going on here:

1. The SSL Cert is fixed to a specific domain or hostname in a domain.  Depends on the certificate type.  for example:  if you use an SSL Cert for www.YourDomain.ext on a server with www.NotMyDomain.ext, you will get an error stating that the hostname of the website does not match what is configured in the SSL Cert.

2. If a site in IIS is setup to be accessed on a specific IP, it will not answer if you try to access it with another IP.  Irrelevant if the server has more than 1 IP configured on it.

Is there a reason you want your internal users to access the secure website from an internal IP?

Dan

Let me explain again.Suppose my public url is www.myweb.com I have taken certificate for that . Now in IIS ,my internal URL is http:192.168.8.8 for www.myweb.com ,if I m trying to access it using https:192.168.8.8,Then it does not work But https:\\www.myweb.com  is working.

Regards,
Sudhanshu

Well, the URL www.myweb.com matches what is in the SSL Certificate configuration.  If you go to the website using the IP 192.168.8.8, you will get an error because the SSL Cert does not care what the site's IP is.

The Cert will only properly function if the hostname, domain and extension match what is in the SSL Cert.

There is nothing wrong with your certificate.

If you intend to serve content using https, then everyone should access the website using the URL (fully qualified domain name - FQDN) that is in the certificate.

Dan