cannot see NAS in MSHOME Workgroup since Update to 12.1

[such_und_find]

I recently upgraded to 12.1 very easily and smoothly will all settings/users etc still there. I also set the IP scheme to Manual, had been in the DHCP space before. The NAS sits on a secondary WiFi Access Point configured as a Switch, which is connected to the main Router on a home network.

I used to be able (v6.x) to see the NAS and the volumes via Browisng the Workgroup through the Map Network Drive function in Windows Explorer (my Workgroup is called MSHOME)
It would show itself as
\\SPD8020-7EAD14\XXXXX and allow connecting by clicking.

I just found out that this function does not work anymore (no idea why). I *can* connect through IP address
\\192.168.2.10\XXXXX

Putting NFS on or off didnt change anything (or do I need to reboot the PC and/or the NAS for that?).

I always thought Microsoft runs a flavor of SAMBA for that function, and that is all turned on. Am I overlooking something maybe?
......
Systeminformationen:
Systemnamen SPD8020-7EAD14
IP-Adresse: 192.168.2.10
Subnetzmaske 255.255.255.0
MAC-Adresse: 00:90:3E:7E:AD:14
Arbeitsgruppe: MSHOME
Firmware Version: phn fvdw-sl 12.1
Datum: September 2, 2012 01:46:16 PM
Betriebszeit: 7 Tage, 1 Stunden, 3 Minuten, 19 Sekunden


Freigabename Laufwerk Gesamtgröße Freier Speicher Öffentlich Samba NFS FTP
public Default 464.57 GB 376.21 GB Ja Ja Nein Nein
Guni_Netz Default 464.57 GB 376.21 GB Nein Ja Nein Nein
Fenja_Netz Default 464.57 GB 376.21 GB Nein Ja Nein Nein
Olaf_Netz Default 464.57 GB 376.21 GB Nein Ja Nein Nein
Backups Default 464.57 GB 376.21 GB Nein Ja Nein Nein
Fotos Default 464.57 GB 376.21 GB Nein Ja Nein Nein
mp3 Default 464.57 GB 376.21 GB Ja Ja Nein Nein

[fvdw]

No changes has been made on that point in 12-1 so it should still work. Im my network the NAS is visible with the name.
Most of the time this is a windows issue not refreshings its LAN hosts database and it can take some time before it pops up. It might have Has to do with which system in your LAN is "master browser". The master browser keeps a list of pc in the LAN and if thats is not refreshed then your NAS might not be visible as the other PC use that list to see which systems are on the LAN.

Despite this it ramins strange that using \\name-of-nas doesn't work as well thats independent of the master browser list.

Sometimes it helps to change the name of the NAS and click accept. After that change it back to the original name. If it then doesn't popup up something else must be wrong.

To see if the NAS name is detected you could open a command window in windows and type the command

Code: Select all

nbtstat -a 192.168.2.10

this should display netbios name and other info if the device on 192.168.2.10

[such_und_find]

The trick with renaming worked like a charm. Just changed the last letter, saved on the NAS, there it was in the Browse Menu in the Workgroup. Changed back again and I could use the stored settings from when it used to work.

I did however also force "enable NetBIOS" function before, as the command you suggested came back with a "this function is not enabled on this PC" kind of error.
Though the NAS remains visible also with NetBios set back to "Auto ( get settings from DHCP server), so it probably is not correlated. I´ll check and come back if I see any change.

So probably indeed the renaming thing did the job.
Maybe the system was confused after changing the IP with the same Name on it or something..

In any case - thanks once more and especially a BIG thank you for the really prompt reply. :thumbup :-D

[such_und_find]

the actual error message was
"Failed to access NetBT driver - NetBT may not be loaded."

[fvdw]

the actual error message was
"Failed to access NetBT driver - NetBT may not be loaded."

well I think this was the problem as when this driver is not loaded the PC can not read netbios names.
Anyhow the problem is solved :thumbup

[such_und_find]

Just checked on another PC in the network - visible, so great.

--> About the error message "Failed to access NetBT driver - NetBT may not be loaded."

this is apparently the case (even if it is loaded!), when you type this command with restricted user rights - needs admin rights to run off WinXP in my case.
Then it returns "proper" sensible parameters back - does this look reasonable?

C:\WINDOWS\system32>nbtstat -a 192.168.2.10

Ethernet XXXXX:
Node IpAddress: [192.168.2.143] Scope Id: []

NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
SPD8020-7EAD14 <00> UNIQUE Registered
SPD8020-7EAD14 <03> UNIQUE Registered
SPD8020-7EAD14 <20> UNIQUE Registered
MSHOME <1E> GROUP Registered
MSHOME <00> GROUP Registered

MAC Address = 00-00-00-00-00-00

[fvdw]

yep that is the correct output, it shows the netbios name workgroup of the device that has ip address 192.168.2.10