@scottalanmiller said in What Are You Doing Right Now:

Point and case.

@scottalanmiller said in What Are You Doing Right Now:

Just updated NextCloud to NC17 beta

Finally, the product is mature.

Anything in BETA is not mature . .

@travisdh1 said in What Are You Doing Right Now:

No, it was Invisible Bob

Eh. .

@travisdh1 said in What Are You Doing Right Now:

Guess who turned on hot-add last night

You?

Last question for now, is the client software QuickBooks?

And more to the point did enabling SMB1 resolve the issue?

@scottalanmiller said in Windows 2019 Slower Than Windows 2012 R2:

@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:

Assuming the customer didn't actually update the client software, which was likely developed with SMB1 only in mind.

the client software is regularly maintained, but not "updated" very much.

So very likely a culprit, do you know what the client software is setup to use?

@scottalanmiller said in Windows 2019 Slower Than Windows 2012 R2:

@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:

Scott migrated a legacy application from 2012 to 2019. That's 7 years of change

Only five. 2012 R2 is from 2014.

SMH, 2 years is still a long time.

@IRJ said in Windows 2019 Slower Than Windows 2012 R2:

@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:

@IRJ said in Windows 2019 Slower Than Windows 2012 R2:

@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:

SMBv1 is disabled by default and it could be causing this kind of issue. Being this is a legacy program, that would be where I would look at. Enabling SMBv1 on this 2019 VM and see if the performance issue is addressed.

SMBv2 is supposed to be a bit faster than SMBv1.

Yeah, it is, but the clients have to communicate to the server, realize the server no longer supports SMB1, and then connect via SMB2 or SMB3 if the server supports it.

This is also affected by the "Access" style client/server which may only operate with SMB1 in mind.

With this logic, you should then be disabling SMBv1 on the clients. That is even if your clients still have SMBv1 enabled. They would mean someone hasn't been paying much attention to vulnerabilities over the past 2 years.

Scott migrated a legacy application from 2012 to 2019. That's 7 years of change. Assuming the customer didn't actually update the client software, which was likely developed with SMB1 only in mind.

But I get the argument, in this case I think the client has caused more problems than the protocols used.

@IRJ said in Windows 2019 Slower Than Windows 2012 R2:

@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:

SMBv1 is disabled by default and it could be causing this kind of issue. Being this is a legacy program, that would be where I would look at. Enabling SMBv1 on this 2019 VM and see if the performance issue is addressed.

SMBv2 is supposed to be a bit faster than SMBv1.

Yeah, it is, but the clients have to communicate to the server, realize the server no longer supports SMB1, and then connect via SMB2 or SMB3 if the server supports it.

This is also affected by the "Access" style client/server which may only operate with SMB1 in mind.