Re: Android LAN access problem
On Mar 21, 2:17 pm, Dirk Bruere at NeoPax <dirk.bru...@gmail.com>
wrote:
On 21/03/2011 17:53, Steve Sobol wrote:
In article<8upcurFin...@mid.individual.net>, Dirk Bruere at NeoPax
says...
No.
You fix your DNS.
And every potential client's DNS?
If you expect "hostname" to always be resolvable - just "hostname" - yo=
u
(a) don't understand how DNS works, and (b) are setting yourself up for
disappointment.
If you want to make Android play nice with WINDOWS NETWORKING/NETBIOS,
use CIFS.
If you want your Android device to do NetBIOS-style name resolution
(which, by the way, is a Microsoft invention), use CIFS.
CIFS works on Windows, it works on Linux, and there is no reason it
shouldn't work on Android (as far as I know).
I don't see why this is so hard to understand. And you keep on
complaining, and it's been at least a week or two since I offered a
solution.
I know - I'm looking at jcifs
This is NOT AN ANDROID PROBLEM.
This is NOT A JAVA PROBLEM.
I would say that it *is* an Android problem if they want to interface
easily with home networks.
Otherwise I would not be having to find add-on packages to do what their
SDK cannot.
Muammar Qaddafi requires his people to live in poverty and
oppression. They don't want to, but they need an add-on package of
U.N. air support to fulfill their goals. This is not their fault; the
Qaddafi/Microsoft hegemony has caused the environment, not the
peaceful Java/Android/Libyan common folk.
What do you care whose fault it is? You've had the answer for weeks.
Microsoft doesn't follow the standard the rest of the world uses; you
need a library to interact with their proprietary interface. The
library exists, it's readily available and it's free of charge. BFD.
Why does that bother you so much?
Chill the frak out.
--
Lew