We have a file server that has been in place for over 2 years now. It is running windows server 2008 R2. Two weeks ago, all our windows xp and windows 7 clients were able to access files and folders using dfs and file shares. Then mid morning the file server took a hickup where the windows XP clients could not connect to any file shares. It would say "THE SPECIFIC NETWORK NAME IS NOT AVAILABLE" when trying to browse to the file server unc path by ip or name (netbios/fqdn), but the windows 7 machines continued to work. So we rebooted the server and everything worked file until late afternoon the server took another hickup where the windows xp workstations cannot access any shares on the server by name or ip but the server is pingable by netbios and FQDN. All windows 7 machiens are still working.
I checked event logs on DCs, file server and workstation no errors reported. I also cleared the nbtstat cache on the file server, enabled netbios and still have to reboot the server. I am not sure what the issue is. Could it be something with SMB where Windows XP is using and older version as the new server would be using SMBv2? if a pc connects to a share, what is the process that it uses for that? Does it use the SMB protocol. Also windows firewall is enabled, however all profiles are set to off. When this issue happens if I try to connect to another shared folder on another server that is windows server 2008 R2 it is successful.
We rebooted the server tonight and it resolved the issue but I think it will come back and I am trying to get to the bottom of the issue.