111 replies to this topic

[sjlouis]

Hello,

I've just installed OpenPli 3.0 and I can't see my ET9000 from the explorer of Windows. The old links give an error and if I try to get new ones, there is a failure.

If I use ftp with DreamBoxEdit or FileZilla, it works.

I can also access the shared directory of the PC from the receiver.

I reinstall the 2.1 and it works. I install again the 3.0 and there is again the failure. Have I forgotten something in the configuration?
I don't remember I've done something with the previous versions.

Thank you .

[sjlouis]

Am I the only one to have this problem?

Thank you.

[littlesat]

Did you install Google Chrome??

[sjlouis]

There is Google Chrome on my PC even if I don't think my wife or my girl use it. I can uninstall it but if I reinstall OpenPli 2.1, I can see again the receiver in Windows Explorer local network.

[littlesat]

Google Chrome destroys the normal W7 ftp behaviour.... I had a hard time here to revert it here... No more Chrome for me

Edited by littlesat, 1 November 2012 - 14:03.

[sjlouis]

Ok and is it suffisant to uninstall Chrome and why is it good with OpenPli 2.1?

[adi22]

sorry, bur this nothing to do with chrome!!

it's a problem of the new kernel3.6 or the images with the new kernel3.6.

i have the same problem with new images. if i go back to image with 3.4.3 - no problems anymore!
there is a long traffic within the xtrend forum...that discuss (in german this issue!

hope the experts here cann help / support.

regards
adi

[littlesat]

Ik have no problems here with W7 and the ET boxes with the 3.6 kernels????

[sjlouis]

Ok, thank you for the response, I was desperated to have no response. What is the kernel? Is it dependant of OpenPli? Can I install another kernel with the same image?

[sjlouis]

I try to install again an 3.0 image from the start (I've deleted the files from autobackup). Then I had to choose all the parameters but the result is the same. If I install a 2.1 backup, I can access the receiver from Windows Explorer.

[Henksat]

The problem is not the image, here i have an et9000, W7, and works perfect.

[sjlouis]

If it isn't the image, why does it work when I install again a backup with a 2.1 image?

[demosat1]

Hi,

I have a similar problem with the detection samba network


Edit your host file and C:\Windows\Sytem32\drivers\etc\host
Add ip and name ( exemple for me ) 192.168.1.40 ET9X00
Save file and now is OK

[sjlouis]

Thank you very very much demosat1 , I've added 192.168.0.4 ET9x00 (I've also this receiver) in the PC Windows (XP familial) host file and Windows Explorer reach immediately my receiver .

As you're French or speak French,, I don't know if you know there is a "French" forum on ET9000 :
http://www.homecinem...cb53#p177267433

Can you explain me why there in no problem with 2.1 and why in 3.0, Windows Explorer see the receiver but can't open the shared repertories?

Thank you again, I lost a lot of time to try to solve this problem and I was a little disgusted.

Jean-Louis

[demosat1]

Salut,

Oui je suis français, nous ne sommes pas les seuls à nous plaindre d'une défaillance de la recherche du réseaux samba avec l'environnement 3.0

D'autre personnes sur le forum et-view parlent du sujet, la solution n'est pas de moi mais de Martin_B voir ce post :

http://www.et-view-support.com/Forum/showthread.php?9759-Samba-PLI3-Fragen/page2&highlight=samba

Bonne journée.

[Henksat]

Only English please, otherwise it will be removed.

[Martin_B]

Yes I posted this "workaround" but it is not a solution.
It could be a problem with NetBios name which seems not to be broadcasted.
I'm directly connected via LAN and have no problem.
Other users who have this problem seem to be connected vial WLAN (WLAN-Router).

Some report that changing the NetBios Name in smb.conf solves the problem (but again not for all).

I found out that when NetBiosName in smb.conf is %h testparm shows:

root et9x00:~# testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[Root]"
Processing section "[Harddisk]"
Loaded services file OK.
...
[global]
		workgroup = DREAM
		server string = Dreambox %h network services
		security = SHARE
		guest account = root
		log level = 1
...

NetBiosName in smb.conf set to "MYBOX"

root et9x00:~# testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[Root]"
Processing section "[Harddisk]"
Loaded services file OK.
...
[global]
		workgroup = DREAM
		netbios name = MYBOX
		server string = Dreambox %h network services
		security = SHARE
...

netbiosname is missing when %h is used. But maybe only testparm can not resolve the hostname (%h)

Regards

[demosat1]

Sorry HENKSAT, I do not speak English, it's easier for me to tell him in French.

Here's to you the contents translated by Google
Other people on the forum and speak-view of the subject, the solution is not to me but Martin_B see this post:

[littlesat]

So is it recommandable we have to change something in de smb.conf?
Strange as I haven't the issue here???

[BBsat]

I have exactly the same problem on 2 windows PC's whit LAN connection (W7 and W8)
restarting the ET didnt solve it
sometimes a restart of PC or ET resolves comparabel connection problems
Connecting via Dreamset; no problem
Open webif in browser; no problem