Re: Can't pull mail via USB

On 16 Dec 2005 17:00:47 -0800, "StoneColdStunner"
<> wrote:

>Me again. when I cradle my unit, it won't pull email via the USB
>cradle. I get email via the EVDO connect I make via ActiveSync 3.8 and
>my OWA server. is this normal? I told AS when the partnership was
>setup that it was via the exchange server, the bottom option, not the
>top one.
>
>I have a Xv6600 Audiovox with the latest and greatest Roms and patches.

Do you get an error message when trying to synchronize via the USB
cable? Are you running any firewalls on the desktop?

--
Rob Borek
Microsoft MVP - Mobile Devices
Want *ONE ON ONE* support? http://www.pocketpcone2one.com
Please place all replies into the newsgroup so that others can benefit.

On 17 Dec 2005 07:40:10 -0800, "StoneColdStunner"
<> wrote:

>here is that log. I don't have a 192.168.55.x network. is windows
>giving this its own IP for internal proxy. I see the loopback running
>
>Have Outpost on the laptop, but it is disabled. Only use it when
>traveling or running testing outside of corp firewall

It looks like the ports are being blocked and/or there is a problem
connecting. ActiveSync uses PPP to communicate to the device, and a
proxy in ActiveSync passes through TCP connections to the Internet.
Double check to make sure there isn't anything even running on the
notebook that could be causing problems (sometimes even if the program
is running it can cause problems).

--
Rob Borek
Microsoft MVP - Mobile Devices
Want *ONE ON ONE* support? http://www.pocketpcone2one.com
Please place all replies into the newsgroup so that others can benefit.

The 192.168.55.x network is the RAS network between the
device(192.168.55.101) an PC (192.168.55.100). From the logs the device
connected to 64.135.41.80 port 443 and sent 273 bytes and received 1237. The
device then terminated the connection. Are you receiving any error on the
device??

--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no rights.



