ActiveSync 3.8/WIFI

I'm having issues with ActiveSync over my WIFI connection.

I have a iPaq4705 connecting to my laptop's DLink WIFI card.

The laptop (192.168.10.98) can PING the iPaq both by IP address and name;
the iPaq (192.168.10.97) can PING the laptop by IP address and name. I can
even use the iPaq's file explorer to successfully connect to shares on the
laptop (over the WIFI connection).

After I have succesfully synch'ed the iPaq to the laptop via a USB cradle
connection, I cannot do the same sync over the WIFI connection mentioned
above.

An Ethereal packet capture reveals packets from the iPaq to the laptop with
"Port Destination Unreachable" for UDP ports 1900 & 53; but those are the
_only_ errors in the packet capture during the ActiveSync attempt.

Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990, 999,
5678, and 5679; although I don't see any of these packets in the Ethereal
capture.

So I'm rather confused as to what I'm seeing, and why the ActiveSync fails
over a known good WIFI connection.

Thanks in advance for any assistance.


================================================== ==================
C:\>nbtstat -c

Local Area Connection:

Node IpAddress: [144.158.52.170] Scope Id: []

No names in cache

Local Area Connection 2:

Node IpAddress: [192.168.10.98] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]

------------------------------------------------------------

HPIPAQ4705 <03> UNIQUE 192.168.10.97 -1

HPIPAQ4705 <00> UNIQUE 192.168.10.97 -1

HPIPAQ4705 <20> UNIQUE 192.168.10.97 -1

C:\>

C:\>netstat -an

Active Connections

Proto Local Address Foreign Address State

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1072 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1312 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1314 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1315 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1317 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1340 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1357 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1370 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1776 0.0.0.0:0 LISTENING

TCP 0.0.0.0:2701 0.0.0.0:0 LISTENING

TCP 0.0.0.0:2702 0.0.0.0:0 LISTENING

TCP 0.0.0.0:3612 0.0.0.0:0 LISTENING

TCP 0.0.0.0:3614 0.0.0.0:0 LISTENING

TCP 0.0.0.0:3615 0.0.0.0:0 LISTENING

TCP 0.0.0.0:3616 0.0.0.0:0 LISTENING

TCP 0.0.0.0:4899 0.0.0.0:0 LISTENING

TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING

TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING

TCP 0.0.0.0:26214 0.0.0.0:0 LISTENING

TCP 0.0.0.0:26470 0.0.0.0:0 LISTENING

TCP 127.0.0.1:1244 127.0.0.1:26470 ESTABLISHED

TCP 127.0.0.1:3612 127.0.0.1:26214 ESTABLISHED

TCP 127.0.0.1:26214 127.0.0.1:3612 ESTABLISHED

TCP 127.0.0.1:26470 127.0.0.1:1244 ESTABLISHED

TCP 144.158.52.170:139 0.0.0.0:0 LISTENING

TCP 144.158.52.170:1264 0.0.0.0:0 LISTENING

TCP 144.158.52.170:1312 144.158.5.59:1025 ESTABLISHED

TCP 144.158.52.170:1317 144.158.5.138:1406 ESTABLISHED

TCP 144.158.52.170:1340 150.234.146.216:445 ESTABLISHED

TCP 144.158.52.170:1357 144.155.192.178:445 ESTABLISHED

TCP 144.158.52.170:1370 144.156.219.20:445 ESTABLISHED

TCP 144.158.52.170:3604 144.156.219.15:8081 TIME_WAIT

TCP 144.158.52.170:3614 132.201.85.184:80 ESTABLISHED

TCP 144.158.52.170:3615 144.156.219.49:26214 ESTABLISHED

TCP 144.158.52.170:3616 144.156.219.49:26470 ESTABLISHED

TCP 144.158.52.170:3617 144.158.62.29:3268 TIME_WAIT

TCP 144.158.52.170:3618 144.158.62.29:3268 TIME_WAIT

TCP 144.158.52.170:9240 0.0.0.0:0 LISTENING

UDP 0.0.0.0:445 *:*

UDP 0.0.0.0:500 *:*

UDP 0.0.0.0:601 *:*

UDP 0.0.0.0:1027 *:*

UDP 0.0.0.0:1048 *:*

UDP 0.0.0.0:1052 *:*

UDP 0.0.0.0:1064 *:*

UDP 0.0.0.0:1068 *:*

UDP 0.0.0.0:1083 *:*

UDP 0.0.0.0:1101 *:*

UDP 0.0.0.0:1149 *:*

UDP 0.0.0.0:1776 *:*

UDP 0.0.0.0:3211 *:*

UDP 0.0.0.0:4500 *:*

UDP 0.0.0.0:8081 *:*

UDP 0.0.0.0:8082 *:*

UDP 127.0.0.1:3364 *:*

UDP 127.0.0.1:62515 *:*

UDP 127.0.0.1:62517 *:*

UDP 127.0.0.1:62519 *:*

UDP 127.0.0.1:62521 *:*

UDP 127.0.0.1:62523 *:*

UDP 127.0.0.1:62524 *:*

UDP 144.158.52.170:137 *:*

UDP 144.158.52.170:138 *:*

UDP 144.158.52.170:1150 *:*

UDP 144.158.52.170:13189 *:*

C:\>

"Dave" <> wrote in
microsoft.public.pocketpc.activesync:

> I'm having issues with ActiveSync over my WIFI connection.
>
> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>
> The laptop (192.168.10.98) can PING the iPaq both by IP address
> and name; the iPaq (192.168.10.97) can PING the laptop by IP
> address and name. I can even use the iPaq's file explorer to
> successfully connect to shares on the laptop (over the WIFI
> connection).
>
> After I have succesfully synch'ed the iPaq to the laptop via a
> USB cradle connection, I cannot do the same sync over the WIFI
> connection mentioned above.
>
> An Ethereal packet capture reveals packets from the iPaq to the
> laptop with "Port Destination Unreachable" for UDP ports 1900 &
> 53; but those are the _only_ errors in the packet capture during
> the ActiveSync attempt.
>
> Microsoft article Q25369 suggests that ActiveSync uses TCP ports
> 990, 999, 5678, and 5679; although I don't see any of these
> packets in the Ethereal capture.
>
> So I'm rather confused as to what I'm seeing, and why the
> ActiveSync fails over a known good WIFI connection.
>
> Thanks in advance for any assistance.



Did you enable Netbios over TCP/IP?


http://theillustratednetwork.mvps.or...ync/WM2003Acti
veSyncConfiguration.html

(URL wrap)


--
CeeBee


"I don't know half of you
half as well as I should like;
and I like less than half of you
half as well as you deserve."

Hi,
Did you enable the File and Print Sharing to access the firewall? Did you
enter the desktop's IP address as the WINS server in the Wi-Fi connection?


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

