hello can confirm that this bug may be caused by settings in /etc/nsswitch.conf.
In my case, I have Hardy, installed with samba, firestarter (running at startup) and winbind.
adding the value "wins" in the line in /etc/nsswitch.conf:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 wins
causes the problem for me, removing "wins" from nsswithc.conf and logging out and logging on fixed the problem. i can again access samba shares and files.
adding "wins" was supposed to ping samba PCs via their PC Names instead of their IP numbers 192.168.x.x, etc. I added that line after installing winbind.
hello can confirm that this bug may be caused by settings in /etc/nsswitch.conf.
In my case, I have Hardy, installed with samba, firestarter (running at startup) and winbind.
adding the value "wins" in the line in /etc/nsswitch.conf:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 wins
causes the problem for me, removing "wins" from nsswithc.conf and logging out and logging on fixed the problem. i can again access samba shares and files.
adding "wins" was supposed to ping samba PCs via their PC Names instead of their IP numbers 192.168.x.x, etc. I added that line after installing winbind.