Skip to main content
Solved

TimeXtender Desktop on local machine


Forum|alt.badge.img

Hi!

We have installed TimeXtender and ODX on an Azure VM (TimeXtender 6536.1). They are both running in ADF.

I have installed TimeXtender Desktop locally on my own computer (outside of the VM) and I’m able to log in and open the instances. However, when I try to execute a table I get this error:

-Execute Execution Package Execution Queue Default 'Failed'
    No DNS entries exist for host <nameofVM>.
    No such host is known

I am connected to the same network as the TimeXtender VM ('nameofVM') through a VPN connection.

Is this setup not supported or am I missing some network configurations?

Best answer by sigsol

Thanks Rory.

The issue was firewall settings on the VM itself. Works now.

View original
Did this topic help you find an answer to your question?

4 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 649 replies
  • March 4, 2024

Hi,

if your computer is outside of the VPN, how would it be able to communicate with the resources you defined for your TimeXtender platform? You can see the instances because the metadata is stored on the instance repositories TimeXtender hosts for you and your login allows you to connect to those. Your infrastructure, VMs and databases, will not be reachable however.


Forum|alt.badge.img
  • Author
  • Contributor
  • 25 replies
  • March 4, 2024

I’m connected to the network through Azure VPN Client.


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 649 replies
  • March 4, 2024

Hi,

then your machine is inside the VPN not outside. You can use nslookup <hostname> from the CLI / Powershell to verify that the dns names of your ODX storage endpoints and databases are reachable from your machine. Given the error message it seems likely they are not, there can be many causes depending on your networking setup.


Forum|alt.badge.img
  • Author
  • Contributor
  • 25 replies
  • Answer
  • March 4, 2024

Thanks Rory.

The issue was firewall settings on the VM itself. Works now.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings