Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
End Users
Pocket PCActiveSyncMultimediaEBooksWirelessSmartPhones
Developers
Windows MobileSmartPhonesWinCE ProgrammingVB for WinCEVC++ for WinCEPlatform BuilderTest Tools
PocketPC DirectoryFree SoftwareWeb Resources
Related Topics
PalmMobile PhonesMore Topics ...

Pocket PC Forum / End Users / Pocket PC / July 2008

Tip: Looking for answers? Try searching our database.

iPAQ 4350 not resolving names with DNS

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
no_spam_paquette@uwo.ca - 24 Jul 2008 13:34 GMT
My wife has a legacy iPAQ 4350 running Windows for Pocket PC 2003.
Its networking card seemed to be working normally and DNS resolution
was working until yesterday.  Yesterday morning I changed my router
arrangement to accommodate a machine running N protocol WiFi
encryption.  Basically I added a second router configured as a passive
switch (with its own WEP-encrypted wireless network) and reset my main
router as a separate WPA2 encrypted network.  This all works fine.  My
single N-protocol machine is happy on its network and my Pocket PC as
well as a legacy laptop are happy on the WEP network.  My wife's
legacy iPAQ 4350, however, doesn't seem to be connecting to DNS.  I've
double checked several times and the iPAQ wireless card DNS IP is
definitely set to the same IP as the other WEP-network devices, namely
the IP of the WEP-network router (both routers being configured for
DNS pass-through).

I have tried removing the battery from the iPAQ and running the
“welcome" utility to reset things but no luck.  The iPAQ absolutely
refuses to connect to any website.  IE keeps complaining that “The
page you are looking for cannot be found.”

I have actually seen this behavior in the past with the iPAQ in
question but have usually been able to make it go away by removing the
battery and running the “welcome” utility.  No such luck this time
though!

Does anyone have any idea how to fix this problem?

Thanks in advance for any help!
no_spam_paquette@uwo.ca - 24 Jul 2008 13:36 GMT
On Jul 24, 8:34 am, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> wrote:
> My wife has a legacy iPAQ 4350 running Windows for Pocket PC 2003.
> Its networking card seemed to be working normally and DNS resolution
[quoted text clipped - 24 lines]
>
> Thanks in advance for any help!

PS—VPN does connect on the iPAQ, however, so I know I have a working
WiFi connectionon it.
Beverly Howard [Ms-MVP/MobileDev] - 24 Jul 2008 21:41 GMT
Suggest downloading and running vxUtil and vxIPConfig from http://cam.com

These will show the dns ip address if one exists and allow you to ping
it and determine if it is responding.

Tip on vxUtil... there are entries for all possible connection options,
so you will need to spot the currently active connection... (not hard)

Beverly Howard [MS MVP-Mobile Devices]
no_spam_paquette@uwo.ca - 24 Jul 2008 23:34 GMT
On Jul 24, 4:41 pm, "Beverly Howard [Ms-MVP/MobileDev]"
<BevNoSpamBevHoward.com> wrote:
> Suggest downloading and running vxUtil and vxIPConfig fromhttp://cam.com
>
[quoted text clipped - 5 lines]
>
> Beverly Howard [MS MVP-Mobile Devices]

Thank you for the reply!

When I ping with them both vxUtil and Z2PocketLan show reply packets
from the IP address for the “passive switch” router on which I am
running the 811g wireless network.  Both routers are set to allow DNS
relay and three other machines including one Pocket PC (Windows Mobile
5 though) are working just fine with the saying 811g wireless network.

For some reason, however, on the Windows Mobile 2003 Pocket PC, DNS
lookup fails.  All four machines are configured  identically in that
the DNS address for the adapter cards is set to the IP address of the
“passive switch” router on which the 811.G wireless network is
running.

I am completely a loss to explain why this is happening!
Beverly Howard [Ms-MVP/MobileDev] - 25 Jul 2008 01:16 GMT
using vxUtil's ping, what happens when you ping a "verbose" address such
as "yahoo.com" ?

