C:\Users\Peter>net view \\169.254.184.206 System error 53 has occurred. The network path was not found.Again, I can ping the machine:
C:\Users\Peter>ping 169.254.184.206 Pinging 169.254.184.206 with 32 bytes of data: Reply from 169.254.184.206: bytes=32 time<1ms TTL=64 Reply from 169.254.184.206: bytes=32 time<1ms TTL=64 Reply from 169.254.184.206: bytes=32 time<1ms TTL=64 Reply from 169.254.184.206: bytes=32 time<1ms TTL=64 Ping statistics for 169.254.184.206: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0msSearching for "System error 53 has occurred" leads to this page which lists the following:
1) if it is domain environment, check your WINS;
2) if it is peer-to-peer workgroup, enable NetBIOS over TCP/IP;
3) make sure the machine is running;
4) make sure file and Printer Share enabled on remote computer;
5) make sure client for ms networks is enabled on local computer;
6) make sure you type the correct name.
7) Make sure no firewall running or any security setting.
1 doesn't apply, 2 didn't work, 5 is enabled, toggling firewall made no difference.
I'm currently thinking it's got to be something in Local Area Connection Properties and/or TCP/IPv4 properties - something I inadvertently changed and whatever configuration I try I can't find the magic values that it had before. :(
Network discovery is on.
Windows IP Configuration Host Name . . . . . . . . . . . . : Storm Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Mixed IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Wireless LAN adapter Wireless Network Connection: [snip] Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller Physical Address. . . . . . . . . : 00-90-F5-9B-5A-57 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Autoconfiguration IPv4 Address. . : 169.254.184.205(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled [snip]
Accessing NFS shares on Windows seems like a minefield, and there's an iSCSI option but that seems to have so much configuration... :&
So if I can't figure out WTF is stopping CIFS connecting then that leaves me with FTP. :'(
Regrettably I don't know of any protocols that possess the appropriate temporal aspect to let me record all the settings and changes made before things got screwed up.
The NAS is connected via Ethernet to the same switch as the Windows machine. (The NAS doesn't connect to wifi.)
I have no other active Windows boxes, and I'm not faffing around finding and swapping the harddrive I took out of my netbook since I'm approximately 5000% certain the NAS is correctly configured and the issue is with this Windows instance.