QNAP NAS Community Forum

BrutisNZ wrote: ↑Sat Jun 29, 2019 10:46 am
so the code looks like below
Save the file and restart SMB with /etc/init.d/smb.sh restart

Code: Select all

        …
	# "map to guest" reset. Dependes on "restrict anonymous".
	restrict_anonymous=`/sbin/getcfg global "restrict anonymous" -d "NOT_FOUND" -f ${CONFIG}`
	if [ "x${restrict_anonymous}" == "x2" ]; then
	# restrict anonymous level 2.
		/sbin/setcfg global "map to guest" "Never"    -f ${CONFIG}
		/sbin/setcfg global "invalid users" "guest" -f ${CONFIG}
	else
		/sbin/setcfg global "map to guest" "Bad User" -f ${CONFIG}
		/sbin/setcfg global "invalid users" "" -f ${CONFIG}
	fi
	}

BowGo wrote: ↑Tue Jul 02, 2019 7:06 pm Any news whether or not the latest Beta firmware addresses this issue? 4.4.1.0978 (Public Beta 2) build 20190626
I for one, not wanting to edit files manually, and seeing that downgrading has no effect, the only option is to install a new firmware.

zebulon-ufh wrote: ↑Tue Jul 02, 2019 7:22 pm Do I read that correctly, that this patch now reflects the settings in the web interface gui, instead of the first "quick'n'dirty" thing which was disabling the "guest = invalid" entry what ever else has been configerd via web gui ?

BrutisNZ wrote: ↑Tue Jul 02, 2019 7:35 pm

BowGo wrote: ↑Tue Jul 02, 2019 7:06 pm Any news whether or not the latest Beta firmware addresses this issue? 4.4.1.0978 (Public Beta 2) build 20190626
I for one, not wanting to edit files manually, and seeing that downgrading has no effect, the only option is to install a new firmware.

It is broken in the same way as 4.3.6.0979

Hi there,

The logs will tell you nothing that you haven’t already seen from the logs that I and other people on the Forum have supplied to QNAP.

The problem is in the way the Code of the file smb.sh was rewritten in 4.3.6.0979.

I have pointed QNAP to the FORUM where this was discussed and in that FORUM provided a solution for your customers (who have still not received a solution from QNAP)
A link was provided previously and here is a link to the exact solution and what is wrong with the code viewtopic.php?f=185&t=149124&start=30#p719369
You need to escalate this to someone who is a “Programmer” of the firmware. I’m sure once they understand the problem and see how the code was rewritten they can fix it quickly.

Kind regards,
Bruce.

kizza42 wrote: ↑Wed Jul 03, 2019 6:03 pm Just chiming in to say that this issue affects me as well. I have legacy clients that can no longer access their shares. Please resolve this asap QNAP

njcha wrote: ↑Thu Jul 04, 2019 7:50 am in last year. QNAP always released firmware update by weekly or bi-weekly.
...in normal case...
but. I think this is emergency case... QNAP should release new firmware for fix it.

I use 2 TS-1263 model 80T and 1 TS-1253 80T ... for 300 employee..
and, I can stand anymore....

I will sue... my vendor.