Thanks. I'll check out the references tomorrow. Right now it's 04:24 here The app I am writing is for a tablet to be connected to customers LAN designed to control an XP based machine named "Base". I have no control over their router settings. Nor can I rely on them having an active Internet connection, as opposed to merely a switched on LAN (WiFi)
On 23/03/2011, Bob Kerns <r...@acm.org> wrote: > By setting up your LAN properly. > > You will need: > > 1. Your LAN's DHCP server to know the proper location of your DNS server. > This is the DNS server your phone will use. > 2. Your DNS server to know the names addresses of your MS machines. DNS > is how your phone (and anything else even remotely standard) resolves > addresses. > 3. Your application to use the FQDN (Fully Qualified Domain Name, e.g. > myserver.mycompany.com) > > There are a number of approaches to doing this. I'll describe just the > simplest (in the sense of requiring the least technology and making the > fewest assumptions), not necessarily the easiest or best. > > 1. Assign a static IP address for your server. If you will only be > accessing it via LAN, it can be on the internal LAN IP address range, but > not one that is in use, or allocated to a DHCP address pool. > 2. Register that IP address with your DNS server for mycompany.com. You > want to add an 'A' record with the name (without the .mycompany.com) and > the > IP4 address. You may also want to add an IP6 address, using an AAAA > record, > if your network supports that. > 3. Make sure Constants.serverNameStr has the '.mycompany.com' on the end. > > Other approaches allow for setting it up and managing it dynamically, for > example, see this Microsoft article on integrating WINS and DNS: > > http://technet.microsoft.com/en-us/library/cc750589.aspx > > Or this one on Active Directory and DNS: > > http://technet.microsoft.com/en-us/library/cc759550(WS.10).aspx > > If you want to access it even if you're not on the LAN, you'll need a public > IP address, and suitable router configuration for your service to be > contacted on the proper machine, but it still boils down to the same > process. > > Note that you can have an internal DNS server with data that is not public. > Your phone (and any device using DHCP) will get the address of the DNS > server to use for resolving host names from the response from your DHCP > server. However, this isn't necessary for successful use. > > -- Homepage: www.neopax.com/technomage - My new book -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
