[partly solved] - unable to browse windows shares

[davexnet]

So far I've had no luck in establishing connectivity with shared folders between pclos and win2k.
In win2k, I can see the pclos name, when I select it I see the share names, but I'm unable to open them,
presumably an authentication issue of some ttype.

In pclos, at one time I could see the win2k pc name, but even that has disapeared.

In Dolphin, I click on Network (on the left) > samba shares > workgroup and it asks for a password?
What password?  Something in Win2k? Something in pclos?

I setup a shortcut in Dolphin to directly point to a share in win2k, but when I click on it, Dolphin tells me at the bottom
that it timed out.  It looks like this:  smb://192.168.100.1/C2K

I setup shares in pclos control center/share drive and directories with windows (smb).
I set it to public=yes, writable=yes, browseable=yes.  The folder I pointed to was one of the folders in \home\userid

Anything else I have to do? My next step is to boot the liveCD and try that.  For some reason, I'm not getting very far with my installed system.

EDIT: I booted the LiveCD and I can access my win2k shares, folders and files from PCLOS/Dolphin.  It worked right off - I didn't do anything to set it up.
It has never worked in the installed system.

[davexnet]

I was able to get the win2k box to appear now, however, the list of shares never do.  Here's as far
as I get, the Windows 2000 box is called amdwin2k.

As I mentioned, I can browse the shares if I boot from the LiveCD, the exact same CD I installed pclos from about
3 months ago.  What could the difference possibly be?  Something to do with permissions?
Some difference in the running processes?  I'm at a loss at this point.


EDIT : I've made some progress, I can now see the shares.  The clue was in the following thread and it has to do with
Linux being unable to resolve the Netbios name to IP address.  For now, I just added it to the HOSTS file using PCC -
eg. AMDWIN2k 192.168.1.100.  To me, it doesn't make a whole lot of sense,
see the SMB4K graphic I posted earlier,  it clearly already knows the IP address.

There may be a better way of doing it and I'll research it further.
http://forums.fedoraforum.org/showthread.php?s=c26ee4e256ace33d5c3cd0d98c153edd&p=1351712#post1351712



Uploaded with ImageShack.us