Comment 2 for bug 198351

I can reproduce this bug under two conditions.

1) If my network is not set up correctly, and it is impossible to connect to a MS networking server even with smbclient, then any attempt to use fusesmb (understandably) fails in exactly the way that Dr_Willis reports

2) If my network is set up correctly, and I CAN connect to MS networking servers as verified using smbclient, then my very first attempt to use fusesmb for a user always fails exactly as Dr_Willis has described, with the additional detail that ~/.smb/fusesmb.cache does not get created, but ~/.smb/fusesmb.cache.pid does get created. After approximately 5 minutes have passed, ~/.smb/fusesmb.cache.pid suddenly disappears and ~/.smb/fusesmb.cache suddenly appears. All subsequent attempts to use fusesmb work perfectly after that point, and the only way I can reproduce Dr_Willis's symptoms again is by manually deleting ~/.smb/fusesmb.cache