Re: ActiveSync 3.8/WIFI

From: Chris De Herrera (spam_at_pocketpctalk.com)
Date: 03/13/05 

Date: Sat, 12 Mar 2005 20:59:10 -0800

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" <dave.blackwell@sbcglobal.net> wrote in message 
news:%23G8OY9oJFHA.3788@tk2msftngp13.phx.gbl...
> 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:\>
>
>

Relevant Pages

  • Re: VPN - How do they know?
    ... Funny that - because I connect from work to home most days tunnelling ... an OpenVPN connection through the corporate web proxy using TCP. ... TCP is adaptive to bandwidth - so if you have a poor connection, ... than UDP). ...
    (uk.telecom.broadband)
  • Re: netstat command
    ... It seems like normal Windows Apps. ... 02k.exe:700 TCP my200srv:15000 my200srv:0 LISTENING ... dns.exe:1040 UDP my200srv:domain *:* ...
    (microsoft.public.security.virus)
  • Re: netstat command
    ... It seems like normal Windows Apps. ... 02k.exe:700 TCP my200srv:15000 my200srv:0 LISTENING ... dns.exe:1040 UDP my200srv:domain *:* ...
    (microsoft.public.win2000.security)
  • Re: Cant get UDP example to work
    ... differences between UDP and TCP. ... The example you gave uses connecton a UDP socket. ... There really is no connection set up when you ...
    (comp.lang.python)
  • Re: ActiveSync 3.8/WIFI
    ... In the Wi-Fi connection on the iPAQ did you enter the ip 192.168.10.98 as ... I can tell you, however, that I can use> File Explorer on the iPaq to successfully map to a share on the laptop. ... >>> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990, ... >>> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING>>> ...
    (microsoft.public.pocketpc.activesync)
Loading