Lenny-Sambaserver unter Windows nicht zu sehen

[honky]

Ich habe bei mir in der Küche einen frisch eingerichteten Rechner mit Lenny und Samba stehen. Auf meinem Notebook habe ich ein frisches Windows XP installiert und kann mich im Windows-Explorer über Extras mit der Sambafreigabe verbinden, was auch bei einem Neustart von Windows gut funktioniert. In der Netzwerkumgebung sehe ich allerdings meinen Server in der Küche nicht. Woran liegt das?

[rendegast]

Code: Alles auswählen

testparm -v

# vielleicht auch smb.conf ohne Kommentare:
cat smb.conf  |  egrep  -v  "^ *#|^$"

[honky]

Code: Alles auswählen

testparm -v

http://nopaste.debianforum.de/20397

Code: Alles auswählen

# vielleicht auch smb.conf ohne Kommentare:
cat smb.conf  |  egrep  -v  "^ *#|^$"

http://nopaste.debianforum.de/20398

[rendegast]

Liegt es daran? :

SECURITY = USER

This is the default security setting in Samba 3.0. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the username map parameter).
Encrypted passwords (see the encrypted passwords parameter) can also be used in this security mode. Parameters such as user and guest only if set are then applied and may change the UNIX user to
use on this connection, but only after the user has been successfully authenticated.

Note that the name of the resource being requested is not sent to the server until after the server has successfully authenticated the client. This is why guest shares don´t work in user level
security without allowing the server to automatically map unknown users into the guest account. See the map to guest parameter for details on doing this.

Code: Alles auswählen

	map to guest = Never

[honky]

Was muss ich denn jetzt an der smb.conf genau ändern? Mein Intrepid Ibex kann den Lenny-Server übrigens auch nicht "sehen". Beide hängen im gleichen Subnetz.

[rendegast]

map to guest (G)

This parameter is only useful in SECURITY = security modes other than security = share and security = server - i.e. user, and domain.

This parameter can take four different values, which tell smbd(8) what to do with user login requests that don´t match a valid UNIX user in some way.

The four settings are :

· Never - Means user login requests with an invalid password are rejected. This is the default.

· Bad User - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the guest account.

· Bad Password - Means user logins with an invalid password are treated as a guest login and mapped into the guest account. Note that this can cause problems as it means that any user
incorrectly typing their password will be silently logged on as "guest" - and will not know the reason they cannot access files they think they should - there will have been no message given
to them that they got their password wrong. Helpdesk services will hate you if you set the map to guest parameter this way .

· Bad Uid - Is only applicable when Samba is configured in some type of domain mode security (security = {domain|ads}) and means that user logins which are successfully authenticated but which
have no valid Unix user account (and smbd is unable to create one) should be mapped to the defined guest account. This was the default behavior of Samba 2.x releases. Note that if a member
server is running winbindd, this option should never be required because the nss_winbind library will export the Windows domain users and groups to the underlying OS via the Name Service
Switch interface.

Note that this parameter is needed to set up "Guest" share services when using security modes other than share and server. This is because in these modes the name of the resource being requested
is not sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection to the share) for
"Guest" shares. This parameter is not useful with security = server as in this security mode no information is returned about whether a user logon failed due to a bad username or bad password,
the same error is returned from a modern server in both cases.

For people familiar with the older Samba releases, this parameter maps to the old compile-time setting of the
GUEST_SESSSETUP value in local.h.

Default: map to guest = Never

Example: map to guest = Bad User

Bei Dir ist 'security = USER', also probiere doch mal aus

Code: Alles auswählen

map to guest = Bad User

[honky]

Negativ. Mit /etc/init.d/samba restart neu gestartet. Die Debian-Kiste erscheint auch bei meinem Intrepid Ibex nicht unter Orte / Netzwerk. Auch in der Windows-Netzwerkumgebung ist nichts zu sehen. Mein MacBook ist momentan in der Reparatur. Kann ich nicht testen.

[Theophil T.]

Hallo honky,

wie ist die Ausgabe der Samba-Logdatei? Ich hatte das gleiche Problem, als bei mir in der smb.conf die "interfaces"-Anweisung falsch war. Samba kann dann die Broadcast-Anfragen der Clients nicht beantworten. Hier müsste die für Deine Verbindung zuständige Schnittstelle eingetragen werden:

Code: Alles auswählen

smb.conf
interfaces = 127.0.0.0/8 <interface, z.B. eth0>

Viele Grüße
Theophil