Call 1888 885 1810 to Windows cannot access Windows support number and get Instant Homepage technical support from our Certified Experts. We guarantee to provide best technical assistance and our technicians are available 24/7 365 days. For more info, Visit our Website https://www.windowsitsupports.com
Windows is positioned as an enterprise-friendly operating system, with lots of features to support workgroups and sharing of files and physical resources. Despite this focus, however, Redmond’s flagship operating system seems to go out of its way to generate cryptic and user-hostile error messages for common problems. These error messages always make solving issues more difficult than it needs to be, while adding a layer of confusion and frustration for intelligent but not computer-immersed users, people who could probably fix a problem if they knew something about its cause.
One of the more egregious offenders is Windows error code 0x80004005. This error generally pops up during as failed attempt to use a shared resource over the network such as a shared network hard drive. The usual syntax for this error is generally something along the lines of “Windows cannot access \\Computer1, Check the spelling… Error code 0x80004005 Unspecified error.” This super-helpful message popping up on someone’s screen tells them basically nothing,
The specific computer that was encountering the error most frequently was a Windows 7 laptop that had WiFi & a Wired Network Connection, both of which were ENABLED and connected to the router/internet during the time of the error. After some troubleshooting, I noticed that when I disabled the Wireless adapter, the Network Share Errors would go away. This led me to investigate what, if any, difference in settings there were between the Wireless adapter and the Wired connection. First off, the Local Area Connection (wired) was setup with a manual static IP address, while the Wireless Network Connection was set to Obtain an IP address automatically through DHCP. This should make no difference really, although it could if there was a problem with the wireless function of the router or the laptop’s wireless adapter, but I knew that was not the case.
It took some digging but the other difference between the two network adapters was an Advanced setting within the Windows 7 network adapters configuration screen (Control Panel\Network and Internet\Network Connections). This setting relates to NetBIOS over TCP/IP. NetBIOS is the service that allows Windows systems to access file shares via the computer name, instead of using the IP address. Coincidentally, a trick I have used in the past, to get Windows 7 computer shares to work more reliably, is to Map the Network Drives using each system’s IP address, as opposed to their NetBIOS or Computer name. For some reason, Windows XP seems to access all shares more reliably–both Windows 7 file shares & other Windows XP file shares…perhaps it has something to do with the way Windows XP
No comments:
Post a Comment