I have had situations in the past where SQL Serve reported a network problem but the Network people said nothing had gone wrong.

Eventually we wrote a simple script that did a PING every second and saved the result. This showed intermittent network problems, and the Network people had to accept that something had gone wrong. Eventually they found and fixed the problem, but as with anything that is intermittent it took a while to sort out.

If you can prove that the problem happens outside of SQL Server, then you have a better chance of the subject matter experts accepting a problem exists and getting it fixed.