I ran into an issue similar to this myself a few months ago.
For me, enabling TCP/IP for both IPV4 and IPV6 in SQL Server Configuration manager fixed the issue. I have also seen this occur even when IPV6 is not installed. Oddly enough, I've even experienced this behavior even when I only specify IPV4 addresses?!
