IE 11 Cannot access HTTPS on non standard port
up vote
0
down vote
favorite
I have a road warrior who is accessing one of our server from its IP address.
Since few days he cannot access to a service which listen on 8443 https tcp port. HTTP version works well on port 8080
The url is valid and work well with other browsers like chrome, but IE and Edge fails with DNS Error.. I cannot understand why DNS is used in this situation.
URL is like:
https://192.168.0.2:8443/foo/bar
I've tested a lot of things, ran anti-malware, disabled IE functionality and re-enabled, disabled antivirus, reset all parameters... without any success.
Does anybody have an idea?
windows-10 internet-explorer https
asked Jun 22 '16 at 8:44
maxxvw
38139
add a comment |
up vote
0
down vote
favorite
I have a road warrior who is accessing one of our server from its IP address.
Since few days he cannot access to a service which listen on 8443 https tcp port. HTTP version works well on port 8080
The url is valid and work well with other browsers like chrome, but IE and Edge fails with DNS Error.. I cannot understand why DNS is used in this situation.
URL is like:
https://192.168.0.2:8443/foo/bar
I've tested a lot of things, ran anti-malware, disabled IE functionality and re-enabled, disabled antivirus, reset all parameters... without any success.
Does anybody have an idea?
windows-10 internet-explorer https
asked Jun 22 '16 at 8:44
maxxvw
38139
What's the specific error message?
– ivan_pozdeev
Jun 22 '16 at 8:47
~"Internet Explorer cannot access to this web page" from debug console i see "dnserror"
– maxxvw
Jun 22 '16 at 8:48
Possible reason is likely IE settings (invalid/untrusted certificate, unsupported TLS version, custom network settings).
– ivan_pozdeev
Jun 22 '16 at 8:49
"dnserror.htm" is a generic error page. IIRC somewhere at the bottom, it gives a more technical formulation.
– ivan_pozdeev
Jun 22 '16 at 8:51
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a road warrior who is accessing one of our server from its IP address.
Since few days he cannot access to a service which listen on 8443 https tcp port. HTTP version works well on port 8080
The url is valid and work well with other browsers like chrome, but IE and Edge fails with DNS Error.. I cannot understand why DNS is used in this situation.
URL is like:
https://192.168.0.2:8443/foo/bar
I've tested a lot of things, ran anti-malware, disabled IE functionality and re-enabled, disabled antivirus, reset all parameters... without any success.
Does anybody have an idea?
windows-10 internet-explorer https
asked Jun 22 '16 at 8:44
maxxvw
38139
I have a road warrior who is accessing one of our server from its IP address.
Since few days he cannot access to a service which listen on 8443 https tcp port. HTTP version works well on port 8080
The url is valid and work well with other browsers like chrome, but IE and Edge fails with DNS Error.. I cannot understand why DNS is used in this situation.
URL is like:
https://192.168.0.2:8443/foo/bar
I've tested a lot of things, ran anti-malware, disabled IE functionality and re-enabled, disabled antivirus, reset all parameters... without any success.
Does anybody have an idea?
windows-10 internet-explorer https
windows-10 internet-explorer https
asked Jun 22 '16 at 8:44
maxxvw
38139
asked Jun 22 '16 at 8:44
maxxvw
38139
asked Jun 22 '16 at 8:44
maxxvw
38139
asked Jun 22 '16 at 8:44
maxxvw
38139
asked Jun 22 '16 at 8:44
maxxvw
38139
38139
What's the specific error message?
– ivan_pozdeev
Jun 22 '16 at 8:47
~"Internet Explorer cannot access to this web page" from debug console i see "dnserror"
– maxxvw
Jun 22 '16 at 8:48
Possible reason is likely IE settings (invalid/untrusted certificate, unsupported TLS version, custom network settings).
– ivan_pozdeev
Jun 22 '16 at 8:49
"dnserror.htm" is a generic error page. IIRC somewhere at the bottom, it gives a more technical formulation.
– ivan_pozdeev
Jun 22 '16 at 8:51
add a comment |
What's the specific error message?
– ivan_pozdeev
Jun 22 '16 at 8:47
~"Internet Explorer cannot access to this web page" from debug console i see "dnserror"
– maxxvw
Jun 22 '16 at 8:48
Possible reason is likely IE settings (invalid/untrusted certificate, unsupported TLS version, custom network settings).
– ivan_pozdeev
Jun 22 '16 at 8:49
"dnserror.htm" is a generic error page. IIRC somewhere at the bottom, it gives a more technical formulation.
– ivan_pozdeev
Jun 22 '16 at 8:51
What's the specific error message?
– ivan_pozdeev
Jun 22 '16 at 8:47
What's the specific error message?
– ivan_pozdeev
Jun 22 '16 at 8:47
~"Internet Explorer cannot access to this web page" from debug console i see "dnserror"
– maxxvw
Jun 22 '16 at 8:48
~"Internet Explorer cannot access to this web page" from debug console i see "dnserror"
– maxxvw
Jun 22 '16 at 8:48
Possible reason is likely IE settings (invalid/untrusted certificate, unsupported TLS version, custom network settings).
– ivan_pozdeev
Jun 22 '16 at 8:49
Possible reason is likely IE settings (invalid/untrusted certificate, unsupported TLS version, custom network settings).
– ivan_pozdeev
Jun 22 '16 at 8:49
"dnserror.htm" is a generic error page. IIRC somewhere at the bottom, it gives a more technical formulation.
– ivan_pozdeev
Jun 22 '16 at 8:51
"dnserror.htm" is a generic error page. IIRC somewhere at the bottom, it gives a more technical formulation.
– ivan_pozdeev
Jun 22 '16 at 8:51
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The most likely reason is IE's security or network settings:
- Invalid/untrusted certificate
- (in this case, however, a custom error message is printed AFAIK)
- Unsupported TLS version (no intersection in supported versions between browser and server)
- explicit custom network settings present (proxy or dial-up connection)
I consider the 2nd one the most probable. Support for older TLS versions is gradually phased out by browser vendors as vulnerabilities in them are discovered and fixed and vast majority of servers are updated. While at your private server, you are likely not updating and reconfiguring server software as you should. So, there may have been an update to IE that phased out support for even the newest version that your server is configured to use.
If you can use a sniffer, looking at the packets may give more info on the source of the error.
There's also "Internet Explorer cannot display the webpage" error" KB article by M$ that shows several troubleshooting steps, including checking the aforementioned network settings.
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
It's not the untrusted certificate alert... nor an unsupported version as i have activated all of them for testing purpose. Proxy settings are OK, On this same machine it doesn't work through both VPN and LAN. I'll try the sniffer option next time he'll come in the office.
– maxxvw
Jun 22 '16 at 9:50
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1092120%2fie-11-cannot-access-https-on-non-standard-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The most likely reason is IE's security or network settings:
- Invalid/untrusted certificate
- (in this case, however, a custom error message is printed AFAIK)
- Unsupported TLS version (no intersection in supported versions between browser and server)
- explicit custom network settings present (proxy or dial-up connection)
I consider the 2nd one the most probable. Support for older TLS versions is gradually phased out by browser vendors as vulnerabilities in them are discovered and fixed and vast majority of servers are updated. While at your private server, you are likely not updating and reconfiguring server software as you should. So, there may have been an update to IE that phased out support for even the newest version that your server is configured to use.
If you can use a sniffer, looking at the packets may give more info on the source of the error.
There's also "Internet Explorer cannot display the webpage" error" KB article by M$ that shows several troubleshooting steps, including checking the aforementioned network settings.
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
It's not the untrusted certificate alert... nor an unsupported version as i have activated all of them for testing purpose. Proxy settings are OK, On this same machine it doesn't work through both VPN and LAN. I'll try the sniffer option next time he'll come in the office.
– maxxvw
Jun 22 '16 at 9:50
add a comment |
up vote
0
down vote
The most likely reason is IE's security or network settings:
- Invalid/untrusted certificate
- (in this case, however, a custom error message is printed AFAIK)
- Unsupported TLS version (no intersection in supported versions between browser and server)
- explicit custom network settings present (proxy or dial-up connection)
I consider the 2nd one the most probable. Support for older TLS versions is gradually phased out by browser vendors as vulnerabilities in them are discovered and fixed and vast majority of servers are updated. While at your private server, you are likely not updating and reconfiguring server software as you should. So, there may have been an update to IE that phased out support for even the newest version that your server is configured to use.
If you can use a sniffer, looking at the packets may give more info on the source of the error.
There's also "Internet Explorer cannot display the webpage" error" KB article by M$ that shows several troubleshooting steps, including checking the aforementioned network settings.
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
It's not the untrusted certificate alert... nor an unsupported version as i have activated all of them for testing purpose. Proxy settings are OK, On this same machine it doesn't work through both VPN and LAN. I'll try the sniffer option next time he'll come in the office.
– maxxvw
Jun 22 '16 at 9:50
add a comment |
up vote
0
down vote
up vote
0
down vote
The most likely reason is IE's security or network settings:
- Invalid/untrusted certificate
- (in this case, however, a custom error message is printed AFAIK)
- Unsupported TLS version (no intersection in supported versions between browser and server)
- explicit custom network settings present (proxy or dial-up connection)
I consider the 2nd one the most probable. Support for older TLS versions is gradually phased out by browser vendors as vulnerabilities in them are discovered and fixed and vast majority of servers are updated. While at your private server, you are likely not updating and reconfiguring server software as you should. So, there may have been an update to IE that phased out support for even the newest version that your server is configured to use.
If you can use a sniffer, looking at the packets may give more info on the source of the error.
There's also "Internet Explorer cannot display the webpage" error" KB article by M$ that shows several troubleshooting steps, including checking the aforementioned network settings.
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
The most likely reason is IE's security or network settings:
- Invalid/untrusted certificate
- (in this case, however, a custom error message is printed AFAIK)
- Unsupported TLS version (no intersection in supported versions between browser and server)
- explicit custom network settings present (proxy or dial-up connection)
I consider the 2nd one the most probable. Support for older TLS versions is gradually phased out by browser vendors as vulnerabilities in them are discovered and fixed and vast majority of servers are updated. While at your private server, you are likely not updating and reconfiguring server software as you should. So, there may have been an update to IE that phased out support for even the newest version that your server is configured to use.
If you can use a sniffer, looking at the packets may give more info on the source of the error.
There's also "Internet Explorer cannot display the webpage" error" KB article by M$ that shows several troubleshooting steps, including checking the aforementioned network settings.
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
edited Jun 22 '16 at 9:42
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
answered Jun 22 '16 at 9:25
ivan_pozdeev
1,103722
1,103722
It's not the untrusted certificate alert... nor an unsupported version as i have activated all of them for testing purpose. Proxy settings are OK, On this same machine it doesn't work through both VPN and LAN. I'll try the sniffer option next time he'll come in the office.
– maxxvw
Jun 22 '16 at 9:50
add a comment |
It's not the untrusted certificate alert... nor an unsupported version as i have activated all of them for testing purpose. Proxy settings are OK, On this same machine it doesn't work through both VPN and LAN. I'll try the sniffer option next time he'll come in the office.
– maxxvw
Jun 22 '16 at 9:50
It's not the untrusted certificate alert... nor an unsupported version as i have activated all of them for testing purpose. Proxy settings are OK, On this same machine it doesn't work through both VPN and LAN. I'll try the sniffer option next time he'll come in the office.
– maxxvw
Jun 22 '16 at 9:50
It's not the untrusted certificate alert... nor an unsupported version as i have activated all of them for testing purpose. Proxy settings are OK, On this same machine it doesn't work through both VPN and LAN. I'll try the sniffer option next time he'll come in the office.
– maxxvw
Jun 22 '16 at 9:50
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1092120%2fie-11-cannot-access-https-on-non-standard-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's the specific error message?
– ivan_pozdeev
Jun 22 '16 at 8:47
~"Internet Explorer cannot access to this web page" from debug console i see "dnserror"
– maxxvw
Jun 22 '16 at 8:48
Possible reason is likely IE settings (invalid/untrusted certificate, unsupported TLS version, custom network settings).
– ivan_pozdeev
Jun 22 '16 at 8:49
"dnserror.htm" is a generic error page. IIRC somewhere at the bottom, it gives a more technical formulation.
– ivan_pozdeev
Jun 22 '16 at 8:51