Cannot Open Site in IE 11.

awed1
awed1 used Ask the Experts™
on
On one of our computers, we cannot open the fedex.com site in IE11.
This is a Win 7 Pro system.
She usually can open the site in Chrome.
She used to be able to open the fedex site in IE, but now it gets stuck seemingly trying to redirect to the site, to the proper address.
When she tries to connect, the address bar blinks a lot and shows signs of trying to redirect, maybe to Akamai, but it never fully resolves.
I have tried adding *.fedex.com to the Allowed Sites List in the IE Security settings.
I have cleared the DNS cache.
I have tried clearing her SSL State under the Content Tab in her IE Settings.
Other computers near her can connect to the site using IE 11, but she no longer can.
We have rebooted her computer.
We have uninstalled the security software, then rebooted.
We have cleared her Browsing History.
When I try to ping the site, it fails, but then it fails on the other computers as well, even though they can connect to the site using IE 11.
When I tracert, the result is always failure at the same distant point in the process.
I don't know if they allow Ping, so that might be the last step on the way, and it might for some reason block the protocol.

Tracing route to fedex.com [204.135.8.155]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     1 ms     1 ms     1 ms  173-11-90-46-SFBA.hfc.comcastbusiness.net [173.11.90.46]
  3     *        *        *     Request timed out.
  4    13 ms    11 ms     9 ms  be-92-ur03.ukiah.ca.sfba.comcast.net [68.85.191.181]
  5    18 ms    13 ms    14 ms  te-0-0-0-21-sur04.rohnertpr.ca.sfba.comcast.net [68.87.226.225]
  6    14 ms    13 ms    17 ms  hu-0-18-0-0-ar01.santaclara.ca.sfba.comcast.net [68.85.154.57]
  7    20 ms    16 ms    14 ms  be-33651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.90.93]
  8    19 ms    21 ms    22 ms  be-11025-cr01.9greatoaks.ca.ibone.comcast.net [68.86.87.158]
  9    18 ms    19 ms    17 ms  hu-0-12-0-1-pe03.11greatoaks.ca.ibone.comcast.net [68.86.83.130]
 10    17 ms    18 ms    20 ms  144.232.6.77
 11    19 ms    23 ms    20 ms  144.232.22.216
 12    22 ms    23 ms    20 ms  144.232.12.217
 13    23 ms    28 ms    23 ms  144.232.22.179
 14    24 ms    23 ms    23 ms  144.232.15.238
 15    63 ms    65 ms    69 ms  144.232.22.2
 16    64 ms    65 ms    65 ms  sl-gw17-che-0-15-0-0.sprintlink.net [144.232.2.10]
 17    65 ms    65 ms    66 ms  sl-fedex59-563280-0.sprintlink.net [144.223.8.102]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Any ideas about what may be wrong, or about how to proceed?
Thanks in advance,
B.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
mbkitmgrOwener

Commented:
Try just the IP in the browser bar 204.135.8.155 and see if the site loads.  if it does then name resolution is playing tricks.  If it still doesnt try right clicking choosing view source to see what code is presented
David FavorFractional CTO
Distinguished Expert 2018

Commented:
If you have any sort of Ad Blocker running, be sure to whitelist all Fedex.com pages.

Looking at Fedex.com redirect chain, there's no reference to Akamai...

imac> curl -I -L fedex.com
HTTP/1.1 301 Moved Permanently
Date: Wed, 12 Jul 2017 14:33:57 GMT
Server: Apache
Set-Cookie: siteDC=edc; path=/; domain=.fedex.com; expires=Thu, 13-Jul-2017 14:33:57 GMT
Location: http://www.fedex.com/
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK
Server: Apache
Last-Modified: Fri, 01 May 2015 17:02:31 GMT
Access-Control-Allow-Credentials: true
Content-Type: text/html
Expires: Wed, 12 Jul 2017 14:33:57 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Wed, 12 Jul 2017 14:33:57 GMT
Connection: keep-alive
Set-Cookie: siteDC=edc; path=/; domain=.fedex.com; expires=Thu, 13-Jul-2017 14:33:57 GMT
Set-Cookie: fdx_cbid=30707895801499870037214590064721; path=/; expires=Tue, 07-Jul-37 14:33:57 GMT; domain=.fedex.com

Open in new window


If a true redirect is occurring, rather than just referencing some asset/file on an Akamai CDN, then I'd guess this machine might be hacked.

Ah Windoze. Good times. You never know if you've been hacked or not. Also, there are few good debug tools available.

Your traceroute is likely good, as Fedex.com appear to block ICMP packets, so you can't really use any ICMP based tools with their site, which includes traceroute + mtr + ping.

Better to use curl https://curl.haxx.se/download.html#Win32 to verify you can connect + return content.

You can attempt to disinfect your Windoze install or maybe have to do a fresh install.

For the few Windoze Apps I require, I run Mac/OSX + VirtualBox + Windoze, so if Windoze gets hacked while it's running, the next reboot loads from the pristine VirtualBox Windoze installation image, so Windoze works well... till it doesn't + a simple reboot restores to a clean copy.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial