>> I'm trying to get the IP address of a named computer in my local network.
>
[quoted text clipped - 5 lines]
> other computers on my LAN by name when the IP is server-assigned since the
> numbers are all the same anyway?
> DNS isn't one of those three numbers! The DNS server address is probably
> not being sent by your DHCP server but may be set statically for the
> adapter. So, when you use static addressing, you get the address from the
> registry, which is right, and when you use dynamic addressing, you don't get
> the DNS server address, so it doesn't work. At least, that's my first
> guess...
Yeah, there's a separate tab for name servers (DNS, Alt DNS, WINS, Alt
WINS) which are all blank. A blank DNS appears to be the key here
because when I look in my Axim registry here:
HKLM\Comm\ODIM\TIACXWLN1\Parms\TCPIP
I have the following settings when using a server-assign IP:
DhcpDefaultGateway = 192.168.1.1
DhcpIPAddress = 192.168.1.2
DhcpDNS = 24.93.41.125
DefaultGateway = 0.0.0.0
IpAddress = 0.0.0.0
DNS = (blank)
When I use a static IP, the DefaultGateway and IpAddress get filled in
but the DNS stays blank. So the culprit must be the DhcpDNS value. That
24.93.41.125 number is owned by my ISP and is being fed by my LinkSys
router. And of course my ISP's DNS isn't going to know about the PCs on
my internal LAN.
So is this fixable? I need the Axim to be able to see the outside world
and the other PCs in my LAN without having to use a static IP. I tried
just blanking out the DhcpDNS value in the registry but it had no
immediate affect and was reset when the connection was reset, as expected.

Signature
Kent Briggs, kbriggs@spamcop.net
Briggs Softworks, http://www.briggsoft.com
Paul G. Tobey [eMVP] - 28 Jul 2006 16:58 GMT
Work-aroundable, maybe. I'm not sure what method is being used when the DNS
server list is empty. The only real fix I can see is to *have* a DNS server
on your local network that *does* know the name to IP mapping. It's not
clear to me why it works in the blank case, but something undocumented is
happening under the covers, I think.
Paul T.
>> DNS isn't one of those three numbers! The DNS server address is probably
>> not being sent by your DHCP server but may be set statically for the
[quoted text clipped - 28 lines]
> just blanking out the DhcpDNS value in the registry but it had no
> immediate affect and was reset when the connection was reset, as expected.
Kent Briggs - 28 Jul 2006 17:19 GMT
> Work-aroundable, maybe. I'm not sure what method is being used when the DNS
> server list is empty. The only real fix I can see is to *have* a DNS server
> on your local network that *does* know the name to IP mapping. It's not
> clear to me why it works in the blank case, but something undocumented is
> happening under the covers, I think.
The problem with that is my particular application will only know the
SSID of the Wi-Fi network and the name of computer on that network to
which it is trying to fetch the IP. It won't know any IPs on the network
in advance except for what the Wi-Fi router is feeding it via DHCP.

Signature
Kent Briggs, kbriggs@spamcop.net
Briggs Softworks, http://www.briggsoft.com
Paul G. Tobey [eMVP] - 28 Jul 2006 17:33 GMT
The WiFi router should be able to be configured with the DNS server it
should pass to an DHCP clients it has. Alternatively, you should be able to
turn off DHCP on the WiFi router and just have it route DHCP requests to the
wired network it connects with, where you'd have a DHCP server on a desktop
or server machine running. That would *certainly* be able to be configured
with the right DNS server address and the server itself.
Paul T.
>> Work-aroundable, maybe. I'm not sure what method is being used when the
>> DNS server list is empty. The only real fix I can see is to *have* a DNS
[quoted text clipped - 6 lines]
> is trying to fetch the IP. It won't know any IPs on the network in advance
> except for what the Wi-Fi router is feeding it via DHCP.
Kent Briggs - 28 Jul 2006 19:01 GMT
> The WiFi router should be able to be configured with the DNS server it
> should pass to an DHCP clients it has. Alternatively, you should be able to
> turn off DHCP on the WiFi router and just have it route DHCP requests to the
> wired network it connects with, where you'd have a DHCP server on a desktop
> or server machine running. That would *certainly* be able to be configured
> with the right DNS server address and the server itself.
Unfortunately in my particular scenario, the Wi-Fi router (which is also
the internet gateway) may be owned by a third party where configuration
changes are not possible.

Signature
Kent Briggs, kbriggs@spamcop.net
Briggs Softworks, http://www.briggsoft.com
Paul G. Tobey [eMVP] - 28 Jul 2006 19:24 GMT
Then you'll have to resolve names by some means other than real DNS. I
don't know enough about .NET CF to really tell you what to try; you'll have
to browse the class library.
Paul T.
>> The WiFi router should be able to be configured with the DNS server it
>> should pass to an DHCP clients it has. Alternatively, you should be able
[quoted text clipped - 6 lines]
> the internet gateway) may be owned by a third party where configuration
> changes are not possible.