So this has been plaguing my environment for awhile and is starting to happen more often. I have a web server (2008R2) that accesses a file server. Both are located on the same network at the datacenter with no firewall between them.
Sometimes my website starts telling users that it cannot find the network resource. So I log into the web server, and I can access the network resource at \\fs2.domain.local and \\172.31.xxx.xxx but cannot access \\fs2 which all 3 are the same resource. I can however ping all 3 and do an nslookup with good results. I believe that there is probably somewhere, in some code that points to just fs2 instead of the FQDN but my devs can't seem to find where.
So on the other side of this issue I would like to find out why \\fs2 is randomly not accessible, but most of the time it is. Below are some of the steps I have one or checked:
- There is an entry in my host file for fs2 and for fs2.iss.local pointing to the correct IP address.
- NetBIOS process is not crashing and is up and running during the outage.
- I can access \\fs2 from other machines during an outage, just not the web server.
What else can I look for to help resolve this issue?