Why does MS Office 2013, when working with a file server, access it via the Http protocol?

Question

Samba

The crux of the matter is as follows. There is a file server, on linux, a fleet of machines working with it, mostly Windows 7 with MS Office 2013. The file server is productive enough, there are no problems when working with pictures or PDF files.
But when working with MS Office, mainly Word and Exele, there are problems, files open and save for a long time, and this applies to completely new files, without data.
When you open the opening at the bottom, the inscription "Referring" Network path to the file "" , hangs for a long time.
When you try to save from the "Save As" dialog, after pressing the "Browse" button 6 times, a new window "Referring" Network path to the file " " opens with a progress bar.
showed that when opening the window " Referring" Network path to the file " office for some reason tries to connect to the file server via the http protocol (port 80), while this port is not open on the server.
The behavior is floating, it may or may not occur. Moreover, if the behavior is without network access on port 80, everything works very quickly.
Hence the question: Why ?, and most importantly, how to prohibit such behavior?

Answer 1

Thanks everyone, I figured out what's going on.
The office needs the \\ServerName\ PIPE\srvsvc
resource. If this resource is not available on the file server, due to some of its internal logic, with some probability, it tries to connect to the server via Http (port 80) and so on 6 times.
On Windows-base On servers, as I understand it, this cannot be disabled, while on linux machines using Samba, this resource is configured.
Directive smb.conf
PS Unforgettable about SambaCry