Windows 8.1.1 LogIn to SMB

RouterOS General
1

Regards to all. I have a small problem with logging on mikrotik smb. When I try to open mikrotik smb with my laptop on which is windows 7 everything works great. But when I try to open mikrotik smb from my PC on which is Windows 8.1 update 1 i get some sort of network error 1208. If anyone has a solution I would be Grateful.

Meybe Windows 8.1 update 1 force logging to my email address even though I write the second username and password for logging to MikroTik smb ?

here is part of MikroTik log:

smb,info connection from: 10.x.x.x
smb,info user xxxx logged in
smb,info user xxxx connected to share IPC$
smb,info IPC$ active sessions: 1
smb,info connection from: 10.x.x.x
smb,error invalid user xxxx.xxxx@hotmail.com tried to log in
smb,error user xxxx.xxxx@hotmail.com authentication failed
smb,info closing connection with 10.x.x.x
smb,info connection from: 10.x.x.x
smb,error invalid user xxxx.xxxx@hotmail.com tried to log in
smb,error user xxxx.xxxx@hotmail.com authentication failed
smb,info closing connection with 10.x.x.x


RB751G-2Hnd
RouterOS 6.15

2

This problem is caused by the “Secure Negotiate” feature that was added to SMB 3.0 for Windows Server 2012 and Windows 8. This feature depends upon the correct signing of error responses by all SMBv2 servers, including servers that support only protocol versions 2.0 and 2.1. Some third-party file servers do not return a signed error response. Therefore, the connection fails.

You can read the Microsoft KB article here: http://support.microsoft.com/kb/2686098

See my post here http://forum.mikrotik.com/t/feature-request-smb-v3-or-proper-v2-support/78393/1 and another post here with the solution http://forum.mikrotik.com/t/rb951ui-smb-not-share/77304/1

The solution involves disabling secure signing which in my opinion isn’t really a solution. The issue is with MikroTiks implementation of SMB.

3

I found it, solution is to write 2 commands in PowerShell ISE as administrator.



Set-SmbClientConfiguration -RequireSecuritySignature $false
Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters” RequireSecureNegotiate -Value 0 -Force

4

SMB in MikroTik works with every device in the world (including Windows 7, XP, Android, Linux, iOS). Only system that does NOT work is Windows 8.1 update 1!
Do you really think that MikroTik is wrong?!

5

Since Microsoft are the “leaders” of SMB… in that they force the direction of other implementations… yeah… MikroTik is kind of wrong. Although I’m not sure “wrong” is the right word, any more than a browser is “wrong” not to support a particular CSS directive or a JavaScript API… I think a better word is “incomplete” - MikroTik’s SMB implementation is incomplete.

6

Nobody is wrong. It is just Microsoft trying to sell their server platform by preventing users to walk the samba route.

7

Microsoft is only trying to make things more secure. It is not that much of an ask for things talking to Windows to make sure the requests are signed.

8

Everything is OK when they are trying and asking, not forcing. This is problem of Windows 8 and Server 2012 users.

9

To say short: Windows 8 and Server 2012 are disasters. Those systems have so bad reputation that if something does not work we assume that it is their fault (or another update). Both, almost does not exist in business environments. For every ONE sold new device or computer with Windows there are THREE sold new devices with Linux. What I want to say is that Microsoft is not “leader” anymore. They have to adopt to others and not force others to adopt to them. If I have problem between Windows 8 (or 2012) and MikroTik I will replace Windows 8 (2012) with something else.

EOT for me.

P.S. Look at his log:

smb,info user xxxx logged in
smb,info user xxxx connected to share IPC$
smb,info IPC$ active sessions: 1
smb,info connection from: 10.x.x.x
smb,error invalid user xxxx.xxxx@hotmail.com tried to log in

Do you think this is normal that Windows tries to log in to SMB using email address?

10

… And that is not “true”, but instead, just as you said, just “bad reputation”… or more precisely, a false perception, born due to the bad reputation.

It’s like how MikroTik has a somewhat bad reputation in Cisco circles (as in “it’s a second grade router”; I’ve ACTUALLY had a few people say that to me; None had ever used a MikroTik router of course), yet I’m sure you’ll agree that’s rubbish.

You’re saying that as if a market failure of those versions immediately removes the old ones… Microsoft’s implementation of SMB is still the most used one, by virtue of Windows versions prior to 8 being the most common OS-es, and a lot of those people aren’t migrating to Linux devices any time soon. A lot of them will rather migrate to Windows 9 or whatever newer version gets better reputation among the general public. That newer version will in turn keep the features from Windows 8.1, if it doesn’t expand them too, so in the end… Whether we like it or not (and I don’t like it any more than you do)… Microsoft’s SMB implementation is the “de facto standard” that everyone else follows, as opposed to it being a formal “fixed” standard (think HTTP, CSS, JPEG, etc.) that everyone (including Microsoft) follows.

Right, right… because Windows 7 (or any Linux flavor for that matter) is just flawless with no problems on its own, and the workaround above is soooo much more complicated, error prone and all.
(sarcasm… duh)

With Windows 8.0 and above, where you can make your Windows username be a Microsoft account - yes, it IS normal. Windows in general first tries to log in with your current username and password, so if those happen to be associated with a Microsoft account, that’s what you’ll see in the logs.