Binary package hint: samba
There is enough response on the Dapper forum that, while not everyone is experiencing this problem, I am not alone.
I used to be able to access Windows XP shares and the Windows XP box could access the Dapper shares, but after Dapper daily updates last week Samba has become totally broke.
When I try to access the Dapper shares via “Start->My Network Places”, the Dapper shares do not display.
When I try to access the Dapper shares via “Start->My Network Places->View Workgroup Computers”, the Dapper machine icon displays, but when I click on it, it fails with a “The network path was not found” error dialog box.
When I try to access the Windows shares from Dapper via Places-Network Servers, the Windows Network icon is displayed but when I click on the icon, the dialog box window clears to a blank and the shares do not display.
/etc/smb.conf is generic original except that I have added a share at the bottom (via the GUI). The workgroup is the same name as the XP box, “MSHOME”; security-user; netbios = alvin.
Remember – all of this worked correctly prior to last week’s Dapper daily updates.
Because some people have indicated that they are successfully using Samba with Dapper I have attempted another try at fixing it.
1. Using Synaptic I totally removed, including configuration files, ALL packages dealing with Samba. The packages removed were: samba, samba-common, libsmbclient, smbclient, smbfs, libgnomevfs2-extra
2. I rebooted Dapper and verified that /etc/rc?.d/*sambs, /etc/initd/samba, /etc/samba/* were all gone.
3. Using Synaptic I added only samba and samba-common and repeated attempts to access Windows shares and visa-versa. The results of accessing Dapper shares from Windows had the same “The network path was not found” error. Accessing Windows shares from Dapper resulted in a "smb:/// is not a valid location." Error. This error is why I originally added libgnomevfs2-extra.
4. I tested printing to the Windows XP shared printer and it, once again, wasn’t working. So, I next used Synaptic to add back libsmbclient, smbclient, smbfs and libgnomevfs2-extra. Then I rebooted Dapper.
5. Now the Windows XP shared printer works but access shares to/from is back to the original problem – Windows reports “The network path was not found” and Dapper shows a blank dialog box when I click the “Windows Network” icon at Places-Network Servers.
6. Windows shares can be viewed via Firefox with "smb://192.168.0.102/", yet only a blank screen results from looking for the shares via nautilus’s “Places->Network Servers”.
7. I went to "Places-Network Servers", then clicked on the Windows Network icon, which, as before, showed a blank display. Then I entered a control-L on the blank display and the address line showed "smb:///". I then inserted the IP address of the window box into the proper spot in the address line, i.e., smb://192.168.0.102/, and it correctly displayed the Windows XP share icons. This is a manual fix as the screen remains blank when I repeat the process. Nautilus, or nmbd isn't resolving server names?
8. I have the problem all of the time (now) but others on the forum indicate that it is intermittent for them “jalonsom: This is really a weird problem. I hadn't realized earlier because I have permanently mounted all the shares I need so they work OK:
I have seen that sometimes I can do Network>Windows network>workgroup so I can see the servers present, but trying to open one leads to the error described.
But other times I can do Network>Windows network>workgroup and I only see the local computer (browsing local computer always works)
And at other times I can just do Network>Windows network and a blank screen appears. This is what celem described.”.
Similar problem here.
Definately related to name resolution in samba as I can see samba servers and shares in nautilus when usind IP addresses.
More discussion in:
http://