TSNet error 6
J. Landman Gay
jacque at hyperactivesw.com
Fri Sep 1 16:41:52 EDT 2017
This is for an Android app that can be run from anywhere, so I don't
have control over the routers or servers. (And yeah, I didn't quite get
everything you were talking about, I'm a network novice.)
The apps run fine for most people and only get this error with a few
users. I think you're basically saying there's no cure, right?
If the web site has a static IP and the Android app uses that instead of
a domain name, will that fix it? The app is communicating with a
database on the web server.
On 9/1/17 12:12 PM, Bob Sneidar via use-livecode wrote:
> That is a DNS error. If referring to a host, you can use the NetBIOS name locally, the FQDN locally or remotely, or the IP number (which might change so that is always a bad idea).
> Now if the host name is NetBIOS, a number of things can go wrong in a non-domain environment. With a domain server acting as your local DNS, it will resolve NetBIOS names to their FQDN equivalents via the WINS service. Barring that, NetBIOS name resolution falls back on an election process, where some windows computer is elected as the Master Browser, which is then responsible for tracing all devices on the network and their current IP addresses.
> If it happens to be a regular workstation, and it is set to go to sleep after a certain amount of time, well another device has to become the master browser, and it won't know about the server in question until it requests the current master browser and it might not do that for some time. See the problem?
> So there are a couple ways around that. First you can configure the local router with a static DNS entry, and make sure the primary DNS server listed is that router. Alternately you can edit the hosts file on each workstatino and make a static entry there. The latter is probably going to be the most reliable, but starting with windows 7 I think that file is locked, so it requires elevated privileges.
> Sucks huh? The best thing is to have a real DNS server locally (every router these days does this but not everyone configures their routers correctly) and then via the command line you *should* be able to register with the DNS server, but I'm not sure how.
> Hope that is not too much.
> Bob S
>> On Sep 1, 2017, at 09:40 , J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
>> I have two apps that normally work fine but in both an occasional user will get an error "TSNeterr : (6) could not resolve host". What would be the cause of this sporadic problem? We're not sure what to tell these users.
>> Jacqueline Landman Gay | jacque at hyperactivesw.com
>> HyperActive Software | http://www.hyperactivesw.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the Use-livecode