Looking at the output above, it is nmblookup, which fails for the Windows share. I have tried to run it in the terminal and it properly returns Linux share IP address:
~$ nmblookup -T NECLAPTOP querying NECLAPTOP on 192.168.11.255 neclaptop.local, 192.168.11.15 NECLAPTOP<00>
but nothing for the Windows share:
~$ nmblookup -T AC-PC querying AC-PC on 192.168.11.255 ~$
If I run it without '-T', then it sort of works:
:~$ nmblookup NECLAPTOP querying NECLAPTOP on 192.168.11.255 192.168.11.15 NECLAPTOP<00>
~$ nmblookup AC-PC querying AC-PC on 192.168.11.255 192.168.11.2 AC-PC<00>
but obviously it may be not what is required for the pyNeighborhood to work properly...
Looking at the output above, it is nmblookup, which fails for the Windows share. I have tried to run it in the terminal and it properly returns Linux share IP address:
~$ nmblookup -T NECLAPTOP
querying NECLAPTOP on 192.168.11.255
neclaptop.local, 192.168.11.15 NECLAPTOP<00>
but nothing for the Windows share:
~$ nmblookup -T AC-PC
querying AC-PC on 192.168.11.255
~$
If I run it without '-T', then it sort of works:
:~$ nmblookup NECLAPTOP
querying NECLAPTOP on 192.168.11.255
192.168.11.15 NECLAPTOP<00>
~$ nmblookup AC-PC
querying AC-PC on 192.168.11.255
192.168.11.2 AC-PC<00>
but obviously it may be not what is required for the pyNeighborhood to work properly...