Windows 2008 R2, Trouble with Connecting to a Buffalo NAS Device

Published on
3,736 Points
Last Modified:
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them.

Troubleshooting Steps:
  • Command line: net view \\servername | NOPE
    • System error 53 has occurred, the network path was not found
  • Command line: net view \\192.168.1.x | NOPE (note: ping the actual IP address of the device)
  • Command line: net view /cache | Server is viewable but still get "System error 53"
  • Disabled Firewall | NOPE
    • Services Windows Firewall
  • Disabled Antivirus | NOPE
  • Tried to connect from another Windows 2008 R2 server, OK no issues.
  • Checked Network Settings, IP, DNS, WINS all the same (except the actual IP DUH!)
  • Ping both the NETBIOS name and IP address | OK
  • Clear and Reset: arp, nbtstat, ipconifg (from an elevated command prompt)
    • Elevated command prompt: arp -d
    • Elevated command prompt: nbtstat -R (must be capitalized)
    • Elevated command prompt: ipconfig /flushdns
    • Wait a few moments...
    • Elevated command prompt: nbtstat -RR (must be capitalized)
    • Elevated command prompt: ipconifg /registerdns
  • No errors in either Application log or the System log.
  • Ensured the SMB1 and SMB2 are installed working and enabled.
    • Powershell prompt: Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 1 -Force
    • Powershell prompt: Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB2 -Type DWORD -Value 1 -Force
    • Restart System must do for the above to take effect and before doing the below…
    • Elevated command prompt: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
    • Elevated command prompt: sc.exe config mrxsmb10 start= auto
    • Elevated command prompt: sc.exe config mrxsmb20 start= auto
    • Restart again (and if you have been doing this as long as I have you start to think are we back in the days of Windows 3.11)
  • Validated the Local Security policies (secpol.msc) | Security Settings > Local Policies | Security Options
    • Review all the policies "Network access:" with the machine that does work and make contact to the buffalo device.
    • Do not delete either update or add, and document what your changes are (before and after) so if this breaks something else you can take it back.
  • Review the Workstation services settings: HKLM\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters to those of the working server.
    • My change wound up being the "RequireSecuritySignature" value needed to be 0 (Disabled)


(value not set)

0x00000000 (0)

0x00000001 (1)


0x00000000 (0)


0x00000001 (1)

Reboot so the changes take effect, test and hope this works for you as well.

Featured Post

HTML5 and CSS3 Fundamentals

Build a website from the ground up by first learning the fundamentals of HTML5 and CSS3, the two popular programming languages used to present content online. HTML deals with fonts, colors, graphics, and hyperlinks, while CSS describes how HTML elements are to be displayed.

This is Part-2 of Learning to use the Power of Mailwasher Pro so if you haven't watched Part-1 yet, I urge you to do so before watching this video. Click this link to watch Part-1 (https://www.experts-exchange.com/videos/56638/Learn-to-use-the-POWER…
There are many cases found where ScanPST.exe fails to repair corrupt Outlook PST File. When user tries to repair PST using Inbox Repair tool and it throws below error: •      Inbox Repair tool does not recognize the file •      ScanPST.exe hangs in betwee…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month