Next clue, when you ping "yahoo.com" with a working pc, jot down the ip
address from that ping, and report what happens when you use vxUtil to
ping yahoo's ip address.

Beverly Howard [MS MVP-Mobile Devices]
no_spam_paquette@uwo.ca - 25 Jul 2008 13:14 GMT
On Jul 24, 8:16 pm, "Beverly Howard [Ms-MVP/MobileDev]"
<BevNoSpamBevHoward.com> wrote:
> using vxUtil's ping, what happens when you ping a "verbose" address such
> as "yahoo.com" ?
[quoted text clipped - 4 lines]
>
> Beverly Howard [MS MVP-Mobile Devices]

First, thanks again!

I get packets back with no problem.  Of course, if I try "Get HTML"
for http://www.yahoo.com I get a "Could not get IP address" error.
This is definitely a DNS lookup problem but I just don't see what's
going on.
Beverly Howard [Ms-MVP/MobileDev] - 26 Jul 2008 01:19 GMT
rather than "get html, simply enter "yahoo.com" in the ping address
field... I expect a timeout, but want to confirm.

My focus would be back on the dhcp... first, would confirm that ip
address is really on automatic and the base ip address that the unit has
 really come from the router.

Next, copy the dns address that the router itself shows and ping that
directly... there's always the possibility that the pc's have gotten
fixed or alternate dns entries.

Open the router utility on a pc and confirm that the ppc shows up as an
attached device and make sure it's mac is not in the router's fixed ip
table.

for our edification, copy the entire ip info page while connected and
post that here (edit out anything sensitive) look for something
subtle... like an alternate device with almost the same settings or an
address with an "0" rather than a "1"

Finally, you can resolve this using a fixed ip address approach by
entering a high base ip and then going directly to your desired dns server.

Beverly Howard [MS MVP-Mobile Devices]
no_spam_paquette@uwo.ca - 28 Jul 2008 14:46 GMT
On Jul 25, 8:19 pm, "Beverly Howard [Ms-MVP/MobileDev]"
<BevNoSpamBevHoward.com> wrote:
> rather than "get html, simply enter "yahoo.com" in the ping address
> field... I expect a timeout, but want to confirm.
>
> My focus would be back on the dhcp... first, would confirm that ip
> address is really on automatic

Yes--on "Use server-assigned IP address!"

and the base ip address that the unit has
>   really come from the router.

The address is 192.168.0.104 which is within the main router's (a
second router is configured as a passive switch) ip number pool.

> Next, copy the dns address that the router itself shows and ping that
> directly... there's always the possibility that the pc's have gotten
> fixed or alternate dns entries.

The router that I am using as a passive switch to connect to 11g
machines does not display the IP number, only connect time, Mac
address, and mode.  It is clear, however, from connect time and Mac
address that the router in question is “passing through” an IP
assignment to my wife's Pocket PC.  Furthermore, I can ping that
Pocket PC from other machines on the network at that IP number
(192.168.0.104).  The “main” router, the one that is actually
assigning DHCP addresses, does report my wife's Pocket PC name and Mac
address at 192.168.0.104.

> Open the router utility on a pc and confirm that the ppc shows up as an
> attached device and make sure it's mac is not in the router's fixed ip
> table.

There is only one reserved fixed address on the “underlying” router
(the one actually assigning DHCP addresses).  That is the address used
by my main work machine for which I require a fixed address.  I have
verified this visually by checking directly in the DHCP reservations
list on the underlying router.

> for our edification, copy the entire ip info page while connected and
> post that here (edit out anything sensitive) look for something
> subtle... like an alternate device with almost the same settings or an
> address with an "0" rather than a "1"

Time : Thursday, July 01, 2004 6:01:50 PM
Firmware Version : 1.09,    2006/10/23

WAN

Connection Type : PPPoE
Cable Status : Connected
Network Status : Established
Connection Up Time : 4 day(s), 16:17:17

MAC Address : 00:17:9A:48:43:90
Authentication & Security : PAP
IP Address : 74.xx.xx.xxx
Subnet Mask : 255.255.255.255
Default Gateway : xx.xxx.xxx.xx
Primary DNS Server : 204.101.251.1
Secondary DNS Server : 204.101.251.2
BigPond Server Name :
BigPond Status : Unknown (Please wait...)

