![]() ![]() Looking in the registry to check the order of redirectors, I can see that Avid's redirector is listed first.ĭoes anyone familiar with inner workings of redirector drivers have any ideas why this might be happening? Of course I don't have Avid's source code for their Nexis client :) If I disconnect the DC from the network (since I can do that) the operation takes whole lot longer and fails in the end, suggesting that the client computer wanted to query the DNS and the DC for the operation, while it should be handled by Avid's redirector. All of this should be handled by the driver):Įcho 2 > \nexis\nxzajem\test.txt in processmonitor reveals this: ![]() Looking at what happens when doing (nexis is Avid's shared storage using the redirector driver and nxzajem is a "workspace" on nexis. When the computer with the driver installed is not joined to the AD everything works as expected, but as soon as the computer is joined to the AD, then it seems that the file operations don't hit Avid's redirector driver, possibly because the client wants to involve the DC and DFS. ![]() On our servers there is a 3rd party network redirector driver installed (from Avid Technology, Nexis filesystem). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |