We have three Servers 1 x 2008 64Bit with Exchange 2007 (a), 1 x 2003 R2 Sp2 with SQL 2005 32 bit (b), 1 x 2003 R2 with Terminal Services (c). All three servers ar SR2500ALBRPR with 5 x 300Mb SAS drives 1 x RAID1 & 1 x RAID5 with 8Gb of RAM. There are also some 15 PC's with WIN XPP with Office 2007. This setup was working fine until Friday Morning, when it was discovered that Network shares on (b) were not accessable from WIN XPP or (c). No WIndows Updates were deployed on Thursday night.A review of the configuration of (b) has been undertaken, and it can be confirmed that The Shares are properly configured, with appropriate NTFS permissions. The shares are accessible on (b) from (b) and from (a). The shares are refreshed from login script. When accessing the shares from WINXPP the system responds with Network path not found System Error 53. A review of the internet suggested that (b) might not be registered with WINS properly/correctly. WINS was reviewed and (b) appeared to be registered correctly, to be sure (b) was re-registered. Thinking that possibly the DNS records may be misaligned, nslookup from a WIN XPP or (a) or (c) responds as expected. (b) can also be pinged both by IP and Hostname. The shares on (b) have been deleted, and reassigned, with NTFS permission also being removed and reapplied. Group Policy has been checked and undefined then redefined, and gpupdate /force being run. Group Policy included Microsoft Client digitally sign communications (always) & Microsoft Client digitally sign communications (if server agrees)and MicrosoftServer digitally sign communications (always) & MicrosoftServer digitally sign communications (ifclient agrees).In addition from WINXPP at the command prompt if ipconfig /flushdns and arp -d are run, a net view of (b) is successful but only once, if tried again it fails, if ipconfig /flushdns and arp -d are run again, from the startmenu the \\(b)\sysvol share will be available but only for about 10 seconds, then it drops out with System Error 53. Anti-Virus, and WIndows Firewall have been uninstalled. On the off chance AD was playing games, (b) was demoted and promoted as AD. From a WINXPP or (c) it makes not difference whether user has domain admin rights failure is still the same. Access to the shares from (a) on (b) are still OK. Event LOg reveals no errors from either System or Application.If anyone has some advice for something I might have overlooked / solution, I would be most grateful.

Hello, From your description, it seems that you encountered the error "Network path not found System Error 53" when you access share folder on a server. In order to troubleshoot it, let us refer the following steps to perform a Clean Boot and restart the to see if the issue still continues. Step 1: Perform a Clean Boot 1. Click "Start", go to "Run", and type "msconfig" in the open box to start the System Configuration Utility. 2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click Disable All (if it is not gray). 3. Click the "Startup" tab, click "Disable All" and click "OK". 4. Restart your computer. When the "System Configuration Utility" window appears, please check the box and click "OK". Possible Solution: 1. Check for the "TransportBindName" and "SMBDeviceEnabled" Value under the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\ParametersIf it does not exist, create it with the following attributes.Name: TransportBindName Type: REGSZValue: \Device Name: SMBDeviceEnabled Type: REG_DWORD Value: 12. If that does not resolve the problem, please look for the correct GUID Under the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces The correct GUID should have values under DhcpNameServerList, NameServerList, NetbiosOptions.3. Please make sure that this GUID is list under all the parameter of the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\LinkageIf not, please modify the data value for all the parameters listed under the above registry key. Hope this can be helpful.This posting is provided "AS IS" with no warranties, and confers no rights.