'Open with explorer' via http makes Explorer crash

Question

We currently have the effect that when clicking Open with explorer in a document library we can't add / edit / change items. The folder opens but as soon as we try to add something the explorer.exe freezes. Same goes for mapping a library to a drive letter.

By default we access our intranet via http. About a year ago we added the option to access it via https. And when accessing our Intranet via https everything works fine.

Anyone else has this feature/bug? Is there a way to fix it (a patch that might have been responsible)?

We use SharePoint 2013 on Windows Server 2012 R2. Client OS is Windows 10.

Edit1: Here are our AAM / IIS settings:

Edit2: We just got hold of a laptop without the latest patches and the behavior is the same. So our Patchday wasn't the issue here.

Edit3: We tried rewriting the URLs through our KEMP load balancer but the result is a 'broken' intranet due to the hard links.

Edit4: taking a look with fiddler revealed that as soon as I try to create a new folder this happens (the blurred URL is always 'intranet.company.com):

The only 302 message I can think of is the error page we set in IIS. But this has been made ~2 months before we encountered this issue.

Edit5: Trying to upload a file (credits.txt) takes some time and then presents me with these messages including a 504:

Answer 1

The Fiddler screenshot (edit3) indicates that the request #76 returns with a 302 i.e. it is redirected to the root and then results in a 401 (not authorised)

Can you try to grant the user read access to the root site on your farm? and then re-test?

Can you also try to disable the custom error page? (and restart IIS) would be good if we can exclude this as a cause.

Paul

Answer 2

I would fire up Fiddler and intercept the network traffic between the client and SharePoint. Can you establish a direct connection to one of the front-end servers by changing your local hosts file? This way you bypass the load balancer. Paul