41 replies to this topic

[WanWizard]

Managed to install Windows 10 in a virtual machine.

 

Created this mount on my box using the mount manager:

 1_0_19_5226_812_2_11A0000_0_0_0.jpg   52.41KB   4 downloads

 

which created this mount:

//172.16.1.108/Users on /media/net/test type cifs (rw,noatime,vers=2.0,sec=ntlmssp,cache=strict,username=test,domain=GOTHAM,uid=0,noforceuid,gid=0,noforcegid,addr=172.16.1.108,file_mode=0755,dir_mode=0755,iocharset=utf8,nounix,r
size=65536,wsize=65536,actimeo=1)

once I enabled "Microsoft File and Printer sharing" on the network interface of the Windows machine.

 

It doesn't seem to support SMBv2.1 or SMBv3 connections, I couldn't make a connection using those versions.

 

This on a box with a 3.14.28 kernel.

[sjlouis]

When you want to share a directory with Windows, the only way we have found is to choice (I hope it's the good English translation) :

 

Configuration panel

Network center and sharing

Modify shared advanced settings                   (you choose them on the left)

All the networks                                              (click on the down arrow)

Disable password-protected sharing

 

Disable this option seems very curious but it's the only way we found to access a shared Windows directory with (since?) Windows 7. And it works for some users with the Zidoo. It doesn't work with my box.

[WanWizard]

Your option is only valid of you don't care about protecting your data.

 

Normally you would right-click on a folder in Explorer, open the "share" tab, give the share a name, and specify the user that has access to it.

 

This sums it up nicely: https://www.teamknow...g-on-windows-10

 

In OpenPLi, the mount manager does not support mounts without a username and password, so that is why your method doesn't work. You could get it to work, but that requires either autofs or a fixed entry in your /etc/fstab.

[sjlouis]

It's the only way we found (other users and me) to access from another box to Windows 7. I enter a user name "Jean-Louis" but no password and it works.

 

I was not very happy to disable the option but after days of tests, it's the only way which works. i have no password to open a user session.

 

The other guys who access to Windows 10 with the Zidoo box have disabled this option, entered a username and no password.

[WanWizard]

As said, the OpenPLi mount manager does not support shares without any protection, or shares without a password.

[sjlouis]

I can access to my shared Windows 7 repertories with the Xtrend and the Vu+ since several years.

 

When you say "does not support", what do you want to say : "it's impossible" or "it may work or it mat not work, it's not guaranteed"?

 

It's annoying to have to add a password if we don't want one   .

[WanWizard]

The mountmanager will always add "username=<youruser>,password=<yourpassword>" to the mount options. If you leave the username and/or the password empty, it will still generate this format.

 

A blank user is not supported, for shares that are public you need to do a guest mount, and this is not an option in the mountmanager. In a full Linux distro, a blank password is supported, so "password=" without a password works for shares that do have a user but don't have a password. However, the busybox version of mount, which is used in the box, is a bit flaky in that area (so, is not guaranteed ).

[sjlouis]

Ok, thank you. I always write a user but never the password. If it's nesaary to use a password, it's for the Windows login or only on the directory?

[WanWizard]

It is the username and password you have assigned to the share.

 

See https://www.howtogee...ow-do-i-use-it/, the section "Share With Local and Networked Users".

 

The problem might well be that you do pass a username, but use an "everyone" share which doesn't have a username/password asssigned to it, but needs to be mounted in "guest" mode, which the Mount Manager doesn't support.

[sjlouis]

Ok.

 

In the Windows 7 share, it works if I use "Everybody". it doesn't work if I use "Jean-Louis" in Pli while the Windows user is "Jean-Louis".

[WanWizard]

I'm willing to bet that the problem there is the dash in your name.

 

That probably means the Mount Manager should generate quoted names and passwords, so username="Jean-Louis" instead of username=Jean-Louis. Our it could be fixed by escaping it with a backslash, so enter Jean\-Louis.

[sjlouis]

I've tried with "Alex", my girl, and one of her repertories and it doesn't work no more.

 

"Jean-Louis" works well with Windows 7.

[WanWizard]

Then I have no clue what you are doing. Only that if you do not specify the SMB version like I told you, it is never gping to work.

[sjlouis]

It does not work with "rw, vers=3.0" and "rw, vers=2.1".

 

As you can see, I've tried with the versions number.

[WanWizard]

I used vers=2.0,

 

As to Windows 10, I wrote:

 

 

It doesn't seem to support SMBv2.1 or SMBv3 connections, I couldn't make a connection using those versions.

 

I couldn't get higher versions to work either.

[sjlouis]

I've tried vers=2.0, 2.1, 3.0. I don't understand why some guys can connect to Windows 10 with the Zidoo box and others can't. It's curious   .

 

Don't worry WanWizzard, it's not dramatic .

 

I've just an interrogation : I've created 2 same shares on the 2 PC (because there is an old PC and the new one). In the Mount Manager, I replaced 192.168.0.26, the old one, by 192.168.0.29, the new one. And MM said "Ok, it's good". Then I thought it did the link with the new PC but when I verified, I could see it was the old link because I've add another file in the old directory to be sure. Have you an idea why MM continue to address the old PC instead of the new one?

 

Thank you   .

[anudanan]

It is possible there differents between  Windows10 professional and Window10 Home.

It can be Windows10 Home works but Windows10 professional not

[sjlouis]

No, there are the 2 cases with the 2 Windows   .

[WanWizard]

I've just an interrogation : I've created 2 same shares on the 2 PC (because there is an old PC and the new one). In the Mount Manager, I replaced 192.168.0.26, the old one, by 192.168.0.29, the new one. And MM said "Ok, it's good". Then I thought it did the link with the new PC but when I verified, I could see it was the old link because I've add another file in the old directory to be sure. Have you an idea why MM continue to address the old PC instead of the new one?

 

Maybe the old one wasn't disconnected?

[sjlouis]

Effectively, it wasn't disconnected but it's not the same IP addresses   .