Deduplicating until we are sure it's the same bug.
It looks like a name resolution issue: querying "nasdrive" on the windows network returns 206.112.100.151 for some reason, then you get a timeout accessing that unknown IP. Running smbtree sends a local broadcast to which the nasdrive responds and then the computer caches that information, until next reboot or cache timeout.
Additionally:
- Please attach your /etc/samba/smb.conf file
- What does "ping nasdrive" return ?
- What does "grep hosts /etc/nsswitch.conf" return ?
- Does "smbclient //nasdrive/sharedfolder -R bcast -U username" work ?
- Please send the output of "smbclient -d4 //nasdrive/sharedfolder -U username"
Deduplicating until we are sure it's the same bug.
It looks like a name resolution issue: querying "nasdrive" on the windows network returns 206.112.100.151 for some reason, then you get a timeout accessing that unknown IP. Running smbtree sends a local broadcast to which the nasdrive responds and then the computer caches that information, until next reboot or cache timeout.
Could you attach the information requested at: /wiki.ubuntu. com/DebuggingSa mba#samba- client
https:/
Additionally: sharedfolder -R bcast -U username" work ? sharedfolder -U username"
- Please attach your /etc/samba/smb.conf file
- What does "ping nasdrive" return ?
- What does "grep hosts /etc/nsswitch.conf" return ?
- Does "smbclient //nasdrive/
- Please send the output of "smbclient -d4 //nasdrive/