# lines or following the machine name denoted by a '#' symbol. # Additionally, comments (such as these) may be inserted on individual # The IP address and the host name should be separated by at least one # be placed in the first column followed by the corresponding host name.
# entry should be kept on an individual line. # This file contains the mappings of IP addresses to host names. # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # Copyright (c) 1993-2009 Microsoft Corp. I have checked the host's C:\Windows\System32\Drivers\Ect\hosts file and it looks like this: There is a clue here someplace, I can get to my local router and I can get to also I can get to but when I click on Download Center I get "The page cannot be displayed". So you download the FireFox 52.9 to your Windows 10 host and copy it over to the XP VM (maybe through drag-and-drop or Shared Folders, assuming you got VMware Tools installed/running in the XP VM). I would not point you to download from third party sites (but if you want, you do that on your own risk).Īlternatively, you can get Firefox 52.9 (it looks like it is the last version that supports XP and supports TLS 1.2). It looks like Microsoft does not even offer a full download for IE8 for XP anymore.
If it is not getting through for the http only MIT and Apache sites, possibly it is something else that is broken with IE6.0 after all, IE6.0 is almost 18 years old, almost an adult in most societies/cultures/legal definitions if IE6.0 were a person. IE6.0 only supports TLS 1.0 and it is disabled by default. That is why I asked if the MIT and Apache website went through with IE6.0 or not. If you are able to ping websites by name and unable to get to those websites through IE6.0 (such as bing or ), chances are it is because of the https TLS 1.2 requirement. Don't think it has anything to do with the hosts file.
0 kommentar(er)
