Directory is shared but konqueror still unable to find any workgroups

Looking in /var/log/samba/log.smbd it says:

 [2007/06/23 12:20:52, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/06/23 12:20:52, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/06/23 12:23:51, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/06/23 12:23:51, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!

Can this have anything to do with the problem?

Could you please provide more information. In particular, the file /etc/samba/smb.conf would help.

The error message varies a bit. I.e. now I am able to see my workgroup and click on my computer name but when I click on the shared folder, an error-popup window appears with the message that the folder doesn't exist.
The smb.conf file is attached.

Are there any errors or other information in /var/log/samba? There should be a file log.<ip addr> or log.<hostname> of the client that tries to access the folder.

Thanks

When I try to access the shared folder I get no log.<whatever> file in /var/log/samba.
However I get the following output in log.smbd:
----------------------------------------------------------------------------------------------
[2007/07/05 10:14:39, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/05 10:14:39, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
----------------------------------------------------------------------------------------------

and the following output from log.nmbd:

----------------------------------------------------------------------------------------------
[2007/07/05 10:14:38, 0] nmbd/nmbd.c:main(699)
  Netbios nameserver version 3.0.24 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/07/05 10:14:38, 0] nmbd/nmbd_subnetdb.c:create_subnets(190)
  create_subnets: No local interfaces !
[2007/07/05 10:14:38, 0] nmbd/nmbd_subnetdb.c:create_subnets(191)
  create_subnets: Waiting for an interface to appear ...
[2007/07/05 10:20:50, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
  *****

  Samba name server TMP-LAPTOP is now a local master browser for workgroup MSHOME on subnet 10.0.0.101

  *****
[2007/07/05 10:20:50, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
  *****

  Samba name server TMP-LAPTOP is now a local master browser for workgroup MSHOME on subnet 169.254.9.139

  *****
[2007/07/05 11:11:17, 0] libsmb/nmblib.c:send_udp(791)
  Packet send failed to 10.0.0.255(138) ERRNO=Invalid argument
[2007/07/05 11:11:17, 0] libsmb/nmblib.c:send_udp(791)
  Packet send failed to 10.0.0.255(138) ERRNO=Invalid argument
[2007/07/05 11:11:17, 0] libsmb/nmblib.c:send_udp(791)
  Packet send failed to 169.254.255.255(138) ERRNO=Invalid argument
[2007/07/05 11:11:17, 0] libsmb/nmblib.c:send_udp(791)
  Packet send failed to 169.254.255.255(138) ERRNO=Invalid argument
[2007/07/05 11:14:31, 0] libsmb/nmblib.c:send_udp(791)
  Packet send failed to 10.0.0.255(138) ERRNO=Invalid argument
[2007/07/05 11:16:52, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
  *****

  Samba name server TMP-LAPTOP is now a local master browser for workgroup MSHOME on subnet 10.0.0.101

  *****
----------------------------------------------------------------------------------------------

i just create an empty file /etc/printcap and then in the logfiles

log.smbd:
[2007/07/20 00:43:51, 0] smbd/server.c:main(847)
  smbd version 3.0.24 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006

there is no
"Unable to open printcap file /etc/printcap for read!"
line anymore!

but the folders are still not accessible :-(

"Unable to find any workgroups in your local network. This might be caused by an enabled firewall"

or

"...folder doesn't exist"

are there any ideas to overcome this bug?

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

Eh what?! The bug has not been fixed yet. So why is it now expired?! Lack of activity doesn't automatically fix the bug...

Could try to remove the "msdfs proxy = no" option from your smb.conf file ?

> remove the "msdfs proxy = no" option from your smb.conf

Already done. Doesn't help.

Did you reload samba after you've updated smb.conf ?

Can you list the shares with smbclient ?

You can use the following command from a terminal window :

  smbclient -L //TMP-LAPTOP/

I'm having the same problem. I've reloaded samba and recieve this error:

wintermute@wintermute:~$ smbclient -L //CHROME/
Connection to CHROME failed (Error NT_STATUS_BAD_NETWORK_NAME)

I also have no firewall to my knowledge.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!