More SAMBA trouble

[nilsA]

OK, I installed Feisty Fawn on an old Lifebook - and everything went fine.

Except Samba networking.

I have installed Samba - and tried a lot of different things by searching in this Forum + Googling.

The problem seems to be that when I fix one problem, something else is broken.

For instance -

msdfs proxy = no

keeps reappearing.

Then I can see both the Kubuntu and the Windows computers, but only read from Kubuntu.

Then I can't access anything but another user group (not mine - an empty pictures folder)

My problem seems to be that there is too much information, too many HOWTO's that just resemble how things are in Feisty Fawn (or at least my PC).

I'm simply not able to sort out where to start, what to look for to begin building a working SAMBA-WINDOWS network.

It's a WIFI network, where the WINDOWS PC's talk just fine - sort of; it's WINDOWS

Could someone give me the "hand holding" it seems I need to sort this out?

[penguin.ch]

Re: More SAMBA trouble

Could someone give me the "hand holding" it seems I need to sort this out?

Start from scratch, read: from an empty smb.conf and set this up by hand (in particular without the "aid" of what KDE / Kubuntu offers for "support") - thereby using only options you really have understood (and omitting everything else) ...

Plan B (even worse): read this manual - as a whole 8)

[nilsA]

Re: More SAMBA trouble

Could someone give me the "hand holding" it seems I need to sort this out?

Start from scratch, read: from an empty smb.conf and set this up by hand (in particular without the "aid" of what KDE / Kubuntu offers for "support") - thereby using only options you really have understood (and omitting everything else) ...

Plan B (even worse): read this manual - as a whole 8)

... there's just one tiny problem - the manual is about as easy for me to read as Old English, Old Norse, Icelandic or Dutch. I get the overall meaning, but too many words, concepts just has no meaning for me.

At the present I get this output:

nils@nils-lifebook:~$ sudo smbclient -L localhost -U%
Domain=[HOYDALEN] OS=[Unix] Server=[Samba 3.0.24]

    Sharename    Type   Comment
    ---------    ----   -------
    public     Disk   Data
    IPC$      IPC    IPC Service (Samba 3.0.24)
Domain=[HOYDALEN] OS=[Unix] Server=[Samba 3.0.24]

    Server        Comment
    ---------      -------
    NILS-LIFEBOOK    Samba 3.0.24

    Workgroup      Master
    ---------      -------
    HOYDALEN
nils@nils-lifebook:~$

... and nothing when I try connecting either way.

[penguin.ch]

Re: More SAMBA trouble

... there's just one tiny problem - the manual is about as easy for me to read as Old English

So what? It's like Shakespeare for the modern (read: ignorant) masses

O.k., "Plan C" then: this setup I've been using for several months now (with Kubuntu 06.10 as server and several Linuces as clients) ... you may try to "deconstruct" that - with additional explanations provided from my side as need be ...

--

Addenum: "dead tree approach"

[nilsA]

Re: More SAMBA trouble

O.k., "Plan C" then: this setup I've been using for several months now (with Kubuntu 06.10 as server and several Linuces as clients) ... you may try to "deconstruct" that - with additional explanations provided from my side as need be ...

OK; I used KDESU Kate to edit smb.conf;
Cleared the file, copied your list of commands, and changed this:

[global]

workgroup = HOYDALEN
interfaces = ath0

