problems with samba and konqeror

[cmillar6]

I have had a Vista/PCLOS 2009/XP home network that has worked flawlessly for quite some time now. Lately when trying to browse my network through remote places-->samba my workgroup shows up yet when I click on it none of the PC's show up anymore, I just get a timeout error. I have found a work around by typing smb://pcname into Konqeror and then I am able to connect to windows boxes and all shares show up.  I would still like to know why all PC's on my network no longer show up when I click on my workgroup in Konqeror?  When trying to connect to any of the PC's from vista or xp everything works fine.

[travisN000]

If I recall correctly this has to do with your linux box defaulting to a different workgroup name than your windows clients..  see if the following helps (the PCC setup is the same in both Gnome & KDE):

http://linuxgator.org/forums/viewtopic.php?f=15&t=879

[cmillar6]

I've checked all of that. Nothing has changed.

[docnascar]

I continue to have this same exact problem. It will actaully go away if I reboot my linux pc. Then about 30min to an hour later the server timeout comes back.  Using smb://pcname works everytime.

Interesting to note as well, I share a windows xp machine with a printer to my linux box. When the timeout happens I loose my shared printer from windows until I reboot linux.

[ThirdOfSix]

cmillar6,

I had this problem for a while until I recognized the pattern of when things did not work.

It turned out that my original main computer running Windows XP had always been left on. When I started experimenting with distributions, I sometimes booted that machine in something other than the original Windows install.

Whenever that machine was not running Windows, my network did not work.

A lot of studying brought the concept of a master browser and where it resides into the picture.

The fix was to go into the configuration file in PCLOS and set it up to become the master browser when needed.

Sorry, I don't remember which file that is.

So, if you sometimes have another machine on when it is working, that may be what is going on.

 

[nixer]

Very interesting ThirdOfSix, I had similiar issues on my home network with windows and linux boxes.  This may explain why.

My work around was to replace all mentions of machine names with ip numbers, then bookmarked them in konq, smb4k, and printer configurations.  It has worked pretty good since then.

Hope this helps.