Prioritize/Choose RD Gateway Region

%3CLINGO-SUB%20id%3D%22lingo-sub-1189888%22%20slang%3D%22en-US%22%3EPrioritize%2FChoose%20RD%20Gateway%20Region%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1189888%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20found%20that%20for%20some%20of%20our%20customers%20the%20RD%20Client%20is%20flip-flopping%20between%20which%20region%20to%20use%20for%20connecting%20to%20the%20RD%20Gateway.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20customer%20is%20now%20routing%20through%20Australia%20Southeast%2095%25%20of%20the%20time%20after%20changing%20DNS%20host%20to%208.8.8.8%2C%20however%20another%20client%20using%208.8.8.8%20for%20DNS%20is%20being%20routed%20through%20either%20Japan%20West%20or%20Japan%20East%20100%25%20of%20the%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20the%20Japan%20routed%20customer%2C%20The%20RTT%20on%20the%20WVD%20Experience%20Estimator%20is%20showing%20around%20300%20for%20Australia%20Southeast.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tired%20many%20Australian%20DNS%20hosts%2C%20but%20for%20this%20one%20customer%20they%20are%20always%20routed%20through%20either%20Japan%20or%20the%20US.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20we%20can%20prioritize%20or%20statically%20select%20a%20certain%20gateway%3F%20I'm%20confident%20that%20the%20experience%20would%20be%20better%20on%20an%20AU%20gateway%2C%20and%20that%20there%20is%20an%20issue%20correctly%20calculating%20the%20RTT.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20lag%20experienced%20when%20routed%20through%20Japan%20is%20substantial%20and%20I%20have%20had%20to%20resort%20to%20using%20the%20classic%20MSTSC%20method%20of%20connecting%20directly%20to%20the%20VMs%20hostnames%20for%20the%20time%20being.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205667%22%20slang%3D%22en-US%22%3ERe%3A%20Prioritize%2FChoose%20RD%20Gateway%20Region%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205667%22%20slang%3D%22en-US%22%3E%3CP%3EAnything%3F%20This%20is%20a%20total%20showstopper%20for%20us%2C%20and%20we%20can't%20even%20properly%20use%20the%20infrastructure%20we've%20built%20and%20are%20currently%20paying%20for.....%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi there,

 

We have found that for some of our customers the RD Client is flip-flopping between which region to use for connecting to the RD Gateway.

 

One customer is now routing through Australia Southeast 95% of the time after changing DNS host to 8.8.8.8, however another client using 8.8.8.8 for DNS is being routed through either Japan West or Japan East 100% of the time.

 

For the Japan routed customer, The RTT on the WVD Experience Estimator is showing around 300 for Australia Southeast.

 

I have tired many Australian DNS hosts, but for this one customer they are always routed through either Japan or the US. 

 

Is there a way we can prioritize or statically select a certain gateway? I'm confident that the experience would be better on an AU gateway, and that there is an issue correctly calculating the RTT.

 

The lag experienced when routed through Japan is substantial and I have had to resort to using the classic MSTSC method of connecting directly to the VMs hostnames for the time being.

 

Thanks

1 Reply

Anything? This is a total showstopper for us, and we can't even properly use the infrastructure we've built and are currently paying for.....