Pocket PC (iPaq 4350) fails to make wireless connection even after replacing motherboard!
- From: "no_spam_paquette@xxxxxx" <paquette@xxxxxx>
- Date: Mon, 29 Sep 2008 15:29:17 -0700 (PDT)
My wife has a legacy iPaq 4350 that she likes to use around the house
for various things. Some time ago it began having increasing problems
making WiFi connections. Now it never connects. Initially I thought
this was a DNS problem but I now realize that it is a problem making
any connection at all (even a connection from an IP number rather than
from a fully qualified domain name). Another Pocket PC device (albeit
a Windows Mobile 5 rather than Windows 2003 device) and a laptop—in
fact occasionally several laptops—work just fine from the same access
point. I recently bought a new motherboard for the 4350 on the
assumption that the problem was with the WiFi circuitry on the
motherboard. To my surprise the problem continued even after switching
the motherboard.
I have tried every possible configuration change to the network
settings on the 4350 with no luck. Here is what I do know after
spending some time using z2PocketLan and a couple of other diagnostic
utilities to study the connection of the WM5 device and the attempts
to connect of the 4350.
1. The 4350 never actually makes a connection For instance the z2
report of the WM5 device includes much evidence of sending and
receiving such as below:
Active opens: 4532
Passive opens: 0
Failed connection attempts: 4518
Established connections reset: 2
Established connections: 2
Segments received: 22663
Segment sent: 9256
Segments retransmitted: 13554
Incoming errors: 0
Outgoing resets: 4098
Cumulative connections: 2
The z2 report for the 4350, however, shows no evidence of connection
or sending and receiving as shown below:
Active opens: 0
Passive opens: 0
Failed connection attempts: 0
Established connections reset: 0
Established connections: 0
Segments received: 0
Segment sent: 0
Segments retransmitted: 0
Incoming errors: 0
Outgoing resets: 0
Cumulative connections: 0
2. Trace-route to anywhere on the 4350 makes about a dozen hops and
then times out.
3. A z2 ip scan of the (working) WM5 device reports as follows:
Scan Network Report
12:38:13 09/29/2008
-z2 PocketLAN v4.01/8
Host Name: localhost
IP Address: 192.168.0.187
Mac Address: 00-09-2D-94-B1-03
INC Vendor: High Tech Computer
Group Name: ?Unknown
TCP port open: Not found2/8
Host Name: XXXXXX _HOME
IP Address: 192.168.0.190
Mac Address: 00-17-9A-4C-9D-EE
INC Vendor: D Link
Group Name: HOMENET
TCP port open: 5
TCP port open list:
25 (smtp); 135 (msrpc); 139 (netbios-ssn); 445 (microsoft-ds); 990
(ftps);3/8
Host Name: WINDOWSMOBILE97
IP Address: 192.168.0.194
Mac Address: 00-0E-7F-76-C4-77
INC Vendor: Hewlett Packard
Group Name: ?Unknown
TCP port open: Not found4/8
Host Name: XXXXXX_NOTE
IP Address: 192.168.0.150
Mac Address: 00-04-23-5F-B6-0A
INC Vendor: Intel
Group Name: HOMENET
TCP port open: 4
TCP port open list:
135 (msrpc); 445 (microsoft-ds); 139 (netbios-ssn); 990 (ftps);5/8
Host Name: WINDOWSMOBILE67
IP Address: 192.168.0.255
Mac Address:
INC Vendor:
Group Name: ?Unknown
TCP port open: Not found6/8
Host Name: XXXXXX 2
IP Address: 192.168.0.100
Mac Address: 00-16-76-C7-DD-45
INC Vendor: Intel
Group Name: HOMENET
TCP port open: Not found7/8
Host Name: ?Unknown
IP Address: 192.168.0.200
Mac Address: 00-1E-58-3B-4B-7B
INC Vendor:
Group Name: ?Unknown
TCP port open: Not found8/8
Host Name: ?Unknown
IP Address: 192.168.0.1
Mac Address: 00-17-9A-48-43-8F
INC Vendor: D Link
Group Name: ?Unknown
TCP port open: Not found
while an IP scan of the 4350 yields the following report:
Host Name: WINDOWSMOBILE97
IP Address: 192.168.0.194
Mac Address: 00-0E-7F-76-C4-77
INC Vendor: Hewlett Packard
Group Name: ?Unknown
Host Name: XXXXXX _HOME
IP Address: 192.168.0.190
Mac Address: 00-17-9A-4C-9D-EE
INC Vendor: D Link
Group Name: 192.168.0.190
Host Name: XXXXXX _NOTE
IP Address: 192.168.0.150
Mac Address: 00-04-23-5F-B6-0A
INC Vendor: Intel
Group Name: 192.168.0.150
Host Name: WINDOWSMOBILE97
IP Address: 192.168.0.255
Mac Address:
INC Vendor:
Group Name: ?Unknown
Host Name: XXXXXX 2
IP Address: 192.168.0.100
Mac Address: 00-16-76-C7-DD-45
INC Vendor: Intel
Group Name: 192.168.0.100
Host Name: ?Unknown
IP Address: 192.168.0.200
Mac Address: 00-1E-58-3B-4B-7B
INC Vendor:
Group Name: ?Unknown
Host Name: ?Unknown
IP Address: 192.168.0.1
Mac Address: 00-17-9A-48-43-8F
INC Vendor: D Link
Group Name: ?Unknown
An obvious difference is that the working WM5 device assigns the IP
number assigned to the device by the router/access point to
"localhost" while the 4350 assigns the IP number that it gets from the
router/access point to WINDOWSMOBILE97 (these WINDOWSMOBILE host names
are evidently provided by Windows Mobile Device Center (version 6.1)
running under Vista). The 4350 also assigns 192.168.0.255 to the same
host name (WINDOWSMOBILE97) while the WM5 device assigns its router/
access point-assigned IP number, 192.168.0.194 to WINDOWSMOBILE97 but
assigns 192.168.0.255 to WINDOWSMOBILE67—a hostname also apparently
assigned by Windows Mobile Device Center. Perhaps I am seriously
misguided here but it looks to me as if the 4350 has two different IP
numbers assigned to hostname WINDOWSMOBILE97 which seems, on the face
of it, like a pretty bad idea.
Perhaps I am going down a blind alley here in which case I would
greatly appreciate any further suggestions for diagnosis. If I have in
fact tumbled on the cause of this very persistent connection problem,
the question then becomes what can I do about it—if even replacing the
motherboard doesn't get rid of it (of course, after updating the ROM
and LAN driver on the new motherboard, I did a system restore on the
4350 from an image I had made just before the motherboard
replacement).
Any help would be gratefully appreciated!
.
- Prev by Date: Re: how to convert bitmap to png or jpeg ?
- Next by Date: WM5 Won't Retain Default Input Method Setting
- Previous by thread: Delete locked contacts?
- Next by thread: WM5 Won't Retain Default Input Method Setting
- Index(es):
Relevant Pages
|
