none
Direct Access Server 2019 Publish Route RRS feed

  • Question

  • hey guys, we have hit the issue described in Richard Hicks blog here - we have two DA servers in a load balanced cluster using a hardware load balancer. The New-NetRoute command as described in his blog works fine for the first server, eveything is happy and DA functions normally. The second server in the cluster, built with the same base OS, in the same subnet on the next IP address along for external and internal network cards, doesnt work.

    The Client IPv6 prefix is published OK but on restarting the server or just the RaMgmtSvc service, the published route is removed. I've tried using PoSH and also the old way with netsh, the route is published fine with both. Restarting the service removes the route, so everytime I load the console it tells me the client prefix isnt published, when it is .... it just doesnt know about it yet as I need to restart the service... and well you get the idea.

    Is this a bug? Time to log a call with Microsoft?

    Wednesday, December 19, 2018 4:06 PM

Answers

  • Yes, the original issue of the route not getting published automatically is a bug and I have been told there is a fix for it, but I have not yet heard how or when the fix will be implemented in the wild.

    If you open a case with Microsoft, I assume they will be able to get you that fix.

    • Marked as answer by Amayacitta Wednesday, December 19, 2018 4:48 PM
    Wednesday, December 19, 2018 4:33 PM
  • I got the same response from Microsoft, which is a shame. Looks like we can't run 2019 DA clustered for the time being..
    • Marked as answer by Amayacitta Friday, February 22, 2019 8:21 AM
    Friday, February 22, 2019 12:26 AM

All replies

  • Yes, the original issue of the route not getting published automatically is a bug and I have been told there is a fix for it, but I have not yet heard how or when the fix will be implemented in the wild.

    If you open a case with Microsoft, I assume they will be able to get you that fix.

    • Marked as answer by Amayacitta Wednesday, December 19, 2018 4:48 PM
    Wednesday, December 19, 2018 4:33 PM
  • Excellent thanks, I'll try get hold of it and see if they have a public KB yet.. if so I'll publish back here.
    Wednesday, December 19, 2018 4:35 PM
  • Case raised with Microsoft :) *fingers crossed*
    Wednesday, December 19, 2018 4:47 PM
  • Hi,

    Any luck getting a KB from Microsoft? We have the same issue. Thanks

    Thursday, February 21, 2019 12:54 AM
  • Hey, the hotfix is due to go public sometime in April. I don’t know anymore than that I’m afraid. We need to keep an eye on the patch releases.
    Thursday, February 21, 2019 3:56 AM
  • I got the same response from Microsoft, which is a shame. Looks like we can't run 2019 DA clustered for the time being..
    • Marked as answer by Amayacitta Friday, February 22, 2019 8:21 AM
    Friday, February 22, 2019 12:26 AM