SMB Browsing Error - (WBEL: Fedora RPM's to install XFce)

[Paul M. Bucalo]

On Fri, 2004-02-27 at 08:20, Paul M. Bucalo wrote:
> On Fri, 2004-02-27 at 07:53, Paul M. Bucalo wrote:
> > The Fedora RPM's for XFce-4.0.3.1 were installed on WBEL 3.0-fixed. I am
> > finding that I cannot browse or connect to my MDK 9.1 Samba server or
> > shares, respectively. The error that given in the 'xffm' monitor is as
> > follows:
> > 
> > Looking for master browsers...
> > XFSAMBA> nmblookup -M -- -
> > queryiNg __MSBROWSE__ on 192.168.1.255
> > name_query failed to find name __MSBROWSE__#01
> > 
> > Nautilus browses and connects with normalcy. 
> > 
> > Workstations and server are statically assigned and all '/etc/hosts'
> > files have the server's IP and host name included. Nothing has changed
> > to the network outside of this recent WBEL installation. BTW...I have a
> > Fedora workstation up and running and it browses and connects as
> > expected. 
> > 
> > Has anyone experienced this in WBEL? Could this be because I used
> > Fedora-favored RPM's to install XFce? Any ideas as to where to find my
> > solution?
> 
> Here's a follow-up to this...
> 
> I decided to see what was happening in the background: I ran 'xffm' from
> a terminal window. There were warnings about needing to set SMB_CODESET
> to ISO-8859-1, but nothing else regarding the browse or connection
> phase. Then, the unexpected happen: 'xffm' was able to browse the Samba
> server and connect! I exited out of 'xffm' and terminal window, and
> tried to browse/connect using 'xffm' run from the XFce panel. It worked!
> Go figure.
> 
> I'm glad that the problem has been resolved, but I still would like to
> know if anyone has any idea(s) as to why it happened in the first place.
> 
> Thanks,
> 
> Paul

A final update on my original post...

It was mentioned by someone that the problems I was experiencing
with connecting to my Samba shares came about because of the differences
in smbclient and smbd versions between the workstations and server,
respectively. The two Linux workstations are running WBEL and FC1, and
both are using Samba v3.0.2. The MDK 9.1 server is using v2.0.7.
LinNeighborhood will no longer works with a smbclient beyond 2.x.x.
'xffm' was having some problems negotiating between the two versions.
Nautilus wasn't having a problem, though I can't tell you why. 

With the upgrading of the server O/S to WBEL 3.0-fixed, the problem was
resolved for 'xffm'. LinNeighborhood still doesn't connect, but that is
now a permanent problem until someone takes over the project and
resolves what needs fixing. All seems to be well. I think this has been
a good indicator that 'xffm' in the v3.0.1-1 release will not always
work properly when asked to browse and connect to Samba  v2.x.x shares
from a Samba v3.0.2 client.

BTW, if anyone is looking for a GUI interface to mount and unmount
shares securely, take a look at Jags:

http://jags.sourceforge.org/

It's similar in nature to LinNeighborhood. Double-clicking (or right
clicking and choosing from a sub-menu) and logging in are the extent of
the tasks involved in mounting and unmounting shares. If the shares are
secured, the app will prompt for user and password. The app can be
closed once shares are mounted and they stay mounted until umounted, or
the user is logged out. So far, it's working like a
champ. 

HTHS in a similar situation of mixed Samba versions and XFce.

Paul