Re: SuSE 9.1 - prbl with Samba Client and locations

From: Larry I Smith (larryXiXsmith_at_verizon.net)
Date: 05/17/04 

Date: Mon, 17 May 2004 18:05:21 GMT

Anund Rannestad wrote:
> Larry I Smith wrote:
>
>
>>Well, it's been awhile since I installed Samba, but
>>here's my config:
>>
>>SuSE Pro v9.0, installed Samba packages (via yast):
>>kdebase3-samba - provides 'smb:/' protocol access
>>libsmbclient - base Samba lib
>>libsmbclient3 - Samba 3 lib
>>samba - Samba server to allow Win clients access to Linux
>>samba-client - Samba client to allow Linux access to Win
>> and Linux client tools (smbmount, etc).
>>yast2-samba-client - yast config module for samba-client
>>yast2-samba-server - yast config module for samba
>>
>>I also installed 'swat' to allow editing my Samba
>>config via any Web Broswer (see the Samba web site).
>>
>>By default, for the Windows pc's to connect to the
>>Linux pc, the Windows user must connect using their
>>Linux userid/password. This can be changed in the
>>Linux Samba config, but it is usually the install
>>default.
>
>
> This works fine. I access the Linux shares from the XP boxes without any
> problem, and can read/ write to these from the XP boxes.
>
>
>>For the Linux pc to connect to a Windows pc, the
>>Linux user must use their Windows userid/password
>>(or whatever userid/password is setup for the
>>Windows share).
>
>
> I know this, too. But the problem is that I don't "get to" the Windows
> shares. I don't see them anywhere ;) All samba packages are installed, but
> I'm unable to browse the network with smb:/
>
> I can use smbclient to a certain degree (that is, I don't know how to use
> smbclient, but I've tried...): smbclient -L (ip of any of the boxes on the
> network) returns some info, telling me that smbclient actually gets in
> contact with them.
>
> I can also mount a share with 'mount -t
> smbfs //<ip_win_box>/<win_share> /<mnt directory>/'
>
> But, alas, still I can't, or don't know, how to browse the network...:( I'm
> really fresh to this, so I don't say I haven't done anything really wrong,
> though...
>
> Regards,
> Anund Rannestad
>
>
>

So, when you open the "Local Network" icon on your
KDE desktop you get an error saying it can't find
any workgroups?

If this is a home network, check the "NetBios over
TCP/IP" setting for one of the Win XP machines.
I don't know about XP, but for Win 2k:
- right click on the "local network" desktop icon
- select "properties" from the popup menu
- ensure that the "TCP/IP" protocol is installed
   and enabled in the listbox.
- highlight the TCP/IP protocol in the listbox
- click the "Properties" button
- click the "Advanced" button
- click the "WINS" tab
- IF your network obtains IP addresses from a DHCP
   server, enable the "Use NetBIOS setting from
   DHCP server" pushbutton, OTHERWISE (non-DHCP)
   enable the "Enable NetBIOS over TCP/IP" pushbutton.
- click the "OK" button.
- a reboot may be required to enable any change to the
   NetBIOS setting.

The intent is to ensure that the Windows NetBIOS traffic
is done via TCP/IP, rather than via NetBUI. That's what
the default Samba install expects (I believe).

Pay close attention to the "Workgroup" name used by
all of the Windows machines. Windows used to (I don't
know if it still does) force the Workgroup name to
all uppercase in the TCP/IP packets that go over the net.

Start Konqueror on the Linux box and enter an 'smb:/'
URL into the Konqueror Location bar. For example if
the Windows Workgroup name is "billy" enter:

   smb://billy

If that doesn't work try:

   smb://BILLY

If that doen't work - I'm out of ideas.....

Good Luck,
Larry 

-- 
Anti-spam address, change each 'X' to '.' to reply directly.