ath0 being the name of my WIFI card as indicated when it connects. (I'll probably be adding eth0 later, so I can wire-connect too.

and this:

[myDesk]

path = /home/nils/Desktop
browseable = yes...
...
username = nils

As I don't at the moment have a printer attached to this PC, I commented (#) out the printer lines.

Still - nothing happens. I have two other PCs talking friendly to each other - one XP one 2000SP4 - nothing visible from this Kubuntu PC, but itself.

The smbclient command output looks ok, doesn't it?

nils@nils-lifebook:~$ sudo smbclient -L localhost -U%
Password:
Domain=[HOYDALEN] OS=[Unix] Server=[Samba 3.0.24]

    Sharename    Type   Comment
    ---------    ----   -------
    myDesk     Disk
    IPC$      IPC    IPC Service (Samba 3.0.24)
Domain=[HOYDALEN] OS=[Unix] Server=[Samba 3.0.24]

    Server        Comment
    ---------      -------
    NILS-LIFEBOOK    Samba 3.0.24

    Workgroup      Master
    ---------      -------
    HOYDALEN       NILS-LIFEBOOK

Seems like I have a Samba network that doesn't like Windows

[penguin.ch]

Re: More SAMBA trouble

Seems like I have a Samba network that doesn't like Windows

I doubt that there is a Samba network at all ...

Are you able to ping the Kubuntu server (to be) from the Windoze clients (to be)?

[Ant2ne]

Re: More SAMBA trouble

http://kubuntuforums.net/forums/inde...opic=3084171.0

Remember
netbios name = AWindowsUserName

[Detonate]

Re: More SAMBA trouble

You do have "File and Printer Sharing" enabled on the M$ machines, don't you? And you do have folders that are shared?

[nilsA]

Re: More SAMBA trouble

Seems like I have a Samba network that doesn't like Windows

I doubt that there is a Samba network at all ...

Are you able to ping the Kubuntu server (to be) from the Windoze clients (to be)?

Windows -> Kubuntu ok.
Windows -> Windows ok.
Kubuntu -> Windows no luck. (Transmitted, not received.)

[nilsA]

Re: More SAMBA trouble

http://kubuntuforums.net/forums/inde...opic=3084171.0

Remember
netbios name = AWindowsUserName

One of the users on my Windows PCs is the same as the one I use on this Kubuntu PC, so that shhouldn't be a problem?

However, you solved one of the "Old English" (which is much older than Shakespeare btw.) words/concepts for me.

[nilsA]

Re: More SAMBA trouble

You do have "File and Printer Sharing" enabled on the M$ machines, don't you? And you do have folders that are shared?

On the WIndows PCs obviously, as the network just works there.

On this? Eh, well, the idea is to share the desktop, and I'm not quite sure how to do that.

But the PC should show anyway, shouldn't it?

[penguin.ch]

Re: More SAMBA trouble

Windows -> Kubuntu ok.

O.k., then what becomes visible when you point the client's file manager to the address (read: name) of the common workgroup? At least the server as a whole should be mentioned - as, for example, in my case, FAMILY shows FREYJA ...

[Ant2ne]

Re: More SAMBA trouble

http://kubuntuforums.net/forums/inde...opic=3084171.0

Remember
netbios name = AWindowsUserName

One of the users on my Windows PCs is the same as the one I use on this Kubuntu PC, so that shhouldn't be a problem?

However, you solved one of the "Old English" (which is much older than Shakespeare btw.) words/concepts for me.

It could very well be the problem! In smb.conf there is a line

netbios name =

and it needs to be = to a WindowsUserName that has authorization.

[nilsA]

Re: More SAMBA trouble

Windows -> Kubuntu ok.

O.k., then what becomes visible when you point the client's file manager to the address (read: name) of the common workgroup? At least the server as a whole should be mentioned - as, for example, in my case, FAMILY shows FREYJA ...

Funny thing - yesterday I did several init.d - routines /stop-start) and restarts - and found only this PC.

Today - the network is ok. Nothing like a good night's sleep?

Thank you; I have a (hopefully) stable network, understand a little of the gibberish in the smb.conf file, and won't touch any graphical manipulation of my smb.conf file until it is declared safe.

[penguin.ch]

Re: More SAMBA trouble

and won't touch any graphical manipulation

From my point of view, the problem with these "GUI aids" is that they merely attempt to hide the given complexity (which is huge - Samba is a reverse engineering of sorts of a rather obsure M$ protocol ...), thus factually adding even more (read: another layer of) complexity - instead of trying to make things more transparent, thus better understandable.