Forum Discussion
Android Galaxy XCover 7 problems with .local adress
Hello
we are facing a problem some of our Samsung Galaxy XCover 7 devices
can only resolve an internal server with a .local address very slowly.
This means that we cannot use the resource, as high latency leads to the connection being terminated.
We use our own DNS server which comes with DHCP. If I change the DNS server manually using an app, but to the same DNS server that also comes with DHCP, we can reach the address without any problems and without long latency. (This happens over a VPN tunnel to the dns server)
Does anyone have ideas?
4 Replies
Hi there,
Sounds like a mismatch with a configuration on the device. What are you using to set up the VPN and are you pushing any other policies to the devices?
What MDM are you using and are you using Knox Service plugin as well?
Hi Michel,
we dont use VPN, its an app where you can configure a DNS Server and then the App automatically starts a vpn connection.
We are sending a bunch of policies to the device: WiFi Cert. Config, Restrictions, Knox Plugin
MDM is Intune and yes the KSP is also on the device.
But we dont changed a configuration for the devices before last week it was all fine.
You could try to set the KSP app in debug mode (be aware that it will launch on all phones when you do that) and see if it is returning some errors.
Since it used to work, are the devices on a different firmware than the ones who do work? If so, you might want to log a ticket with Samsung via your Samsung Knox account. Their support is usually pretty fast and good.
If using Knox Asset intelligence, be sure to pull a device log and add it to your ticket.