LAN

MAC Address : xx:xx:xx:xx:xx:
IP Address : 192.168.0.1
Subnet Mask : 255.255.255.0
DHCP Server : Enabled

Wireless LAN

Wireless Radio : On
MAC Address : xx:xx:xx:xx:xx:xx
Network Name (SSID) : SSIDName
Channel : 6
Security Type : WPA-Personal

LAN Computers

IP Address Name (if any) MAC
192.168.0.100 MainMachine 00:16:76:c7:dd:45
192.168.0.104 WINDOWSMOBILE6 00:0f:20:80:c7:e3
192.168.0.147 Other machine(n) 00:17:9a:4c:9d:ee
192.168.0.150 2OtherMachine 00:04:23:5f:b6:0a
192.168.0.187 WINDOWSMOBILE67 00:09:2d:94:b1:03

IGMP Multicast memberships

Hmm-- yes there is definitely something suspicious here.  First, I
have been wondering how this legacy Pocket PC got remained
WINDOWSMOBILE6 since that is not the name that we assigned to it.
Second, I have no idea where the second entry, that is, the
WINDOWSMOBILE67 entry came from—furthermore, the Mac number doesn't
correspond to anything I know of.  I wonder if I should simply try
renaming the Pocket PC to its original name before I try assigning a
fixed IP number you suggest in the next paragraph.

 What do you think?

Again thanks so much for sticking with this!  Very much appreciated
indeed!

> Finally, you can resolve this using a fixed ip address approach by
> entering a high base ip and then going directly to your desired dns server.

Probably not, if I understand you correctly here.  The reason for
adding the second (“passive switch” router) was that I needed to
operate one wireless machine on 11n yet be able to continue to operate
several legacy machines on 11g.  That meant I was stuck with having
one router  providing WPA encryption and another providing WEP.

> Beverly Howard [MS MVP-Mobile Devices]
no_spam_paquette@uwo.ca - 28 Jul 2008 22:36 GMT
On Jul 28, 9:46 am, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> wrote:
> On Jul 25, 8:19 pm, "Beverly Howard [Ms-MVP/MobileDev]"
>
[quoted text clipped - 113 lines]
>
> > Beverly Howard [MS MVP-Mobile Devices]

PS--Tried fixed address--no luck on that either!
no_spam_paquette@uwo.ca - 28 Jul 2008 22:58 GMT
On Jul 28, 9:46 am, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> wrote:
> On Jul 25, 8:19 pm, "Beverly Howard [Ms-MVP/MobileDev]"
>
[quoted text clipped - 113 lines]
>
> > Beverly Howard [MS MVP-Mobile Devices]

PS--Tried fixed address--no luck on that either!
no_spam_paquette@uwo.ca - 28 Jul 2008 23:20 GMT
On Jul 28, 9:46 am, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> wrote:
> On Jul 25, 8:19 pm, "Beverly Howard [Ms-MVP/MobileDev]"
>
[quoted text clipped - 113 lines]
>
> > Beverly Howard [MS MVP-Mobile Devices]

PS--Tried fixed address--no luck on that either!
Beverly Howard [Ms-MVP/MobileDev] - 28 Jul 2008 23:48 GMT
essentially, I'm lost...

the only remaining observation I have is the pppoe entry... if either
the main or "passthrough" assumes the ppc has a pppoe client, that would
stop things cold... for any ppc setup, the router should be the only
pppoe login to the service and providing non pppoe connections to
everything behind it.

If your ppc is named differently than the router table shows, that's
also a red flag.

Beverly Howard [MS MVP-Mobile Devices]
no_spam_paquette@uwo.ca - 29 Jul 2008 00:06 GMT
On Jul 28, 6:48 pm, "Beverly Howard [Ms-MVP/MobileDev]"
<BevNoSpamBevHoward.com> wrote:
> essentially, I'm lost...
>
> the only remaining observation I have is the pppoe entry... if either
> the main or "passthrough" assumes the ppc has a pppoe client,

