Charles


I must have been asleep when Tim issued that, either that or my memory erased it as just to painful. If you're right about it not being fixed and having to use SMB1 then that's a problem since SMB1 is rather insecure (didn't wannacry exploit it)

Roy Lambert

Roy Lambert wrote:

I must have been asleep when Tim issued that, either that or my memory erased it as just to painful. If you're right about it not being fixed and having to use SMB1 then that's a problem since SMB1 is rather insecure (didn't wannacry exploit it)

I'm not aware that the problem has been fixed, gone away or ever will. The way I look at it, MS broke file sharing and have no intention of fixing it, as the performance enhancements for the "user experience" in later versions of SMB (now 3.1?) are mutually exclusive with "good old" file sharing. My take on this also explains why MS no longer support multi-user Access/Jet-based databases. You must use SQL Server or MSDE if you want multi-user Access projects.

We had to restrict our own servers in-house to SMB1 as we would get corruption with DBISAM in local file-sharing mode.

Ian,

<< That is interesting.  Do you happen to know if the SMB2 issue is still present in Windows Server 2012 R2? >>

Yes.

SMB 3.x on Windows 8/2012 and Windows 10/2016 are broken and have various issues with multi-user usage with direct sessions.

I'm issuing a technical bulletin soon - I just got done with testing this all a week or so ago.  I'm also working on prototyping a file I/O service that can replace the redirector, but I haven't gotten very far with it yet.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

<< I'm issuing a technical bulletin soon - I just got done with testing this all a week or so ago.  I'm also working on prototyping a file I/O service that can replace the redirector, but I haven't gotten very far with it yet. >>

Crikey!

Tim Young [Elevate Software] wrote:

> a file I/O service that can replace the redirector

Hi Tim,
   Pardon my ignorance, but what does that mean in layman's language?
Regards,
Ian

Ian,

<< Pardon my ignorance, but what does that mean in layman's language? >>

It basically means a Windows service that pop on the Windows server machine that EDB can talk to, just like the EDB Server.  However, instead of providing database services, it simply provides file I/O services.  There's only a handful of I/O calls that need to be redirected, and this will allow those to occur without any of the issues that SMB is experiencing.  I've been waiting on MS to fix the SMB 3.x issues for some time, and it's pretty clear by now that they don't intend to.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Ian,
>
> << Pardon my ignorance, but what does that mean in layman's language? >>
>
> It basically means a Windows service that pop on the Windows server machine that EDB can talk to, just like the EDB
> Server.  However, instead of providing database services, it simply provides file I/O services.  There's only a
> handful of I/O calls that need to be redirected, and this will allow those to occur without any of the issues that
> SMB is experiencing.  I've been waiting on MS to fix the SMB 3.x issues for some time, and it's pretty clear by now
> that they don't intend to.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com

Ahhh.  Thanks for the clarification.  Now understood.  Bring it on.