x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 59 subscribers
  • Views 2071 views
  • Users 0 members are here
Browse Forums
Sage Timeslips Anywhere Announcements
6
topics
0
replies
Sage Timeslips Anywhere General Discussion
10
topics
12
replies
Sage Timeslips Premium Announcements
57
topics
17
replies
Sage Timeslips Premium General Discussion
2k
topics
8k
replies
chadmillerTMG

Timeslips 2019 Network Performance

SOLVED
Posted By

We are using Timeslips 2019 and have been for several months with no problems.  On the server machine, Timeslips resides on the D drive.  We replaced the SSD boot drive (cloned from 128GB drive to 512GB drive) and have the system back up and running perfectly, except Timeslips network performance is horrible now.  Locally, Timeslips opens and functions perfectly, but from any of the network workstations, Timeslips takes almost 30 seconds to open, then once opened, even creating a new slip takes 15 seconds to open the entry box.  We have checked all the normal performance-issue causes (AV/DNS, etc) with nothing resolving our issue.  We have other file shares on the D drive of the server and file transfers from the workstations to the server run in the 120Mb/sec range (gigabit switch), so performance is completely normal there.  The server is a Windows 10 workstation.  TSAdmin reports no errors when run from either a workstation or the server.  Does anyone have an idea or direction to point us to troubleshoot this further?

Thanks in advance for any help!

  • +1
    verified answer

    We actually found a solution for this issue.  Even though DNS was working correctly when connecting from the workstations to the server (via ping, file share, etc), when we made an entry in each of the workstations' HOST file for the server's IP address and fixed the problem.

  • 0 in reply to chadmillerTMG

    THANKS SO MUCH for coming back and posting your resolution. That is the first that I have heard of anyone making a change to the HOST file.  Could you possibly elaborate just a bit on what led you to make the change? I.e., under what scenario would that change be appropriate? And what did your entry look like? NOT an IT person here, just a Timeslips Consultant who often needs to work WITH the IT provider to troubleshoot.

    Nancy Duhon, Esq.
    Duhon Technology Solutions, LLC
    Master Certified Consultant for Sage Timeslips
    Providing individual Consultations and Third Party Remote Desktop Support - including older/unsupported versions.
    404-325-9779
    [email protected]

  • 0 in reply to chadmillerTMG

    Chad,

    I think this would be a fairly significant indicator of an issue in DNS in your network.  Since the service is doing a name lookup, it would seem that there is a conflict or error causing an issue internally.  What does a Trace Route show when pointing to that server name? A HOSTS file entry just bypasses the lookup process, just as changing the servername in the Timeslips Administrator would, by likewise using an IP address instead of the machine name.

    I think you would agree this is a band-aided workaround, and not a true resolution.

*Community Hub is the new name for Sage City