Re: unable to log-in to secure sites

From: Steven L Umbach (n9rou_at_comcast.net)
Date: 08/30/03

  • Next message: Ron: "Mandatory User Profiles" 
    Date: Sat, 30 Aug 2003 16:11:35 GMT

    Hi Don. If you are using a firewall, make sure it allows outbound access to https
    port 443. Another thing to try is to add these sites to your "trusted" Web Content
    Zone using tools/internet options/security/trusted sites/sites. It may also help to
    reset tools/internet options/advanced to default. --- Steve

    "Don" <dshmd50@yahoo.com> wrote in message
    news:000b01c36f08$ce645810$a301280a@phx.gbl...
    > I have successful internet access through Warner Cable
    > Roadrunner. At sites such as Chase.com, Etrade.com,
    > C.Schwab.com, I enter the US and PW into webpage of above
    > sites and cannot get through - " cannot display the page "
    > appears. I have had an error at the microsoft site for
    > support ' 0x800A138F ' but have been unable to correct the
    > problem with their remedies.
    >
    > Help at Warner Cable and Chase Bank did not resolve this
    > issue.
    >
    > I have Windows Explorer 6.0 with 128 bit encryption
    >
    > Please help and thanks,
    >
    > Don

  • Next message: Ron: "Mandatory User Profiles"

    Relevant Pages

    • Re: SOHO firewall dropping incoming 443 connections - incorrect state
      ... The only incoming connection that I allow is an HTTPS port ... Occasionally the firewall seem to just start denying HTTPS ... I started a case with WatchGuard too, ...
      (comp.security.firewalls)
    • Re: Cant access web on local network server
      ... For correct DNS resolution you have also open port 69. ... Basically with a firewall to the external world you should be fine. ... Basically the port 80 is for http, sometimes 8080, https uses port ... Standard server and now my pcs can not access the web ...
      (microsoft.public.windows.server.general)
    • Re: Need https,portscan help
      ... the port is open or you wouldn't be getting there ... the firewall sitting in front of the webserver doesn't know ... probably not filtering/routing the https request through the firewall ... Colonel Flagg ...
      (alt.computer.security)
    • Re: Wrapping TCP communications in HTTP
      ... That sounds like we might be able to get away with going through port 80 by ... simply wrapping all of our messages in HTTP GETs or POSTs, ... but I still don't think that going through HTTPS is going to ... >> firewall and be able to connect to our components. ...
      (microsoft.public.win32.programmer.networks)
    • Re: Wrapping TCP communications in HTTP
      ... Use port 443 (HTTPS) instead. ... Microsoft MVP, MCSD ... > firewall and be able to connect to our components. ...
      (microsoft.public.win32.programmer.networks)