No--not as far as I can tell!

that would
> stop things cold... for any ppc setup, the router should be the only
> pppoe login to the service and providing non pppoe connections to
> everything behind it.

I believe that to be the case.  The only device configured for pppoe
is the main router.

> If your ppc is named differently than the router table shows, that's
> also a red flag.

Actually, I changed the name back to the former name but it got
changed back to yet another name (in the main router wireless table)--
this time WindowsMobile97 right after doing an ActiveSync sync
session.

Thanks for all the help--I'll post here if I ever get to the bottom of
this.

> Beverly Howard [MS MVP-Mobile Devices]
no_spam_paquette@uwo.ca - 29 Jul 2008 01:46 GMT
On Jul 28, 6:48 pm, "Beverly Howard [Ms-MVP/MobileDev]"
<BevNoSpamBevHoward.com> wrote:
> essentially, I'm lost...
>
> the only remaining observation I have is the pppoe entry... if either
> the main or "passthrough" assumes the ppc has a pppoe client,

No--not as far as I can tell!

that would
> stop things cold... for any ppc setup, the router should be the only
> pppoe login to the service and providing non pppoe connections to
> everything behind it.

I believe that to be the case.  The only device configured for pppoe
is the main router.

> If your ppc is named differently than the router table shows, that's
> also a red flag.

Actually, I changed the name back to the former name but it got
changed back to yet another name (in the main router wireless table)--
this time WindowsMobile97 right after doing an ActiveSync sync
session.

Thanks for all the help--I'll post here if I ever get to the bottom of
this.

> Beverly Howard [MS MVP-Mobile Devices]
no_spam_paquette@uwo.ca - 29 Jul 2008 12:43 GMT
On Jul 28, 8:46 pm, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> wrote:
> On Jul 28, 6:48 pm, "Beverly Howard [Ms-MVP/MobileDev]"
>
[quoted text clipped - 27 lines]
>
> > Beverly Howard [MS MVP-Mobile Devices]

I'm now inclined to believe that a failing WiFi board on the
motherboard of the PPC has coincidently picked this time to go
permanently flaky.  I've already had to replace the motherboard once
on the iPAQ 4350 in question because of WiFi failure and I see that
loads of other people have had problems with the WiFi circuitry on
that particular board (the WiFi board seems to last only about two
years).  It was starting to become erratic long before I added the
second router.  The “smoking gun” appeared early this morning while I
was experimenting with 64-bit instead of 128-bit encryption to see if
that would make any difference.  During that process DNS lookup worked
once, but only once so I think I'm dealing with a failed WiFi board
again.

Thanks again for your help!
no_spam_paquette@uwo.ca - 29 Jul 2008 13:25 GMT
On Jul 28, 8:46 pm, "no_spam_paque...@uwo.ca" <paque...@uwo.ca> wrote:
> On Jul 28, 6:48 pm, "Beverly Howard [Ms-MVP/MobileDev]"
>
[quoted text clipped - 27 lines]
>
> > Beverly Howard [MS MVP-Mobile Devices]

I'm now inclined to believe that a failing WiFi board on the
motherboard of the PPC has coincidently picked this time to go
permanently flaky.  I've already had to replace the motherboard once
on the iPAQ 4350 in question because of WiFi failure and I see that
loads of other people have had problems with the WiFi circuitry on
that particular board (the WiFi board seems to last only about two
years).  It was starting to become erratic long before I added the
second router.  The “smoking gun” appeared early this morning while I
was experimenting with 64-bit instead of 128-bit encryption to see if
that would make any difference.  During that process DNS lookup worked
once, but only once so I think I'm dealing with a failed WiFi board
again.

Thanks again for your help!
Beverly Howard [Ms-MVP/MobileDev] - 29 Jul 2008 16:45 GMT
Glad you are headed toward resolution.

fyi, are you aware that a number of your posts are being posted multiple
times?

Since you are posting via google groups, is there a chance that you are
reposting my multiple clicks on their send button?

Thanks,
Beverly Howard [MS MVP-Mobile Devices]
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.