"Dave" <> wrote in message
news:%...
> I'm having issues with ActiveSync over my WIFI connection.
>
> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>
> The laptop (192.168.10.98) can PING the iPaq both by IP address and name;
> the iPaq (192.168.10.97) can PING the laptop by IP address and name. I
> can even use the iPaq's file explorer to successfully connect to shares on
> the laptop (over the WIFI connection).
>
> After I have succesfully synch'ed the iPaq to the laptop via a USB cradle
> connection, I cannot do the same sync over the WIFI connection mentioned
> above.
>
> An Ethereal packet capture reveals packets from the iPaq to the laptop
> with "Port Destination Unreachable" for UDP ports 1900 & 53; but those are
> the _only_ errors in the packet capture during the ActiveSync attempt.
>
> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990, 999,
> 5678, and 5679; although I don't see any of these packets in the Ethereal
> capture.
>
> So I'm rather confused as to what I'm seeing, and why the ActiveSync fails
> over a known good WIFI connection.
>
> Thanks in advance for any assistance.
>
>
> ================================================== ==================
> C:\>nbtstat -c
>
> Local Area Connection:
>
> Node IpAddress: [144.158.52.170] Scope Id: []
>
> No names in cache
>
> Local Area Connection 2:
>
> Node IpAddress: [192.168.10.98] Scope Id: []
>
> NetBIOS Remote Cache Name Table
>
> Name Type Host Address Life [sec]
>
> ------------------------------------------------------------
>
> HPIPAQ4705 <03> UNIQUE 192.168.10.97 -1
>
> HPIPAQ4705 <00> UNIQUE 192.168.10.97 -1
>
> HPIPAQ4705 <20> UNIQUE 192.168.10.97 -1
>
> C:\>
>
> C:\>netstat -an
>
> Active Connections
>
> Proto Local Address Foreign Address State
>
> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1072 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1312 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1314 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1315 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1317 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1340 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1357 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1370 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1776 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:2701 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:2702 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3612 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3614 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3615 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3616 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:4899 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:26214 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:26470 0.0.0.0:0 LISTENING
>
> TCP 127.0.0.1:1244 127.0.0.1:26470 ESTABLISHED
>
> TCP 127.0.0.1:3612 127.0.0.1:26214 ESTABLISHED
>
> TCP 127.0.0.1:26214 127.0.0.1:3612 ESTABLISHED
>
> TCP 127.0.0.1:26470 127.0.0.1:1244 ESTABLISHED
>
> TCP 144.158.52.170:139 0.0.0.0:0 LISTENING
>
> TCP 144.158.52.170:1264 0.0.0.0:0 LISTENING
>
> TCP 144.158.52.170:1312 144.158.5.59:1025 ESTABLISHED
>
> TCP 144.158.52.170:1317 144.158.5.138:1406 ESTABLISHED
>
> TCP 144.158.52.170:1340 150.234.146.216:445 ESTABLISHED
>
> TCP 144.158.52.170:1357 144.155.192.178:445 ESTABLISHED
>
> TCP 144.158.52.170:1370 144.156.219.20:445 ESTABLISHED
>
> TCP 144.158.52.170:3604 144.156.219.15:8081 TIME_WAIT
>
> TCP 144.158.52.170:3614 132.201.85.184:80 ESTABLISHED
>
> TCP 144.158.52.170:3615 144.156.219.49:26214 ESTABLISHED
>
> TCP 144.158.52.170:3616 144.156.219.49:26470 ESTABLISHED
>
> TCP 144.158.52.170:3617 144.158.62.29:3268 TIME_WAIT
>
> TCP 144.158.52.170:3618 144.158.62.29:3268 TIME_WAIT
>
> TCP 144.158.52.170:9240 0.0.0.0:0 LISTENING
>
> UDP 0.0.0.0:445 *:*
>
> UDP 0.0.0.0:500 *:*
>
> UDP 0.0.0.0:601 *:*
>
> UDP 0.0.0.0:1027 *:*
>
> UDP 0.0.0.0:1048 *:*
>
> UDP 0.0.0.0:1052 *:*
>
> UDP 0.0.0.0:1064 *:*
>
> UDP 0.0.0.0:1068 *:*
>
> UDP 0.0.0.0:1083 *:*
>
> UDP 0.0.0.0:1101 *:*
>
> UDP 0.0.0.0:1149 *:*
>
> UDP 0.0.0.0:1776 *:*
>
> UDP 0.0.0.0:3211 *:*
>
> UDP 0.0.0.0:4500 *:*
>
> UDP 0.0.0.0:8081 *:*
>
> UDP 0.0.0.0:8082 *:*
>
> UDP 127.0.0.1:3364 *:*
>
> UDP 127.0.0.1:62515 *:*
>
> UDP 127.0.0.1:62517 *:*
>
> UDP 127.0.0.1:62519 *:*
>
> UDP 127.0.0.1:62521 *:*
>
> UDP 127.0.0.1:62523 *:*
>
> UDP 127.0.0.1:62524 *:*
>
> UDP 144.158.52.170:137 *:*
>
> UDP 144.158.52.170:138 *:*
>
> UDP 144.158.52.170:1150 *:*
>
> UDP 144.158.52.170:13189 *:*
>
> C:\>
>
>

Yes, "Enable NetBIOS over TCP/IP" is selected for the WIFI connection on the
laptop.


"CeeBee" <> wrote in message
news:Xns9618181E1CE37ceebeechesterstartco@207.46.2 48.16...
> "Dave" <> wrote in
> microsoft.public.pocketpc.activesync:
>
>> I'm having issues with ActiveSync over my WIFI connection.
>>
>> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>>
>> The laptop (192.168.10.98) can PING the iPaq both by IP address
>> and name; the iPaq (192.168.10.97) can PING the laptop by IP
>> address and name. I can even use the iPaq's file explorer to
>> successfully connect to shares on the laptop (over the WIFI
>> connection).
>>
>> After I have succesfully synch'ed the iPaq to the laptop via a
>> USB cradle connection, I cannot do the same sync over the WIFI
>> connection mentioned above.
>>
>> An Ethereal packet capture reveals packets from the iPaq to the
>> laptop with "Port Destination Unreachable" for UDP ports 1900 &
>> 53; but those are the _only_ errors in the packet capture during
>> the ActiveSync attempt.
>>
>> Microsoft article Q25369 suggests that ActiveSync uses TCP ports
>> 990, 999, 5678, and 5679; although I don't see any of these
>> packets in the Ethereal capture.
>>
>> So I'm rather confused as to what I'm seeing, and why the
>> ActiveSync fails over a known good WIFI connection.
>>
>> Thanks in advance for any assistance.
>
>
>
> Did you enable Netbios over TCP/IP?
>
>
> http://theillustratednetwork.mvps.or...ync/WM2003Acti
> veSyncConfiguration.html
>
> (URL wrap)
>
>
> --
> CeeBee
>
>
> "I don't know half of you
> half as well as I should like;
> and I like less than half of you
> half as well as you deserve."

