Samba problem: findsmb and nmblookup fail
I wrote a program which uses findsmb to get a list of Samba aware resources. It worked fine. It was able to see both my own cluster of virtuals and other company computers too. My company moved to a different location. The network was flakey for awhile, but has seemed okay for months now. I am not sure that moving is the cause of the problem I am about to describe, but it is the only obvious change. Now findsmb only discovers the machine I am running in. I am doing this in a number of VMWare virtuals, and have tried this in several. In every case, findsmb only finds localhost. I should repeat that this was working fine in the past. I did enough research to discover that findsmb relies on nmblookup. So I tried "nmblookup -A <ip address>" for several of the IPs around and it always comes back with "no reply." I have no idea what's wrong. Does anyone have any ideas?
Last edited by Brandon9000; 09-19-2012 at 11:47 AM.