Windows 10: Build 9226 - cant connect to shares?

Just upgraded to the latest build and find I can no longer connect to any samba shares. It worked fine on the previous build.

Seems to be a common problem - anyone found a solution yet?
"The account is not authorized to login from this station" - Microsoft Community


"The account is not authorized to login from this station"

:)

 

Folders Refuse to be Renamed

Thanks for your prompt reply.

1. What is the current build of your Windows 10 (1709) PC?

** Version 1709 (OS Build 16299.64) " Attached "

2.Are you able to rename the folders prior to the update?

** Yes

3. Are you getting an error message when renaming folders?

** NO

By the way , I've tried to rename the folders in D: drive by either using F2 Function button or right click and choose Rename. Also ,I tried to rename by using windows explorer toolbar.

But No SENSE .

 

updates

cant update in os build 14393 on metered connection

 

Hi there
I've posted on this before

What you have to do is in the W10 Firewall is to BLOCK INBOUND port 139 in advanced settings of the firewall. Note do it on the W10 firewall - leave the others alone.

Then it will work fine

SAMBA TO W10 (redsquiirel) -- OK
W10 (RedSqurrel) to Samba (gylfi) OK

Blackdog is W8.1 - no problems - it's only INBOUND to W10 from SAMBA and W7 / earlier Windows.

If Windows (W10) forewall not switched on it won't work --you must block inbpound TCP port 139.

Note - depending on your network speed you might have to be a little patient if you have large directories.

You shouldn't have to change any SAMBA Conf settings either. Ensure also the windows shares are still "shared" of course.

 

No such luck - not working.

Firewall is enabled and I've blocked inbound to TCP139.

This is connecting from W10 to samba shares.

 

Hi there

Sometimes it takes a while for the network to propagate. Re-start the Samba server (both NMB and SMB daemons).

The problem normally is FROM SAMBA to WINDOWS.

Here's part of my samba config file (renamed to smb.txt to conform to Forum naming for attachments).
I've just got the basic minimal security in it - fine for testing. Also did you add your user name to samba via smbpasswd -a username. I'm still using the older security system. Open with Wordpad - better formatting.

Cheers
jimbo

 

This fixed the issue:

Using REGEDIT it's necessary to create a DWORD value called 'AllowInsecureGuestAuth' in HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters and set this new value to 1.

 

No problems at my end on any of my shared devices (tablets, PCs and NAS). Everything is instantly accessible except I just need to re-enter the passwords.

 

Hi there

You shouldn't have to do that as I assume it was connecting TO samba shares FROM a W10 machine that was giving you problems. Normally FROM W10 has no problems whatsoever. The problem comes when you are trying to access W10 shares FROM SAMBA / W7/XP. Windows 8 / 8.1 have Zero problems with W10 connectivity BOTH WAYS. (That includes things like Windows tablets and NAS devices).

Also the insecure guest stuff you should set in the SAMBA.CONF file how you manage Guest and these "un-privileged accounts".

Still if your workaround fixes it - that's fine but on the whole fiddling around with the registry shouldn't be the recommended way of getting a system to work properly.

Cheers
jimbo

 

Thank you. That did fix it for me *Smile.

I had the opposite problem of Jimbo45. Access TO Windows 10 from other Windows 8.1 PC's was not a problem, but FROM windows 10 to any other device (EXCEPT my WD Live TV ??) gave the error:
"The account is not authorized to login from this station"
After editing the regdatabase as described above, it now works.
But as Jimbo45 is writing ... it should NOT be nessesary to fiddle around in reg.database, but so far this is the only solution I have found

 

Hi there

If you have a W7 or Vista or XP machine (real or Virtual) can you also check whether those machines will connect TO W10 shares with that fix applied. I'm also assuming you are using standard DHCP on a home type LAN and not a special domain logon or using HOSTS or other stuff with fixed IP addresses.

My XP sand W7 systems connect both ways just fine without the registry fix suggested. The firewall rule was needed though in my case.

Cheers
jimbo

 

Sorry, I only have 2 other PC's both running windows 8.1. (A laptop and an "office"-PC)
Yes, I'm running standard DHCP on homelan.

The WD Live TV that did work "out of the box" is a Linux kernal AFAIK, the firewall rule was not applied.

 

Thanks for the help, guys. My WD My Book Live could not be accessed. A Vista machine was fine but not this 9926 one.

Tried the FW block of port 139 to no avail. Instant success after making the registry mod.

Now I expect my backups to resume!

 

This "share" issue is hit or miss.
I did another clean install last night when the Action Center stopped working. Then cloned it to an SSD to keep the original installation in HDD as a backup.

The cloned SSD is having the same share issue as stated above.
Then I fired up the original installation on HDD and it was fine. It immediately connects with other PCs.
So I re-cloned again the HDD and wiped out the same SSD. Everything is fine after re-cloning. Sharing is okay.

 

give the man a cigar*Start