Thanks for the response.

I'm not sure I understand your questions, but...

On the laptop's WIFI connection, WINS servers are currently defined as:
192.168.10.97 (the iPaq's WIFI connection)
192.168.10.98 (the laptop's WIFI connection)

With respect to the File and Print Sharing access to the firewall, not sure
how/where to check that. I can tell you, however, that I can use File
Explorer on the iPaq to successfully map to a share on the laptop. (Does
that answer your question?) "File and Printer Sharing for Microsoft
Networks" is currently enabled on the laptop's WIFI connection.

Thanks again...

"Chris De Herrera" <> wrote in message
news:...
> Hi,
> Did you enable the File and Print Sharing to access the firewall? Did you
> enter the desktop's IP address as the WINS server in the Wi-Fi connection?
>
>
> --
> Chris De Herrera
> http://www.pocketpcfaq.com
> http://www.tabletpctalk.com
> http://www.pocketpctalk.com
> http://www.mobilitytalk.com
>
> "Dave" <> wrote in message
> news:%...
>> I'm having issues with ActiveSync over my WIFI connection.
>>
>> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>>
>> The laptop (192.168.10.98) can PING the iPaq both by IP address and name;
>> the iPaq (192.168.10.97) can PING the laptop by IP address and name. I
>> can even use the iPaq's file explorer to successfully connect to shares
>> on the laptop (over the WIFI connection).
>>
>> After I have succesfully synch'ed the iPaq to the laptop via a USB cradle
>> connection, I cannot do the same sync over the WIFI connection mentioned
>> above.
>>
>> An Ethereal packet capture reveals packets from the iPaq to the laptop
>> with "Port Destination Unreachable" for UDP ports 1900 & 53; but those
>> are the _only_ errors in the packet capture during the ActiveSync
>> attempt.
>>
>> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990,
>> 999, 5678, and 5679; although I don't see any of these packets in the
>> Ethereal capture.
>>
>> So I'm rather confused as to what I'm seeing, and why the ActiveSync
>> fails over a known good WIFI connection.
>>
>> Thanks in advance for any assistance.
>>
>>
>> ================================================== ==================
>> C:\>nbtstat -c
>>
>> Local Area Connection:
>>
>> Node IpAddress: [144.158.52.170] Scope Id: []
>>
>> No names in cache
>>
>> Local Area Connection 2:
>>
>> Node IpAddress: [192.168.10.98] Scope Id: []
>>
>> NetBIOS Remote Cache Name Table
>>
>> Name Type Host Address Life [sec]
>>
>> ------------------------------------------------------------
>>
>> HPIPAQ4705 <03> UNIQUE 192.168.10.97 -1
>>
>> HPIPAQ4705 <00> UNIQUE 192.168.10.97 -1
>>
>> HPIPAQ4705 <20> UNIQUE 192.168.10.97 -1
>>
>> C:\>
>>
>> C:\>netstat -an
>>
>> Active Connections
>>
>> Proto Local Address Foreign Address State
>>
>> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1072 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1312 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1314 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1315 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1317 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1340 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1357 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1370 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:1776 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:2701 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:2702 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:3612 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:3614 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:3615 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:3616 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:4899 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:26214 0.0.0.0:0 LISTENING
>>
>> TCP 0.0.0.0:26470 0.0.0.0:0 LISTENING
>>
>> TCP 127.0.0.1:1244 127.0.0.1:26470 ESTABLISHED
>>
>> TCP 127.0.0.1:3612 127.0.0.1:26214 ESTABLISHED
>>
>> TCP 127.0.0.1:26214 127.0.0.1:3612 ESTABLISHED
>>
>> TCP 127.0.0.1:26470 127.0.0.1:1244 ESTABLISHED
>>
>> TCP 144.158.52.170:139 0.0.0.0:0 LISTENING
>>
>> TCP 144.158.52.170:1264 0.0.0.0:0 LISTENING
>>
>> TCP 144.158.52.170:1312 144.158.5.59:1025 ESTABLISHED
>>
>> TCP 144.158.52.170:1317 144.158.5.138:1406 ESTABLISHED
>>
>> TCP 144.158.52.170:1340 150.234.146.216:445 ESTABLISHED
>>
>> TCP 144.158.52.170:1357 144.155.192.178:445 ESTABLISHED
>>
>> TCP 144.158.52.170:1370 144.156.219.20:445 ESTABLISHED
>>
>> TCP 144.158.52.170:3604 144.156.219.15:8081 TIME_WAIT
>>
>> TCP 144.158.52.170:3614 132.201.85.184:80 ESTABLISHED
>>
>> TCP 144.158.52.170:3615 144.156.219.49:26214 ESTABLISHED
>>
>> TCP 144.158.52.170:3616 144.156.219.49:26470 ESTABLISHED
>>
>> TCP 144.158.52.170:3617 144.158.62.29:3268 TIME_WAIT
>>
>> TCP 144.158.52.170:3618 144.158.62.29:3268 TIME_WAIT
>>
>> TCP 144.158.52.170:9240 0.0.0.0:0 LISTENING
>>
>> UDP 0.0.0.0:445 *:*
>>
>> UDP 0.0.0.0:500 *:*
>>
>> UDP 0.0.0.0:601 *:*
>>
>> UDP 0.0.0.0:1027 *:*
>>
>> UDP 0.0.0.0:1048 *:*
>>
>> UDP 0.0.0.0:1052 *:*
>>
>> UDP 0.0.0.0:1064 *:*
>>
>> UDP 0.0.0.0:1068 *:*
>>
>> UDP 0.0.0.0:1083 *:*
>>
>> UDP 0.0.0.0:1101 *:*
>>
>> UDP 0.0.0.0:1149 *:*
>>
>> UDP 0.0.0.0:1776 *:*
>>
>> UDP 0.0.0.0:3211 *:*
>>
>> UDP 0.0.0.0:4500 *:*
>>
>> UDP 0.0.0.0:8081 *:*
>>
>> UDP 0.0.0.0:8082 *:*
>>
>> UDP 127.0.0.1:3364 *:*
>>
>> UDP 127.0.0.1:62515 *:*
>>
>> UDP 127.0.0.1:62517 *:*
>>
>> UDP 127.0.0.1:62519 *:*
>>
>> UDP 127.0.0.1:62521 *:*
>>
>> UDP 127.0.0.1:62523 *:*
>>
>> UDP 127.0.0.1:62524 *:*
>>
>> UDP 144.158.52.170:137 *:*
>>
>> UDP 144.158.52.170:138 *:*
>>
>> UDP 144.158.52.170:1150 *:*
>>
>> UDP 144.158.52.170:13189 *:*
>>
>> C:\>
>>
>>
>
>

I noticed that on the desktop PC that I synch the iPaq with, over the USB
cradle connection, netstat shows an entry for UDP Port 1900:

C:\Program Files\Windows Resource Kits\Tools>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:990 0.0.0.0:0 LISTENING
TCP 127.0.0.1:990 127.0.0.1:3516 ESTABLISHED
TCP 127.0.0.1:3513 127.0.0.1:5679 ESTABLISHED
TCP 127.0.0.1:3516 127.0.0.1:990 ESTABLISHED
TCP 127.0.0.1:3518 127.0.0.1:999 ESTABLISHED
TCP 127.0.0.1:3519 127.0.0.1:5678 ESTABLISHED
TCP 127.0.0.1:3520 127.0.0.1:5678 ESTABLISHED
TCP 127.0.0.1:5678 127.0.0.1:3519 ESTABLISHED
TCP 127.0.0.1:5678 127.0.0.1:3520 ESTABLISHED
TCP 127.0.0.1:5679 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5679 127.0.0.1:3513 ESTABLISHED
UDP 192.168.10.100:1900 *:*

C:\Program Files\Windows Resource Kits\Tools>


....but on the laptop, I don't see any references to UDP Port 1900, or for
that matter TCP ports 990, 999, 5678, and 5679. That almost makes me wonder
if ActiveSync is running correctly on the laptop. But I have tried both
ActiveSync 3.7.1 and 3.1 on the laptop.

Thanks again for any assistance.


"Dave" <> wrote in message
news:%...
> I'm having issues with ActiveSync over my WIFI connection.
>
> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>
> The laptop (192.168.10.98) can PING the iPaq both by IP address and name;
> the iPaq (192.168.10.97) can PING the laptop by IP address and name. I
> can even use the iPaq's file explorer to successfully connect to shares on
> the laptop (over the WIFI connection).
>
> After I have succesfully synch'ed the iPaq to the laptop via a USB cradle
> connection, I cannot do the same sync over the WIFI connection mentioned
> above.
>
> An Ethereal packet capture reveals packets from the iPaq to the laptop
> with "Port Destination Unreachable" for UDP ports 1900 & 53; but those are
> the _only_ errors in the packet capture during the ActiveSync attempt.
>
> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990, 999,
> 5678, and 5679; although I don't see any of these packets in the Ethereal
> capture.
>
> So I'm rather confused as to what I'm seeing, and why the ActiveSync fails
> over a known good WIFI connection.
>
> Thanks in advance for any assistance.
>
>
> ================================================== ==================
> C:\>nbtstat -c
>
> Local Area Connection:
>
> Node IpAddress: [144.158.52.170] Scope Id: []
>
> No names in cache
>
> Local Area Connection 2:
>
> Node IpAddress: [192.168.10.98] Scope Id: []
>
> NetBIOS Remote Cache Name Table
>
> Name Type Host Address Life [sec]
>
> ------------------------------------------------------------
>
> HPIPAQ4705 <03> UNIQUE 192.168.10.97 -1
>
> HPIPAQ4705 <00> UNIQUE 192.168.10.97 -1
>
> HPIPAQ4705 <20> UNIQUE 192.168.10.97 -1
>
> C:\>
>
> C:\>netstat -an
>
> Active Connections
>
> Proto Local Address Foreign Address State
>
> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1072 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1312 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1314 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1315 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1317 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1340 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1357 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1370 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:1776 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:2701 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:2702 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3612 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3614 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3615 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:3616 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:4899 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:26214 0.0.0.0:0 LISTENING
>
> TCP 0.0.0.0:26470 0.0.0.0:0 LISTENING
>
> TCP 127.0.0.1:1244 127.0.0.1:26470 ESTABLISHED
>
> TCP 127.0.0.1:3612 127.0.0.1:26214 ESTABLISHED
>
> TCP 127.0.0.1:26214 127.0.0.1:3612 ESTABLISHED
>
> TCP 127.0.0.1:26470 127.0.0.1:1244 ESTABLISHED
>
> TCP 144.158.52.170:139 0.0.0.0:0 LISTENING
>
> TCP 144.158.52.170:1264 0.0.0.0:0 LISTENING
>
> TCP 144.158.52.170:1312 144.158.5.59:1025 ESTABLISHED
>
> TCP 144.158.52.170:1317 144.158.5.138:1406 ESTABLISHED
>
> TCP 144.158.52.170:1340 150.234.146.216:445 ESTABLISHED
>
> TCP 144.158.52.170:1357 144.155.192.178:445 ESTABLISHED
>
> TCP 144.158.52.170:1370 144.156.219.20:445 ESTABLISHED
>
> TCP 144.158.52.170:3604 144.156.219.15:8081 TIME_WAIT
>
> TCP 144.158.52.170:3614 132.201.85.184:80 ESTABLISHED
>
> TCP 144.158.52.170:3615 144.156.219.49:26214 ESTABLISHED
>
> TCP 144.158.52.170:3616 144.156.219.49:26470 ESTABLISHED
>
> TCP 144.158.52.170:3617 144.158.62.29:3268 TIME_WAIT
>
> TCP 144.158.52.170:3618 144.158.62.29:3268 TIME_WAIT
>
> TCP 144.158.52.170:9240 0.0.0.0:0 LISTENING
>
> UDP 0.0.0.0:445 *:*
>
> UDP 0.0.0.0:500 *:*
>
> UDP 0.0.0.0:601 *:*
>
> UDP 0.0.0.0:1027 *:*
>
> UDP 0.0.0.0:1048 *:*
>
> UDP 0.0.0.0:1052 *:*
>
> UDP 0.0.0.0:1064 *:*
>
> UDP 0.0.0.0:1068 *:*
>
> UDP 0.0.0.0:1083 *:*
>
> UDP 0.0.0.0:1101 *:*
>
> UDP 0.0.0.0:1149 *:*
>
> UDP 0.0.0.0:1776 *:*
>
> UDP 0.0.0.0:3211 *:*
>
> UDP 0.0.0.0:4500 *:*
>
> UDP 0.0.0.0:8081 *:*
>
> UDP 0.0.0.0:8082 *:*
>
> UDP 127.0.0.1:3364 *:*
>
> UDP 127.0.0.1:62515 *:*
>
> UDP 127.0.0.1:62517 *:*
>
> UDP 127.0.0.1:62519 *:*
>
> UDP 127.0.0.1:62521 *:*
>
> UDP 127.0.0.1:62523 *:*
>
> UDP 127.0.0.1:62524 *:*
>
> UDP 144.158.52.170:137 *:*
>
> UDP 144.158.52.170:138 *:*
>
> UDP 144.158.52.170:1150 *:*
>
> UDP 144.158.52.170:13189 *:*
>
> C:\>
>
>

Hi,
In the Wi-Fi connection on the iPAQ did you enter the ip 192.168.10.98 as
the WINS address for the PC? Do you have the Wi-Fi network set to Work in
the Connection Manager?


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

"Dave" <> wrote in message
news:...
> Thanks for the response.
>
> I'm not sure I understand your questions, but...
>
> On the laptop's WIFI connection, WINS servers are currently defined as:
> 192.168.10.97 (the iPaq's WIFI connection)
> 192.168.10.98 (the laptop's WIFI connection)
>
> With respect to the File and Print Sharing access to the firewall, not
> sure how/where to check that. I can tell you, however, that I can use
> File Explorer on the iPaq to successfully map to a share on the laptop.
> (Does that answer your question?) "File and Printer Sharing for Microsoft
> Networks" is currently enabled on the laptop's WIFI connection.
>
> Thanks again...
>
> "Chris De Herrera" <> wrote in message
> news:...
>> Hi,
>> Did you enable the File and Print Sharing to access the firewall? Did
>> you enter the desktop's IP address as the WINS server in the Wi-Fi
>> connection?
>>
>>
>> --
>> Chris De Herrera
>> http://www.pocketpcfaq.com
>> http://www.tabletpctalk.com
>> http://www.pocketpctalk.com
>> http://www.mobilitytalk.com
>>
>> "Dave" <> wrote in message
>> news:%...
>>> I'm having issues with ActiveSync over my WIFI connection.
>>>
>>> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>>>
>>> The laptop (192.168.10.98) can PING the iPaq both by IP address and
>>> name; the iPaq (192.168.10.97) can PING the laptop by IP address and
>>> name. I can even use the iPaq's file explorer to successfully connect
>>> to shares on the laptop (over the WIFI connection).
>>>
>>> After I have succesfully synch'ed the iPaq to the laptop via a USB
>>> cradle connection, I cannot do the same sync over the WIFI connection
>>> mentioned above.
>>>
>>> An Ethereal packet capture reveals packets from the iPaq to the laptop
>>> with "Port Destination Unreachable" for UDP ports 1900 & 53; but those
>>> are the _only_ errors in the packet capture during the ActiveSync
>>> attempt.
>>>
>>> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990,
>>> 999, 5678, and 5679; although I don't see any of these packets in the
>>> Ethereal capture.
>>>
>>> So I'm rather confused as to what I'm seeing, and why the ActiveSync
>>> fails over a known good WIFI connection.
>>>
>>> Thanks in advance for any assistance.
>>>
>>>
>>> ================================================== ==================
>>> C:\>nbtstat -c
>>>
>>> Local Area Connection:
>>>
>>> Node IpAddress: [144.158.52.170] Scope Id: []
>>>
>>> No names in cache
>>>
>>> Local Area Connection 2:
>>>
>>> Node IpAddress: [192.168.10.98] Scope Id: []
>>>
>>> NetBIOS Remote Cache Name Table
>>>
>>> Name Type Host Address Life [sec]
>>>
>>> ------------------------------------------------------------
>>>
>>> HPIPAQ4705 <03> UNIQUE 192.168.10.97 -1
>>>
>>> HPIPAQ4705 <00> UNIQUE 192.168.10.97 -1
>>>
>>> HPIPAQ4705 <20> UNIQUE 192.168.10.97 -1
>>>
>>> C:\>
>>>
>>> C:\>netstat -an
>>>
>>> Active Connections
>>>
>>> Proto Local Address Foreign Address State
>>>
>>> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1072 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1312 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1314 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1315 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1317 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1340 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1357 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1370 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:1776 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:2701 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:2702 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:3612 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:3614 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:3615 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:3616 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:4899 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:26214 0.0.0.0:0 LISTENING
>>>
>>> TCP 0.0.0.0:26470 0.0.0.0:0 LISTENING
>>>
>>> TCP 127.0.0.1:1244 127.0.0.1:26470 ESTABLISHED
>>>
>>> TCP 127.0.0.1:3612 127.0.0.1:26214 ESTABLISHED
>>>
>>> TCP 127.0.0.1:26214 127.0.0.1:3612 ESTABLISHED
>>>
>>> TCP 127.0.0.1:26470 127.0.0.1:1244 ESTABLISHED
>>>
>>> TCP 144.158.52.170:139 0.0.0.0:0 LISTENING
>>>
>>> TCP 144.158.52.170:1264 0.0.0.0:0 LISTENING
>>>
>>> TCP 144.158.52.170:1312 144.158.5.59:1025 ESTABLISHED
>>>
>>> TCP 144.158.52.170:1317 144.158.5.138:1406 ESTABLISHED
>>>
>>> TCP 144.158.52.170:1340 150.234.146.216:445 ESTABLISHED
>>>
>>> TCP 144.158.52.170:1357 144.155.192.178:445 ESTABLISHED
>>>
>>> TCP 144.158.52.170:1370 144.156.219.20:445 ESTABLISHED
>>>
>>> TCP 144.158.52.170:3604 144.156.219.15:8081 TIME_WAIT
>>>
>>> TCP 144.158.52.170:3614 132.201.85.184:80 ESTABLISHED
>>>
>>> TCP 144.158.52.170:3615 144.156.219.49:26214 ESTABLISHED
>>>
>>> TCP 144.158.52.170:3616 144.156.219.49:26470 ESTABLISHED
>>>
>>> TCP 144.158.52.170:3617 144.158.62.29:3268 TIME_WAIT
>>>
>>> TCP 144.158.52.170:3618 144.158.62.29:3268 TIME_WAIT
>>>
>>> TCP 144.158.52.170:9240 0.0.0.0:0 LISTENING
>>>
>>> UDP 0.0.0.0:445 *:*
>>>
>>> UDP 0.0.0.0:500 *:*
>>>
>>> UDP 0.0.0.0:601 *:*
>>>
>>> UDP 0.0.0.0:1027 *:*
>>>
>>> UDP 0.0.0.0:1048 *:*
>>>
>>> UDP 0.0.0.0:1052 *:*
>>>
>>> UDP 0.0.0.0:1064 *:*
>>>
>>> UDP 0.0.0.0:1068 *:*
>>>
>>> UDP 0.0.0.0:1083 *:*
>>>
>>> UDP 0.0.0.0:1101 *:*
>>>
>>> UDP 0.0.0.0:1149 *:*
>>>
>>> UDP 0.0.0.0:1776 *:*
>>>
>>> UDP 0.0.0.0:3211 *:*
>>>
>>> UDP 0.0.0.0:4500 *:*
>>>
>>> UDP 0.0.0.0:8081 *:*
>>>
>>> UDP 0.0.0.0:8082 *:*
>>>
>>> UDP 127.0.0.1:3364 *:*
>>>
>>> UDP 127.0.0.1:62515 *:*
>>>
>>> UDP 127.0.0.1:62517 *:*
>>>
>>> UDP 127.0.0.1:62519 *:*
>>>
>>> UDP 127.0.0.1:62521 *:*
>>>
>>> UDP 127.0.0.1:62523 *:*
>>>
>>> UDP 127.0.0.1:62524 *:*
>>>
>>> UDP 144.158.52.170:137 *:*
>>>
>>> UDP 144.158.52.170:138 *:*
>>>
>>> UDP 144.158.52.170:1150 *:*
>>>
>>> UDP 144.158.52.170:13189 *:*
>>>
>>> C:\>
>>>
>>>
>>
>>
>
>

Chris, Thanks. I think it's already configured that way; here are all the
details:

On the iPaq:

Connections|Network Adapters, "My network card connects to:" is set to WORK

"HP iPAQ WIFI Adapters" is configured as:
IP Address: 192.168.10.97
Subnet mask: 255.255.255.0
Default Gateway: 192.168.10.98

DNS: 192.168.10.98.98
Alt DNS: 192.168.10.97
WINS: 192.168.10.98.98
Alt WINS: 192.168.10.97

ActiveSync on the iPaq:
TOOLS|Options...
Use this PC: ILACDB4295LT02
vxUtil on the iPaq shows that PING of ILACDB4295LT02 is successful, and
resolves to 192.168.10.98.



On the laptop:
The WIFI Card is LAN Connection 2.

NetBEUI Protocol is installed and enabled.

TCP/IP Protocol is installed and enabled.
IP Address: 192.168.10.98
Subnet mask: 255.255.255.0
Default Gateway: 192.168.10.97

DNS: 192.168.10.98.97
Alt DNS: 192.168.10.98
WINS: 192.168.10.98.97
Alt WINS: 192.168.10.98
Enable NetBIOS over TCP/IP is selected and enabled

IP Security:
Do not use IPSEC is selected
TCP/IP Filtering
Enable TCP/IP Filtering is not selected

The DLink WIFI Utility shows the WIFI connection as connected. It is
also set to have that particular connection set to
IP Address: 192.168.10.98
Subnet mask: 255.255.255.0
Default Gateway: 192.168.10.97

DNS: 192.168.10.98.97
Alt DNS: 192.168.10.98

ActiveSync 3.8 on the laptop:
Flie|Connection Settings...
"Allow USB connection with this desktop" is selected; Status = USB
is available
"Allow network (Ethernet) and DAS server connection with this
desktop computer" is selected; Status = Network is available.
TOOLS|Options|Rules...
Pass Through conenction is set to: WORK
"Open ActiveSync when my mobile device connects" is selected
TOOLS|Options|Schedule...
Wireless schedule: all items are greyed out, and I cannot select
anything.

c:\> Ping HPiPaq4705
resolves to 192.168.10.97, and gets successful responses.

Hope this information helps.

Thanks again.

"Chris De Herrera" <> wrote in message
news:...
> Hi,
> In the Wi-Fi connection on the iPAQ did you enter the ip 192.168.10.98 as
> the WINS address for the PC? Do you have the Wi-Fi network set to Work in
> the Connection Manager?
>
>
> --
> Chris De Herrera
> http://www.pocketpcfaq.com
> http://www.tabletpctalk.com
> http://www.pocketpctalk.com
> http://www.mobilitytalk.com
>
> "Dave" <> wrote in message
> news:...
>> Thanks for the response.
>>
>> I'm not sure I understand your questions, but...
>>
>> On the laptop's WIFI connection, WINS servers are currently defined as:
>> 192.168.10.97 (the iPaq's WIFI connection)
>> 192.168.10.98 (the laptop's WIFI connection)
>>
>> With respect to the File and Print Sharing access to the firewall, not
>> sure how/where to check that. I can tell you, however, that I can use
>> File Explorer on the iPaq to successfully map to a share on the laptop.
>> (Does that answer your question?) "File and Printer Sharing for
>> Microsoft Networks" is currently enabled on the laptop's WIFI connection.
>>
>> Thanks again...
>>
>> "Chris De Herrera" <> wrote in message
>> news:...
>>> Hi,
>>> Did you enable the File and Print Sharing to access the firewall? Did
>>> you enter the desktop's IP address as the WINS server in the Wi-Fi
>>> connection?
>>>
>>>
>>> --
>>> Chris De Herrera
>>> http://www.pocketpcfaq.com
>>> http://www.tabletpctalk.com
>>> http://www.pocketpctalk.com
>>> http://www.mobilitytalk.com
>>>
>>> "Dave" <> wrote in message
>>> news:%...
>>>> I'm having issues with ActiveSync over my WIFI connection.
>>>>
>>>> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>>>>
>>>> The laptop (192.168.10.98) can PING the iPaq both by IP address and
>>>> name; the iPaq (192.168.10.97) can PING the laptop by IP address and
>>>> name. I can even use the iPaq's file explorer to successfully connect
>>>> to shares on the laptop (over the WIFI connection).
>>>>
>>>> After I have succesfully synch'ed the iPaq to the laptop via a USB
>>>> cradle connection, I cannot do the same sync over the WIFI connection
>>>> mentioned above.
>>>>
>>>> An Ethereal packet capture reveals packets from the iPaq to the laptop
>>>> with "Port Destination Unreachable" for UDP ports 1900 & 53; but those
>>>> are the _only_ errors in the packet capture during the ActiveSync
>>>> attempt.
>>>>
>>>> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990,
>>>> 999, 5678, and 5679; although I don't see any of these packets in the
>>>> Ethereal capture.
>>>>
>>>> So I'm rather confused as to what I'm seeing, and why the ActiveSync
>>>> fails over a known good WIFI connection.
>>>>
>>>> Thanks in advance for any assistance.
>>>>
>>>>
>>>> ================================================== ==================
>>>> C:\>nbtstat -c
>>>>
>>>> Local Area Connection:
>>>>
>>>> Node IpAddress: [144.158.52.170] Scope Id: []
>>>>
>>>> No names in cache
>>>>
>>>> Local Area Connection 2:
>>>>
>>>> Node IpAddress: [192.168.10.98] Scope Id: []
>>>>
>>>> NetBIOS Remote Cache Name Table
>>>>
>>>> Name Type Host Address Life [sec]
>>>>
>>>> ------------------------------------------------------------
>>>>
>>>> HPIPAQ4705 <03> UNIQUE 192.168.10.97 -1
>>>>
>>>> HPIPAQ4705 <00> UNIQUE 192.168.10.97 -1
>>>>
>>>> HPIPAQ4705 <20> UNIQUE 192.168.10.97 -1
>>>>
>>>> C:\>
>>>>
>>>> C:\>netstat -an
>>>>
>>>> Active Connections
>>>>
>>>> Proto Local Address Foreign Address State
>>>>
>>>> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1072 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1312 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1314 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1315 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1317 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1340 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1357 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1370 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:1776 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:2701 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:2702 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:3612 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:3614 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:3615 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:3616 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:4899 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:26214 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 0.0.0.0:26470 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 127.0.0.1:1244 127.0.0.1:26470 ESTABLISHED
>>>>
>>>> TCP 127.0.0.1:3612 127.0.0.1:26214 ESTABLISHED
>>>>
>>>> TCP 127.0.0.1:26214 127.0.0.1:3612 ESTABLISHED
>>>>
>>>> TCP 127.0.0.1:26470 127.0.0.1:1244 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:139 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 144.158.52.170:1264 0.0.0.0:0 LISTENING
>>>>
>>>> TCP 144.158.52.170:1312 144.158.5.59:1025 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:1317 144.158.5.138:1406 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:1340 150.234.146.216:445 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:1357 144.155.192.178:445 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:1370 144.156.219.20:445 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:3604 144.156.219.15:8081 TIME_WAIT
>>>>
>>>> TCP 144.158.52.170:3614 132.201.85.184:80 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:3615 144.156.219.49:26214 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:3616 144.156.219.49:26470 ESTABLISHED
>>>>
>>>> TCP 144.158.52.170:3617 144.158.62.29:3268 TIME_WAIT
>>>>
>>>> TCP 144.158.52.170:3618 144.158.62.29:3268 TIME_WAIT
>>>>
>>>> TCP 144.158.52.170:9240 0.0.0.0:0 LISTENING
>>>>
>>>> UDP 0.0.0.0:445 *:*
>>>>
>>>> UDP 0.0.0.0:500 *:*
>>>>
>>>> UDP 0.0.0.0:601 *:*
>>>>
>>>> UDP 0.0.0.0:1027 *:*
>>>>
>>>> UDP 0.0.0.0:1048 *:*
>>>>
>>>> UDP 0.0.0.0:1052 *:*
>>>>
>>>> UDP 0.0.0.0:1064 *:*
>>>>
>>>> UDP 0.0.0.0:1068 *:*
>>>>
>>>> UDP 0.0.0.0:1083 *:*
>>>>
>>>> UDP 0.0.0.0:1101 *:*
>>>>
>>>> UDP 0.0.0.0:1149 *:*
>>>>
>>>> UDP 0.0.0.0:1776 *:*
>>>>
>>>> UDP 0.0.0.0:3211 *:*
>>>>
>>>> UDP 0.0.0.0:4500 *:*
>>>>
>>>> UDP 0.0.0.0:8081 *:*
>>>>
>>>> UDP 0.0.0.0:8082 *:*
>>>>
>>>> UDP 127.0.0.1:3364 *:*
>>>>
>>>> UDP 127.0.0.1:62515 *:*
>>>>
>>>> UDP 127.0.0.1:62517 *:*
>>>>
>>>> UDP 127.0.0.1:62519 *:*
>>>>
>>>> UDP 127.0.0.1:62521 *:*
>>>>
>>>> UDP 127.0.0.1:62523 *:*
>>>>
>>>> UDP 127.0.0.1:62524 *:*
>>>>
>>>> UDP 144.158.52.170:137 *:*
>>>>
>>>> UDP 144.158.52.170:138 *:*
>>>>
>>>> UDP 144.158.52.170:1150 *:*
>>>>
>>>> UDP 144.158.52.170:13189 *:*
>>>>
>>>> C:\>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Hi,
It should work with the settings you have. Have you tried temporarily
disabling any software firewall on your PC?


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

"Dave" <> wrote in message
news:...
> Chris, Thanks. I think it's already configured that way; here are all the
> details:
>
> On the iPaq:
>
> Connections|Network Adapters, "My network card connects to:" is set to
> WORK
>
> "HP iPAQ WIFI Adapters" is configured as:
> IP Address: 192.168.10.97
> Subnet mask: 255.255.255.0
> Default Gateway: 192.168.10.98
>
> DNS: 192.168.10.98.98
> Alt DNS: 192.168.10.97
> WINS: 192.168.10.98.98
> Alt WINS: 192.168.10.97
>
> ActiveSync on the iPaq:
> TOOLS|Options...
> Use this PC: ILACDB4295LT02
> vxUtil on the iPaq shows that PING of ILACDB4295LT02 is successful, and
> resolves to 192.168.10.98.
>
>
>
> On the laptop:
> The WIFI Card is LAN Connection 2.
>
> NetBEUI Protocol is installed and enabled.
>
> TCP/IP Protocol is installed and enabled.
> IP Address: 192.168.10.98
> Subnet mask: 255.255.255.0
> Default Gateway: 192.168.10.97
>
> DNS: 192.168.10.98.97
> Alt DNS: 192.168.10.98
> WINS: 192.168.10.98.97
> Alt WINS: 192.168.10.98
> Enable NetBIOS over TCP/IP is selected and enabled
>
> IP Security:
> Do not use IPSEC is selected
> TCP/IP Filtering
> Enable TCP/IP Filtering is not selected
>
> The DLink WIFI Utility shows the WIFI connection as connected. It is
> also set to have that particular connection set to
> IP Address: 192.168.10.98
> Subnet mask: 255.255.255.0
> Default Gateway: 192.168.10.97
>
> DNS: 192.168.10.98.97
> Alt DNS: 192.168.10.98
>
> ActiveSync 3.8 on the laptop:
> Flie|Connection Settings...
> "Allow USB connection with this desktop" is selected; Status = USB
> is available
> "Allow network (Ethernet) and DAS server connection with this
> desktop computer" is selected; Status = Network is available.
> TOOLS|Options|Rules...
> Pass Through conenction is set to: WORK
> "Open ActiveSync when my mobile device connects" is selected
> TOOLS|Options|Schedule...
> Wireless schedule: all items are greyed out, and I cannot select
> anything.
>
> c:\> Ping HPiPaq4705
> resolves to 192.168.10.97, and gets successful responses.
>
> Hope this information helps.
>
> Thanks again.
>
> "Chris De Herrera" <> wrote in message
> news:...
>> Hi,
>> In the Wi-Fi connection on the iPAQ did you enter the ip 192.168.10.98 as
>> the WINS address for the PC? Do you have the Wi-Fi network set to Work
>> in the Connection Manager?
>>
>>
>> --
>> Chris De Herrera
>> http://www.pocketpcfaq.com
>> http://www.tabletpctalk.com
>> http://www.pocketpctalk.com
>> http://www.mobilitytalk.com
>>
>> "Dave" <> wrote in message
>> news:...
>>> Thanks for the response.
>>>
>>> I'm not sure I understand your questions, but...
>>>
>>> On the laptop's WIFI connection, WINS servers are currently defined as:
>>> 192.168.10.97 (the iPaq's WIFI connection)
>>> 192.168.10.98 (the laptop's WIFI connection)
>>>
>>> With respect to the File and Print Sharing access to the firewall, not
>>> sure how/where to check that. I can tell you, however, that I can use
>>> File Explorer on the iPaq to successfully map to a share on the laptop.
>>> (Does that answer your question?) "File and Printer Sharing for
>>> Microsoft Networks" is currently enabled on the laptop's WIFI
>>> connection.
>>>
>>> Thanks again...
>>>
>>> "Chris De Herrera" <> wrote in message
>>> news:...
>>>> Hi,
>>>> Did you enable the File and Print Sharing to access the firewall? Did
>>>> you enter the desktop's IP address as the WINS server in the Wi-Fi
>>>> connection?
>>>>
>>>>
>>>> --
>>>> Chris De Herrera
>>>> http://www.pocketpcfaq.com
>>>> http://www.tabletpctalk.com
>>>> http://www.pocketpctalk.com
>>>> http://www.mobilitytalk.com
>>>>
>>>> "Dave" <> wrote in message
>>>> news:%...
>>>>> I'm having issues with ActiveSync over my WIFI connection.
>>>>>
>>>>> I have a iPaq4705 connecting to my laptop's DLink WIFI card.
>>>>>
>>>>> The laptop (192.168.10.98) can PING the iPaq both by IP address and
>>>>> name; the iPaq (192.168.10.97) can PING the laptop by IP address and
>>>>> name. I can even use the iPaq's file explorer to successfully connect
>>>>> to shares on the laptop (over the WIFI connection).
>>>>>
>>>>> After I have succesfully synch'ed the iPaq to the laptop via a USB
>>>>> cradle connection, I cannot do the same sync over the WIFI connection
>>>>> mentioned above.
>>>>>
>>>>> An Ethereal packet capture reveals packets from the iPaq to the laptop
>>>>> with "Port Destination Unreachable" for UDP ports 1900 & 53; but those
>>>>> are the _only_ errors in the packet capture during the ActiveSync
>>>>> attempt.
>>>>>
>>>>> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990,
>>>>> 999, 5678, and 5679; although I don't see any of these packets in the
>>>>> Ethereal capture.
>>>>>
>>>>> So I'm rather confused as to what I'm seeing, and why the ActiveSync
>>>>> fails over a known good WIFI connection.
>>>>>
>>>>> Thanks in advance for any assistance.
>>>>>
>>>>>
>>>>> ================================================== ==================
>>>>> C:\>nbtstat -c
>>>>>
>>>>> Local Area Connection:
>>>>>
>>>>> Node IpAddress: [144.158.52.170] Scope Id: []
>>>>>
>>>>> No names in cache
>>>>>
>>>>> Local Area Connection 2:
>>>>>
>>>>> Node IpAddress: [192.168.10.98] Scope Id: []
>>>>>
>>>>> NetBIOS Remote Cache Name Table
>>>>>
>>>>> Name Type Host Address Life [sec]
>>>>>
>>>>> ------------------------------------------------------------
>>>>>
>>>>> HPIPAQ4705 <03> UNIQUE 192.168.10.97 -1
>>>>>
>>>>> HPIPAQ4705 <00> UNIQUE 192.168.10.97 -1
>>>>>
>>>>> HPIPAQ4705 <20> UNIQUE 192.168.10.97 -1
>>>>>
>>>>> C:\>
>>>>>
>>>>> C:\>netstat -an
>>>>>
>>>>> Active Connections
>>>>>
>>>>> Proto Local Address Foreign Address State
>>>>>
>>>>> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1072 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1073 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1244 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1312 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1314 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1315 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1317 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1340 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1357 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1370 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:1776 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:2701 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:2702 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:3612 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:3614 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:3615 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:3616 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:4899 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:26214 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 0.0.0.0:26470 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 127.0.0.1:1244 127.0.0.1:26470 ESTABLISHED
>>>>>
>>>>> TCP 127.0.0.1:3612 127.0.0.1:26214 ESTABLISHED
>>>>>
>>>>> TCP 127.0.0.1:26214 127.0.0.1:3612 ESTABLISHED
>>>>>
>>>>> TCP 127.0.0.1:26470 127.0.0.1:1244 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:139 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 144.158.52.170:1264 0.0.0.0:0 LISTENING
>>>>>
>>>>> TCP 144.158.52.170:1312 144.158.5.59:1025 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:1317 144.158.5.138:1406 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:1340 150.234.146.216:445 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:1357 144.155.192.178:445 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:1370 144.156.219.20:445 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:3604 144.156.219.15:8081 TIME_WAIT
>>>>>
>>>>> TCP 144.158.52.170:3614 132.201.85.184:80 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:3615 144.156.219.49:26214 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:3616 144.156.219.49:26470 ESTABLISHED
>>>>>
>>>>> TCP 144.158.52.170:3617 144.158.62.29:3268 TIME_WAIT
>>>>>
>>>>> TCP 144.158.52.170:3618 144.158.62.29:3268 TIME_WAIT
>>>>>
>>>>> TCP 144.158.52.170:9240 0.0.0.0:0 LISTENING
>>>>>
>>>>> UDP 0.0.0.0:445 *:*
>>>>>
>>>>> UDP 0.0.0.0:500 *:*
>>>>>
>>>>> UDP 0.0.0.0:601 *:*
>>>>>
>>>>> UDP 0.0.0.0:1027 *:*
>>>>>
>>>>> UDP 0.0.0.0:1048 *:*
>>>>>
>>>>> UDP 0.0.0.0:1052 *:*
>>>>>
>>>>> UDP 0.0.0.0:1064 *:*
>>>>>
>>>>> UDP 0.0.0.0:1068 *:*
>>>>>
>>>>> UDP 0.0.0.0:1083 *:*
>>>>>
>>>>> UDP 0.0.0.0:1101 *:*
>>>>>
>>>>> UDP 0.0.0.0:1149 *:*
>>>>>
>>>>> UDP 0.0.0.0:1776 *:*
>>>>>
>>>>> UDP 0.0.0.0:3211 *:*
>>>>>
>>>>> UDP 0.0.0.0:4500 *:*
>>>>>
>>>>> UDP 0.0.0.0:8081 *:*
>>>>>
>>>>> UDP 0.0.0.0:8082 *:*
>>>>>
>>>>> UDP 127.0.0.1:3364 *:*
>>>>>
>>>>> UDP 127.0.0.1:62515 *:*
>>>>>
>>>>> UDP 127.0.0.1:62517 *:*
>>>>>
>>>>> UDP 127.0.0.1:62519 *:*
>>>>>
>>>>> UDP 127.0.0.1:62521 *:*
>>>>>
>>>>> UDP 127.0.0.1:62523 *:*
>>>>>
>>>>> UDP 127.0.0.1:62524 *:*
>>>>>
>>>>> UDP 144.158.52.170:137 *:*
>>>>>
>>>>> UDP 144.158.52.170:138 *:*
>>>>>
>>>>> UDP 144.158.52.170:1150 *:*
>>>>>
>>>>> UDP 144.158.52.170:13189 *:*
>>>>>
>>>>> C:\>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>