TAPI on Windows 10 disconnected network drives

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • matti18
    Member
    • Dec 2016
    • 4

    TAPI on Windows 10 disconnected network drives

    In our situation when this issue occurred we found our network drives would show disconnected (even though we can still manually explore them). Windows explorer would show a red x next to the network drive. When this happened we could not also elevate any process on said network drive.

    This happens on a Avaya IP Office 500 V2 9.1.6 with the TAPI Drivers on USER CD 4_2_88 and 4_2_64.
  • kirchenlo
    Guru
    • Nov 2010
    • 195

    #2
    Can you please detail your issue? I cannot really see a relation between the network drives and the TAPI driver!?

    Comment

    • matti18
      Member
      • Dec 2016
      • 4

      #3
      The service tapisrv stops and the services workstation service, DNS client and other will also crash.

      Some other people have the same problem (the last posts):
      Just seeing if anyone has had a chance to install the admin suite on the new Windows 10. If so, how'd it go?

      Comment

      • matti18
        Member
        • Dec 2016
        • 4

        #4
        The old driver version 1_0_0_42 and isolating the Tapisrv is working in my case.

        sc config Tapisrv type= own

        Comment

        Loading