Windows Mobile 6.5 Cross-Subnet Name Resolution
In Windows Mobile 6.5, resolving hostnames across different local subnets required mechanisms that could bypass the boundary limitations of local broadcast domains. Because standard broadcast-based resolution cannot cross routers, the operating system relied on unicast network services and static configuration files. Specifically, Windows Mobile 6.5 utilized the Domain Name System (DNS), Windows Internet Name Service (WINS), and local HOSTS or LMHOSTS text files to achieve cross-subnet hostname resolution.
Domain Name System (DNS)
The primary and most robust mechanism for resolving hostnames across subnets in Windows Mobile 6.5 was DNS. When a device needed to resolve a fully qualified domain name (FQDN) or an unqualified single-label name configured with a DNS suffix, it sent direct unicast UDP queries to the configured DNS server. Because DNS operates via routed unicast traffic rather than broadcasts, queries seamlessly traversed routers, switches, and remote subnets. DNS server addresses were typically assigned automatically via DHCP during network connection establishment (such as Wi-Fi or cellular connections) or configured manually in the adapter settings.
Windows Internet Name Service (WINS)
For legacy NetBIOS computer names, Windows Mobile 6.5 used WINS to resolve names across subnets. While basic NetBIOS name resolution relies on link-local broadcasts (b-node) that cannot cross subnet boundaries, WINS functions as a centralized NetBIOS Name Server (NBNS). When configured as a p-node (point-to-point) or h-node (hybrid), Windows Mobile 6.5 directed unicast NetBIOS name query packets directly to the WINS server's IP address. This design enabled devices to discover Windows shares, servers, and other NetBIOS resources located on separate corporate subnets. WINS addresses could be populated through DHCP option 44 or specified within custom network configurations.
Static Mapping Files (HOSTS and LMHOSTS)
Windows Mobile 6.5 supported static lookup tables stored in the local
file system, typically placed within the \Windows
directory:
- HOSTS File: A flat text file mapping IP addresses directly to hostnames and domain names. When an application initiated a socket connection, the system would query the local HOSTS file before or alongside querying DNS servers, allowing direct cross-subnet IP routing without requiring server infrastructure.
- LMHOSTS File: Used to map IP addresses to NetBIOS computer names. Similar to desktop Windows environments, this file allowed Windows Mobile to resolve remote NetBIOS systems across subnets when a WINS server was either unavailable or unreachable.
Limitations of Local Broadcasts
Standard broadcast-based resolution protocols, such as basic NetBIOS name queries and local-link broadcasts, were restricted to the originating subnet because network routers routinely drop directed and non-directed broadcast packets. Unless network administrators configured IP helper addresses or DHCP/BOOTP relay agents on the intermediate routing hardware, Windows Mobile 6.5 strictly depended on the unicast routing of DNS, WINS, or local static files to locate systems on other subnets.