My windows 7 system disc died and I had to use my old back up disc but since then I can’t connect to my usb attached drives on the Vero V. I am connected on cable LAN to Vero V I can see the drives if I try to connect but windows security is asking for network username and password. I tried FileZilla but that is reporting ecconnection refused.
Try OSMC & OSMC as user and password
Or your set information if you changed it 
That does not work, where do I set username and password for SMB, there is no option in settings/services SMB
Use the default device username and password ie osmc & osmc , when asked for it via the share
You can set this via
Settings >Services>Control
(Sidenote ive noticed if shared device is running smb V4 protocols, still might not connect)
Hope this helps
If ‘Windows’ has already ‘stored’ the username & password and you need to change them you can clear/set them using he Windows Credential Manager (via Control-Panel).
I have connected to it with my win 7 laptop but its not showing in network and I entered it manually, osmc, osmc worked but it results in passcode or user error on my pc. It’s worked for years but since the reinstall only my pc shares show up. Filezilla will not connect either it reports incorrect port, port must be between 1 and 63??? even though I entered 21 or 22. I can’t send my files now only by putting them in a public folder then loading onto my laptop then sending them from it.
Try 46
There are many confusing information in here.
I suggest to first start with sharing the logs from OSMC (MyOSMC - Log Uploader) and post the URL here.
WinSCP will work as that uses SSH protocol. FileZilla can do a few different protocols so you would need to know what the OSMC device is set to listen to.
Even stranger, the laptop that sent 8 files to my usb connected drive is now showing permission denied and I can’t alter permissions from the laptop but the pc is now showing the folders in map network drive but if I try to map them osmc, osmc will not work, wrong password or username
during the initial setup screens did you set a password (the screens where you set language and skin)? If so try using osmc as the user and that password you set at first boot as the password.
I wrote a hotfix that will reset both the system user password and the SMB password back to the default “osmc”. To run it open the My OSMC add-on, click on the cloud (updates), then “manual controls”, and then click on “Apply HotFix”. This will bring up a keyboard that you will then need to type in “tucafebafa” (without the quotes) and then “OK”. A dialog box should come up and you will need to say yes to the warning for it to run. The reset should take place immediately.
This hotfix will be auto deleted in a few weeks from this post unless @sam_nazarko decides to make it permanant.
Can we just get v4 smb please sorted easy via guide then for us v3 protocol is da problem.
I can’t quite understand your post. OSMC is running Samba 4.13 which supports SMB v3.1.1 which is the newest version of SMB that exists.
I did the reset, pc is still reporting wrong username or password. I checked the owners of the folders, it’s osmcvero administrators, I am denied any type of action from my pc.
Share the logs from OSMC as a starting point
What logs would be helpful? What is the procedure?
I have found a workaround, I put the files on a USB drive, plug it into the VeroV triple usb port then use file manager to copy them ( Move just cycles the osmc logo but does not make any movement on the progress bar) I am getting 120+MB/sec so not a bad workaround.
If you followed my directions exactly it should have reset. I tested it myself before posting.
I assume by this you mean you pulled the drive from your Vero, plugged it into your PC, then checked NTFS permissions. If this is the case it should be irrelevant as I don’t think those are being used by samba server or the ntfs driver.
In addition to providing the logs that fzinken asked you to provide twice now, and assuming you did correctly apply my hotfix which should have reset your passwords, the next stop on your end would be to check windows credential manager as thechrisgregory had already mentioned earlier in this thread. In Windows 11 you can just type “credential manager” in the start menu to bring it up. If your using an earlier version of Windows you can google how to bring it up in whatever version of Windows your using. In any event it will look similar to the following…
It is here in the Windows credentials section you need to check the hostname and/or IP address of your Vero to make sure it is set to connect using the username “osmc” and password “osmc”.
As a starting point just simple logs so we can understand the bigger picture.
-
upload the log using
Log Uploadermethod within the My OSMC menu in the GUI -
publish the provided URL from the log set upload, here