Feature Request: Try IPv4 if IPv6 can't connect to MeshCentral server.

Open af7567 opened this issue 4 years ago • 1 comments

HI, I have just been installing meshagent64 remotely on a few Windows 10 PCs and one of them just wouldn't connect even though installation was successful. I eventually found out that IPv6 is broken on that PC for some reason so the connection to my server was timing out. My server address has an A and AAAA record in DNS, the problem PC can connect OK to my server using the IPv4 address.

Would it be possible to get MeshAgent to use IPv4 instead of IPv6 if there was a problem using IPv6?

I know the error is something on the PC and not MeshAgent, but it would be nice if I could use MeshCentral to connect to that PC to fix the problem :)

Nov 01 '21 13:11 af7567

Interesting. I'll have to look at how it resolves the DNS name, because I think I only captured the first entry. The agent already supports automatic failover to different URLs, so I should be able to populate both IPv4 and IPv6 addresses into the URL list, which should just work.

Dec 03 '21 19:12 krayon007