SMB and TimeSlips speed

Question

There have been a lot of issues with TimeSlips speed related to how fast a new slip is saved. This has become a deal breaker when a client wants to upgrade to a more recent TimeSlips version. 
 On the Sage conference call today Terry Rosenthal mentioned that that issue relates to Service Message Blocks [SMB] and that that has been addressed in a previous Blog on this Forum. Can anyone repost or tell where to get that information?

Terryr · Answer

Copy of original post: 
 Thought I would post this for others who are consistently battling the speed issue at a client site. Client was extremely disappointed with response time in 2014 after upgrading from 2012. We tried all of the normal things (excluded Timeslips from anti-virus and firewall, restored all windows, etc.). After speaking with Roger in support, he mentioned that the IT guy should look at any errors in SMB (Microsoft server message block). Interestingly, when they installed Worldox they had to change a setting in the SMB protocol. Rather than reverse that change, the client moved the program and data to their older 2008 server. Performance was amazingly fast and the client is very happy with Timeslips 2014. 
 Here is part of a description from the Microsoft website which makes sense: 
 Although its main purpose is file sharing, additional Microsoft SMB Protocol functionality includes the following: 
 Dialect negotiation 
 Determining other Microsoft SMB Protocol servers on the network, or network browsing 
 Printing over a network 
 File, directory, and share access authentication 
 File and record locking 
 File and directory change notification 
 Extended file attribute handling 
 Unicode support 
 Opportunistic locks 
 Perhaps this will help someone else one of these days!

Sage Timeslips

SMB and TimeSlips speed

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING