Certain HTTPS sites will not load - no errors - company wide

Environment:
Servers: Windows 2008 R2 Enterprise, Hyper-V, one virtual machine is office domain controller, another slice is Exchange.

Back Story:
On Monday, on of our techs performed a driver update on the Hyper-V's NICs.  Starting then, mail would not flow inbound.  About the same time (not entirely sure), IE stopped working properly.  Tuesday evening, we found that, if we modified the MTU on the network to 1464, we could get mail flowing.  The change was made on the firewall, not the server.

Wed/Thu: IE was working except for some HTTPS sites (ex: https://orders.dominos.com).  Others worked fine (https://secure.experts-exchange.com).  Lots of stuff was done to fix this - including replacing the firewall - EXCEPT removing the updated NIC driver.

Friday:  Still happening on all systems on the network (not just the servers).

Does anyone have a clue?  Could it be the NIC driver on the Hyper-V?  How would that cause other workstations to fail?  I am going to look into removing the driver update but I am not yet convinced it is the problem (not this one anyway).

The NIC is an HP NC382i and the driver is 7.8.21.0.

Help?
crapshooterAsked:
Who is Participating?
 
Craig BeckConnect With a Mentor Commented:
Can you try setting the MTU back to 1500 on the firewall, then see what you get when you use the following command on the mail server...

ping www.google.com -f -l 1472
0
 
crapshooterAuthor Commented:
FYI: I just rolled back to the previous driver.  No change in behavior.
0
 
crapshooterAuthor Commented:
OK, it seems to have worked.  Still waiting for confirmation from the client.  Why did you choose that specific packet size?
0
 
Craig BeckCommented:
1472 is the maximum packet size which will pass through a standard Ethernet port (before overheads are applied)

If you can pass a packet with a size of 1472 bytes at the ping command it will tell you that MTU is fine across the network.

Now that you've set the MTU back to 1500 are you still seeing the problem?
0
 
crapshooterAuthor Commented:
Nope.  At 1500, all is well.  I wonder if the systems were trying to send SSL packets that were larger than what the firewall would handle and the firewall dropped them.  Still, it only happened for some SSL sites.  And it was consistent across all systems on the network.  So it is still pretty weird.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.