"StoneColdStunner" <> wrote in message
news: oups.com...
> here is that log. I don't have a 192.168.55.x network. is windows
> giving this its own IP for internal proxy. I see the loopback running
>
> Have Outpost on the laptop, but it is disabled. Only use it when
> traveling or running testing outside of corp firewall
>
> -----------
> 2/17/2005 10:31:43.701 - Windows CE Services (3.8.5004) Communication
> Logging.
> 12/17/2005 10:31:43.701 - Logging file auto-purge after a successful
> device connection.
> 12/17/2005 10:31:43.701 - Connection: Process connection from IP
> address 127.0.0.1:1425.
> 12/17/2005 10:31:43.721 - CesProxy: Accept on port 990, IsWinsock 1,
> hResult 0
> 12/17/2005 10:31:43.721 - TCP: ....S., 192.168.55.100(1035) =>
> 192.168.55.101(990) Seq=53358525-53358525 Ack=0 Win=8192 Len=44
> 12/17/2005 10:31:43.731 - TCP: .A..S., 192.168.55.101(990) =>
> 192.168.55.100(1035) Seq=22228394-22228394 Ack=53358526 Win=32768
> Len=44
> 12/17/2005 10:31:44.773 - CesProxy: Accept on port 990, IsWinsock 1,
> hResult 0
> 12/17/2005 10:31:44.773 - TCP: ....S., 192.168.55.100(1036) =>
> 192.168.55.101(990) Seq=53359577-53359577 Ack=0 Win=8192 Len=44
> 12/17/2005 10:31:44.773 - TCP: .A..S., 192.168.55.101(990) =>
> 192.168.55.100(1036) Seq=22512717-22512717 Ack=53359578 Win=32768
> Len=44
> 12/17/2005 10:31:44.883 - CesProxy: recv failed on Win socket 990, err
> = 10054
> 12/17/2005 10:31:44.883 - CesProxy: Close Win socket 990
> 12/17/2005 10:31:44.883 - CesProxy: Close PPP socket 990
> 12/17/2005 10:31:44.883 - TCP: ...R.., 192.168.55.100(1035) =>
> 192.168.55.101(990) Seq=53358716-53358716 Ack=22228435 Win=0 Len=40
> 12/17/2005 10:31:44.883 - CesProxy: recv failed on PPP socket 990, err
> = 10004
> 12/17/2005 10:31:46.416 - TCP: ....S., 192.168.55.101(1036) =>
> 192.168.55.100(999) Seq=22962909-22962909 Ack=0 Win=32768 Len=48
> 12/17/2005 10:31:46.416 - Proxy: Connection Attempt on port 999, dest
> ip 0x6437a8c0
> 12/17/2005 10:31:46.426 - TCP: .A..S., 192.168.55.100(999) =>
> 192.168.55.101(1036) Seq=53361229-53361229 Ack=22962910 Win=8760 Len=44
> 12/17/2005 10:31:46.426 - CesProxy: Accept on port 999, IsWinsock 0,
> hResult 0
> 12/17/2005 10:31:47.278 - TCP: ....S., 192.168.55.101(1037) =>
> 192.168.55.100(5678) Seq=23244553-23244553 Ack=0 Win=32768 Len=48
> 12/17/2005 10:31:47.278 - Proxy: Connection Attempt on port 5678, dest
> ip 0x6437a8c0
> 12/17/2005 10:31:47.278 - TCP: .A..S., 192.168.55.100(5678) =>
> 192.168.55.101(1037) Seq=53362080-53362080 Ack=23244554 Win=8760 Len=44
> 12/17/2005 10:31:47.368 - TCP: ....S., 192.168.55.101(1038) =>
> 192.168.55.100(5678) Seq=23311417-23311417 Ack=0 Win=32768 Len=48
> 12/17/2005 10:31:47.368 - TCP: .A..S., 192.168.55.100(5678) =>
> 192.168.55.101(1038) Seq=53362170-53362170 Ack=23311418 Win=8760 Len=44
> 12/17/2005 10:31:47.508 - TCP: ....S., 192.168.55.101(1039) =>
> 64.135.41.80(443) Seq=23394530-23394530 Ack=0 Win=32768 Len=48
> 12/17/2005 10:31:47.508 - Proxy: Connection Attempt on port 443, dest
> ip 0x50298740
> 12/17/2005 10:31:47.508 - TCP: .A..S., 64.135.41.80(443) =>
> 192.168.55.101(1039) Seq=53362310-53362310 Ack=23394531 Win=8760 Len=44
> 12/17/2005 10:31:48.039 - CesProxy: Accept on port 5678, IsWinsock 0,
> hResult 0
> 12/17/2005 10:31:48.039 - CesProxy: Accept on port 443, IsWinsock 0,
> hResult 0
> 12/17/2005 10:31:48.039 - CesProxy: Accept on port 5678, IsWinsock 0,
> hResult 0
> 12/17/2005 10:31:48.290 - TCP: ...R.., 192.168.55.101(1039) =>
> 64.135.41.80(443) Seq=23394804-23394804 Ack=53363547 Win=0 Len=40
> 12/17/2005 10:31:48.290 - CesProxy: recv failed on PPP socket 443, err
> = 10054
> 12/17/2005 10:31:48.290 - CesProxy: Close PPP socket 443
> 12/17/2005 10:31:48.290 - CesProxy: Close Win socket 443
> 12/17/2005 10:31:48.290 - CesProxy: recv failed on Win socket 443, err
> = 10053
> 12/17/2005 10:31:48.300 - TCP: ....S., 192.168.55.101(1040) =>
> 64.135.41.80(443) Seq=23649467-23649467 Ack=0 Win=32768 Len=48
> 12/17/2005 10:31:48.300 - TCP: .A..S., 64.135.41.80(443) =>
> 192.168.55.101(1040) Seq=53363102-53363102 Ack=23649468 Win=8760 Len=44
> 12/17/2005 10:31:48.711 - CesProxy: Accept on port 443, IsWinsock 0,
> hResult 0
> 12/17/2005 10:31:56.947 - CesProxy: Accept on port 990, IsWinsock 1,
> hResult 0
> 12/17/2005 10:31:56.947 - TCP: ....S., 192.168.55.100(1037) =>
> 192.168.55.101(990) Seq=53371744-53371744 Ack=0 Win=8192 Len=44
> 12/17/2005 10:31:56.947 - TCP: .A..S., 192.168.55.101(990) =>
> 192.168.55.100(1037) Seq=25833578-25833578 Ack=53371745 Win=32768
> Len=44
> 12/17/2005 10:32:08.701 - CesProxy: recv failed on Win socket 990, err
> = 10054
> 12/17/2005 10:32:08.701 - CesProxy: Close Win socket 990
> 12/17/2005 10:32:08.701 - CesProxy: Close PPP socket 990
> 12/17/2005 10:32:08.711 - TCP: ...R.., 192.168.55.100(1037) =>
> 192.168.55.101(990) Seq=53372253-53372253 Ack=25833723 Win=0 Len=40
> 12/17/2005 10:32:08.711 - CesProxy: recv failed on PPP socket 990, err
> = 10004
> 12/17/2005 10:32:48.370 - CesProxy: Accept on port 990, IsWinsock 1,
> hResult 0
> 12/17/2005 10:32:48.370 - TCP: ....S., 192.168.55.100(1038) =>
> 192.168.55.101(990) Seq=53423138-53423138 Ack=0 Win=8192 Len=44
> 12/17/2005 10:32:48.370 - TCP: .A..S., 192.168.55.101(990) =>
> 192.168.55.100(1038) Seq=38604781-38604781 Ack=53423139 Win=32768
> Len=44
> 12/17/2005 10:32:49.042 - CesProxy: recv failed on Win socket 990, err
> = 10054
> 12/17/2005 10:32:49.042 - CesProxy: Close Win socket 990
> 12/17/2005 10:32:49.042 - CesProxy: Close PPP socket 990
> 12/17/2005 10:32:49.042 - TCP: ...R.., 192.168.55.100(1038) =>
> 192.168.55.101(990) Seq=53423627-53423627 Ack=21861728 Win=0 Len=40
> 12/17/2005 10:32:49.042 - CesProxy: recv failed on PPP socket 990, err
> = 10004
> 12/17/2005 10:33:08.711 - TCP: ....S., 192.168.55.101(1042) =>
> 192.168.55.100(5533) Seq=43703622-43703622 Ack=0 Win=32768 Len=48
> 12/17/2005 10:33:08.721 - Proxy: Connection Attempt on port 5533, dest
> ip 0x6437a8c0
> 12/17/2005 10:33:08.721 - TCP: .A..S., 192.168.55.100(5533) =>
> 192.168.55.101(1042) Seq=53443477-53443477 Ack=43703623 Win=8760 Len=44
> 12/17/2005 10:33:09.583 - CesProxy: Accept on port 5533, IsWinsock 0,
> hResult 0
>

The PPC will indeed resolve the name on the PC when cradled.

--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no rights.


"StoneColdStunner" <> wrote in message
news: oups.com...
> Carl
>
> If the unit is going to try and contact 64.135.41.80 via
> 192.168.55.101/101 then there will be problem. That device is a NAT on
> our firewall. It isn't possible to go out the firewall to use a public
> NAT. Firewall blocks this. If we want to access "NATS" we just use
> the 10.x.x.x.x IP's or its internal dns name. We have split dns.
> Internal DNS has the same names that the external DNS has. So
> Webmail.com might be 192.168.1.1 using internal dns, where webmail.com
> would be 64.1.1.1 if someone called it via the internet.
>
> I bet if i change this to a name, it would probably work provided the
> PPC pulls dns from my local pc when docked.
>
> Thanks for the insight
>

You can store the IP address in the device's local host table.

--
Carl Wolz [MSFT]
This Posting is provided "AS IS" with no warranties, and confers no rights.


"StoneColdStunner" <> wrote in message
news: ups.com...
> Yep, using the name not the IP solved my USB problem. The one time I
> need to use a name rather than an IP! Not a big fan of trusting
> provider DNS servers, hence the IP not that name.
>