Re: SMB Browsing Problem
From: Chris Cox (ccox_nopenotthis_at_airmail.net)
Date: 07/09/05
- Next message: Chris Cox: "Re: New Linux computer"
- Previous message: steve: "Re: My Professor Says Linux Sucks and Is Not Real Unix."
- In reply to: Larry I Smith: "Re: SMB Browsing Problem"
- Next in thread: Larry I Smith: "Re: SMB Browsing Problem - FIXED"
- Reply: Larry I Smith: "Re: SMB Browsing Problem - FIXED"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 08 Jul 2005 17:53:45 -0500
Larry I Smith wrote:
> Chris Cox wrote:
>>Larry I Smith wrote:
>>>Chris Cox wrote:
>>>>Kevin Nathan wrote:
>>>>>On Thu, 07 Jul 2005 16:59:04 GMT
>>>>>Larry I Smith <larryXiXsmith@verizon.net> wrote:
>>>>>
>>>>>>The SuSE machine cannot see/connect to the Win2k machine
>>>>>>(e.g the "Network Browsing" desktop icon does not work, neither
>>>>>>does "smb://..." in Konqueror, etc). I can connect by IP
>>>>>>address, but even then no files/directories are displayed.
>>>>>>
>>>>>I haven't used Samba in quite awhile, so I will ask a couple of stupid
>>>>>questions and then I'll return to my corner . . . :-)
>>>>>
>>>>>Do you have matching username/passwords on Linux/Windows, or have you
>>>>>mapped Linux users to Windows users?
>>>>>
>>>>>Are your permissions correct on smbmount (smbmnt? don't remember) and
>>>>>smbumount?
>>>>>
>>>>>
>>>>You're having more problems than what I usually see.. but I do
>>>>know that it helps if the Samba box is a member of the domain.
>>>>man winbindd (see net join) You don't have to do the whole
>>>>smashed-mapping of Windows ids into your Linux acct system... just
>>>>need to have the host as a member of the domain.
>>>>
>>>>Otherwise my host will probably not show up in the neighborhood.
>>>>
>>>>It gets quite complicated nowadays.
>>>>
>>>There's no domain, only a workgroup. It's a small home network,
>>>and all machines are members of the same workgroup. Samba on
>>>the SuSE box is also a member of the workgroup.
>>>
>>>The Win2k machines (all workstations, no servers)
>>>can all see & connect to the SuSE box (because it's running a
>>>Samba server that's in the same workgroup). But the SuSE box
>>>can not see or connect to the Win2k boxes by their NAMES.
>>>The SuSE box CAN see & connect to the Win2k boxes by their
>>>IP addresses, but no files are visible once the connection
>>>(by IP) is made, e.g. entering smb://192.168.1.101/C (where "C" is
>>>a valid Win2k share) in Konqueror asks for the Win2k id/password,
>>>does the connect, but displays only an empty browse window - none
>>>of the files/directories from the Win2k box are visible.
>>>
>>>Regards,
>>>Larry
>>Though I hate to overuse the term.. sounds like a name resolution
>>problem that can either be solved by putting the Windows boxes
>>into your DNS or by using winbind (overloaded, different from
>>what I was talking about earlier) into your nsswitch.conf on your
>>Linux hosts in the host resolution area to allow them to do Windows
>>style name lookups.
>>
>>/etc/nsswitch.conf
>>
>>hosts: files dns wins
>>
>>I'd make sure that your Samba server is running a WINS to help
>>keep the network broadcast traffic down. Make sure the clients
>>use that Samba/WINS server in their network config.
>>
>>
>>
>
> The problem is that the machines get dynamic IP's via DHCP (from
> a LinkSys firewall). So' their IP's are always changing. Even the
> SuSE box might be booted to/from Win2k 2 or 3 times a day.
> I actually have 4 pc's, but I'm just trying to get the 1st two talking
> before I tackle the others. When all 4 pc's are booted into Win2k
> (DHCP, no Wins, just a common Workgroup) everything works as it's
> supposed to. The problems occur when the dual-boot pc is booted into
> SuSE. Three of the pc's are laptops that also have to work on other
> nets (when they are taken to school, to the office, etc), so DHCP has
> to stay.
>
> Samba on the SuSE box is config'd to be the 'local master', so netbios
> name caching should occur via UDP broadcasts (it always did with earlier
> versions).
However any time a box comes on or off the network an election will
be forces and the ensuing broadcast storm will happen. Painful.
Browser masters are different from WINS server and different from
what happens when you have an actual Windows domain.
Best (from a network traffic point of view):
Windows Domain
Resonable
Local Linux based Samba WINS with simple workgroup
Worst
NetBIOS Broadcast with simple workgroup
Regardless, both the WINS soln and NetBIOS soln result
in network browser election.. even if you know your
Linux box is going to win (provided you have raised it's
virtual OS release number so that it WILL win).
However WINS helps when doing resolution of the host...
and it sounded like it was a resolution problem.. not
merely a Network Neighborhood (which relies on the Browse
Master) issue.
>
> The big killer is that even when accessing the Win2k box from the
> SuSE box by its IP address (e.g. smb://192.168.1.101), I'm asked for
> the Win2k ID/password, I supply them, Konqueror then connects but
> displays a blank browse window - no files/directories on the Win2k
> box are visible. The Suse desktop "Network Browsing" object does
Well my current situation is a bit different since we run a plethora
of domains and workgroups. When I do smb:/ from Konq on 9.3 I see
all of Domains and Workgroups... then I can nest down to the machine
and I can get in. BUT I do have to do a NTLM style authenticate to
get in. I even do local automounted smbfs areas to our network
file shares (again, with hardcoded username/pass credentials in my
automount files).
> the same thing - shows no files on the Win2k share after "successfully"
> connecting. KNetAttach (on the System menu) exhibits the same
> problem when the IP of the Win2k box is used to connect.
> If connecting by IP, with a valid ID/password, doesn't work, then
> it really doesn't matter whether or not the Samba netbios name caching
> (via nmbd) is working or not.
>
> What's frustrating is that this all worked perfectly when the SuSE
> box was running SuSE 9.2; but it doesn't work with SuSE 9.3.
What happens when you do an smbclient -L <supposed-linux-browse-master>?
Do you get a list of all of the machines?? If not, your Linux
box is likely NOT the browse master... try:
nmblookup -M -- -
And see what Browse Masters are out there and try doing the smbclient -L
against one of them.
You may also want to download nbtscan and do a scan on your network:
e.g.
nbtscan 192.168.1.0/24
and see if you see all of the Windows hosts AND your Linux box
(though it will show a MAC address of all zeros).
It's hard to diagnose these things remotely.. and my brain is
thinking about other things at the moment (busy).
Regards,
Chris
- Next message: Chris Cox: "Re: New Linux computer"
- Previous message: steve: "Re: My Professor Says Linux Sucks and Is Not Real Unix."
- In reply to: Larry I Smith: "Re: SMB Browsing Problem"
- Next in thread: Larry I Smith: "Re: SMB Browsing Problem - FIXED"
- Reply: Larry I Smith: "Re: SMB Browsing Problem - FIXED"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
