C125 Windows 10 Connection Problems
Posted: Sat Jan 04, 2020 12:17 pm
I have had intermittent connection problems with windows 10 and a C125 display for a while now. When the software was unable to find the device I would have to uninstall the dash software and re-install it to be able to connect to the dash. I tried turning off the firewall/AV/VPN connections but it has not helped.
Looking at an older forum post it mentioned the connection log which i dug up. In it there are a few lines which are below that look to be a problemwith the connection to the dash
Fri Jan 3 17:03:18 2020: Registering new address record for 169.254.213.51 on Ethernet 2.IPv4.
Fri Jan 3 17:03:21 2020: Received record with bad TTL [Racecraft.local IN A 169.254.213.51 ; ttl=60]. Refreshing.
Fri Jan 3 17:03:21 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:03:22 2020: Received record with bad TTL [Racecraft.local IN A 169.254.213.51 ; ttl=60]. Refreshing.
Fri Jan 3 17:03:22 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:10:09 2020: Interface Ethernet 2.IPv4 no longer relevant for mDNS.
Fri Jan 3 17:10:09 2020: Leaving mDNS multicast group on interface Ethernet 2.IPv4 with address 169.254.213.51.
Fri Jan 3 17:10:09 2020: Withdrawing address record for 169.254.213.51 on Ethernet 2.
Fri Jan 3 17:10:09 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:10:12 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:10:12 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Any suggestions as to what would be causing this and how to correct it?
Thanks in advance
Looking at an older forum post it mentioned the connection log which i dug up. In it there are a few lines which are below that look to be a problemwith the connection to the dash
Fri Jan 3 17:03:18 2020: Registering new address record for 169.254.213.51 on Ethernet 2.IPv4.
Fri Jan 3 17:03:21 2020: Received record with bad TTL [Racecraft.local IN A 169.254.213.51 ; ttl=60]. Refreshing.
Fri Jan 3 17:03:21 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:03:22 2020: Received record with bad TTL [Racecraft.local IN A 169.254.213.51 ; ttl=60]. Refreshing.
Fri Jan 3 17:03:22 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:10:09 2020: Interface Ethernet 2.IPv4 no longer relevant for mDNS.
Fri Jan 3 17:10:09 2020: Leaving mDNS multicast group on interface Ethernet 2.IPv4 with address 169.254.213.51.
Fri Jan 3 17:10:09 2020: Withdrawing address record for 169.254.213.51 on Ethernet 2.
Fri Jan 3 17:10:09 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:10:12 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Fri Jan 3 17:10:12 2020: Received record with bad TTL [Racecraft.local IN A 192.168.1.163 ; ttl=60]. Refreshing.
Any suggestions as to what would be causing this and how to correct it?
Thanks in advance