-
Notifications
You must be signed in to change notification settings - Fork 898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
network share #1576
Comments
What exact version do you use? |
currently i am using OS Version | motionEyeOS 20180602 and its working just fine but version 20186027 will not let me save to a windows share folder |
I believe that has to do with the SMB protocol version. Could you please try and force SMBv1 on your Windows machine? |
unfortunately im not sure how to do that most of those settings are blocked off in windows home |
if you go to the control panel install application, you can have windows functionality checked that the smb1 entry is checked. with the 27 I had the problem that after a while I no longer reached my pizero from the web, while with the pre release of 28062018 everything is fine. Hello |
Can you make an FTP server on your PC? |
quietly, I also mounted last release of July 12 and access via ftp quietly, if you have any problems with windows 10 remember to enable unsafe guest access. in the windows execute tab that can be called via the + R window key, type "gpedit.msc" from there to go to the left in administrative templates ---> network -> lanman workstation ---> enable unsafe guest access check the entry enable and try again see you |
sadly i kinda have no clue whats going on here. im using windows 10 home not server. when i go back to the ....0406 release it works just fine but after that it tells me couldnt mount |
the home version did not activate these options, it was enough even a professional version, then make sure that the smbv1 protocol is active, as written in another post, go to also check that in the control panel, in programs and functionalities, in activation or deactivation of the windows functions, the entry on smbv1 is checked |
I have a similar problem in that since the upgrade to the most recent version I cannot connect to my windows 2000 server share. |
Guys, the latest nightly-dev includes an option to manually choose SMB protocol version. Please test it and see if it fixes your problems. To upgrade to latest nightly-build, use |
Thanks very usefyl |
Changing to SMB3 seems to be working on my end with RPi3 on motionEyeOS dev20180730 and a openmediavault NAS. Thanks!!! |
I'm away on holiday at the moment so will test after my return |
Just upgraded to the latest nightly build, where do I find the option to manually choose the SMB protocol version ? |
Managed to get my windows 2000 server share working again after rewriting the line in the /data/etc/fstab file as follows |
i am trying to save to a network shared folder on windows 10 home
network ip is 192.168.1.208
share name is server
login is windows 10 email
password is windows password
path is /ducks/camera1
/ducks/camera2
when i use the most recent update version released 7/1/2018 it cannot connect to share but when i use the version released about a month ago it works just fine.
so just ;letting you know that something about this most recent update doesnt like saving to a share folder on windows 10 home.
Preliminary Docs
I confirm that I have read the CONTRIBUTING guide before opening this issue.
I confirm that I have read the FAQ before opening this issue.
motionEyeOS Version
I am running motionEyeOS version: (insert your version here, e.g. 20180314).
Board Model
I am using the following board/model: (insert your board model here, e.g. Raspberry PI 3B+).
Camera
I am using the following type of camera: (choose from V4L2, MMAL, Network Camera, Fast Network Camera and Simple MJPEG Camera).
My camera model is: (insert your camera model, e.g. Logitech C290).
Network Connection
My motionEyeOS unit is connected to the network via: (choose your network connection, e.g. WiFi, Ethernet).
Peripherals
I am using the following peripherals that I consider relevant to this issue:
Log Files
I consider the following log files relevant to this issue:
The text was updated successfully, but these errors were encountered: