OpenELEC - SMB Netzwerk | Windows findet nix mehr

Hi,

ab und an hatte ich mal das Problem das Windows OpenELEC nicht gefunde hate über Netzwerk.
Dann ging es irgendwann mal wieder. Jetzt hab ich beide Kisten Rebootet ( mehrmals ) und immer noch kein Zugriff von Windows. Warum?
SMB ist unter OpenELEC Einstellung auf An. Soweit nichts verändert.

Jemand Rat?

Keine Ahnung. Weis von keinem Update
Ich schau mir mal Link an.

Edit: Wird wohl Update Schuld sein.

QUELLE: http://wiki.openelec.tv/index.php?titl…me_SAMBA_Shares

Zitat

SAMBA is the CIFS/SMB sharing server embedded into OpenELEC. From time
to time people post in the forums saying "SAMBA isn't working, now I
can't connect to shares on my HTPC" or "I can only connect to my HTPC
using its IP address" so the purpose of this article is to educate
people on what's going on. The statement that SAMBA is broken is rarely
true. It's usually running fine, and the cause of the problem is simply
the horribly ugly way that NetBios over TCP/IP name resolution works in
Windows!

The reason you cannot see an \\OPENELEC\Share "that was working 5 mins
ago" is down to browser election fights between the computers on the
network. An election fight is a peer-to-peer negotiation over who gets
elected to be in charge of the domain(s) and/or local master browser
list which is the list of computer names that will appear in the Windows
Network Neighbourhood (or it's current equivalent). The machine that
wins the election is determined through a combination of uptime, OS
version and config settings. This masterful piece of design ensures the
outcome is often unpredictable and the election process can take time
(minutes not milliseconds). Over time your HTPC often becomes the
longest uptime device and has probably been elected as the machine in
charge of the master browser. If you reboot your HTPC the browser list
is destroyed and the remaining machines on the network start an election
process to decide who owns the replacement and what the new list will
contain. Once the election is over it will take time (again, minutes not
milliseconds) to distribute the list and ensure every client has the
same version. If you reboot other computers (often trying to rectify the
disappearance of machines resulting from the HTPC being rebooted) they
will re-join the network and announce their availability causing the
election process to restart all over again. It's easy to see how this
process may go round in circles for "some time" before things stabilise.
Sadly, Mac and Linux computers suffer from the same browser-election
purgatory as Windows machines as they (via the embedded SAMBA server)
are ultimately participating in the same ridiculous election process.

In corporate networks this issue is mitigated by having a domain
controller server. The election process still takes place, but the
domain controller is configured to always win the election so you gain a
degree of consistency and the election process completes faster. The
good news is that it's simple to configure the SAMBA server on your
OpenELEC based HTPC to always win the election and become the master
browser. The reason for picking the HTPC to be the master browser is
that it's probably the going to be the computer that has the highest
uptime in your home network.

First you need to create /storage/.config/samba.conf. There is a sample
one in the directory that can be renamed. Then add the lines indicated
below to your [global] section:

[global]

server string = Media Centre(%i)

workgroup = HOME

domain master = yes <-- add this line

local master = yes <-- add this line

preferred master = yes <-- add this line

os level = 100 <-- add this line

netbios name = OPENELEC

security = share

guest account = root

socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536

wins support = yes

syslog only = yes

name resolve order = lmhosts wins bcast host

printcap name = /dev/null

load printers = no

Even if you do this the problem will never be completely eliminated, but
Windows network browsing should become more stable. If it does not
clear the problem the solution is usually to "turn everything off and on
again" so that the old (incorrect) browser list is lost and a new
(correct) one is created. The failsafe way to access your HTPC is to use
it's IP address, e.g. \\192.168.1.2\

If you don't want your HTPC to become the master browser it is also
possible to rig an existing Windows computer the same way. For more
information please read this article

Alles anzeigen

Mal schauen ob ich über Everest in Ordner vom OpenELEC komme.

Ich versuche jetzt erst einmal das mit der Config Datei von Samba. Werde Berichten.

PS: Wäre auch easy way

Weis jemand auf die Schnelle wie ich Zugriff auf OpenELEC bekomme?
Muss Samba.Conf editieren, aber kp wie ich drauf zugreifen könnte.

Edit: Ok, habs!