TSNet error 6

Ralph DiMola rdimola at evergreeninfo.net
Sat Sep 2 09:39:47 EDT 2017


I would zero in on the https thing. If the user can get to an https web-site via Safari/Chrome on the same server as your DB then tsNet should work unless there is a bug in tsNet. The slack also problem has me concerned with the router. If we eliminate the tin-foil-hat possibilities then could there be a router issue in the coffee shop? Does this happen with other users in other places? I've seen routers do some strange things until a re-boot. The age of the router(or a pending firmware update) could also be in play. It's just so hard when you have no/zero/nada control over network connectivity.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net


-----Original Message-----
From: J. Landman Gay [mailto:jlandmangay at gmail.com] On Behalf Of J. Landman Gay
Sent: Friday, September 01, 2017 11:21 PM
To: rdimola at evergreeninfo.net
Subject: Re: TSNet error 6

In today's episode, the user was in a coffee house using the free wifi (it was one of my testers, there on purpose for testing). The app could not resolve the host though the connection would have been constant. 
When he tests from his own home everything works, as it does for all of us on the team.

We're wondering if https has anything to do with it. He could connect to anything with Chrome but both my app and Slack would not work using https. Could that be a factor?

We need to keep testing to see if https is really the cause, we're not quite sure yet.

On 9/1/17 4:10 PM, Ralph DiMola wrote:
> J,
> 
> I have run into many network issues on mobile. The chance that the 
> user might have a weak cell/wifi signal, move from cellular==>wifi or 
> wifi==>cellular is higher than one would think. This would be my first 
> guess. I always ask the user if Safari/Chrome is serving up pages. 99% 
> of the time network funnies are caused by weak/changing network 
> access. The amount of error checking and combinations thereof has been very challenging.
> The first thing I do before any network access is to ping my server 
> with a https request to a LC backend server script that returns "OK". 
> I set the timeout for 2 seconds. If the returned data is not "OK" or 
> take more than 2 seconds then I put the app into off-line mode. I try 
> to ping the server every time the users does "x" or the user's action 
> again need network access and see if the network is back online or fast enough.
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdimola at evergreeninfo.net
> 
> -----Original Message-----
> From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On 
> Behalf Of J. Landman Gay via use-livecode
> Sent: Friday, September 01, 2017 4:42 PM
> To: Bob Sneidar via use-livecode
> Cc: J. Landman Gay
> Subject: Re: TSNet error 6
> 
> 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:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
> 
> 


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com





More information about the Use-livecode mailing list