IPAQ 3635 will not connect to Desktop with Activesync

I am using a desktop computer with Windows 98 SE and ActiveSync 3.8 with an
IPAQ 3635. I connect via the USB plug from the IPAQ cradle. I was able to
successfully synchronize last year using 3.7.1 but this year cannot make the
connection. When I plug in the IPAQ, the desktop tries to connect but I get
the error message: Your device was not detected The Status of the USB Port
says “USB is available�.
The Activesynch spinner grays out. At the same time, I can
look at the Activesync on the IPAQ and it will say “synchronizing with PC�.
If I go into My Devices when I first plug in the IPAQ, it will list the
“Compaq IPAQ USB Sync� under Windows CE USB Devices. I’ve looked at Device
Manager at USB devices (also in safe mode) and have deleted “Unknown Device�
but Activesync still doesn’t work.

I have searched Microsoft and Compaq forums for possible remedies. I am
running Norton Internet Security 2005 and have gone in and seen that
Activesync is one of the programs permitted and have set up the General Rule
for Activesync as suggested in several forums. I’ve also tried turning the
firewall off. I was running the same firewall last year when I was able to
successfully synchronize. I’ve also tried uninstalling Activesynch 3.8 and
reinstalling 3.7.1. I’ve done multiple soft resets, one hard reset, on the
IPAQ but it still doesn’t work.

Here is the wcescomm.log from my last unsuccessful attempt. This time the
message said the mobile device was not compatible with the version of
Microsoft Activesync being used.

02/17/2006 20:00:17.040 - Windows CE Services (3.8.5004) Communication
Logging.
02/17/2006 20:00:17.090 - Windows CE Services Communication started.
02/17/2006 20:00:17.260 - ConnectWizard: Auto-started - no serial device
defined.
02/17/2006 20:00:17.530 - Connection: Prep for a new socket connection.
02/17/2006 20:01:57.550 - USB: Event 32768, name
\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
02/17/2006 20:01:57.550 - USB: Device Arrival notification
02/17/2006 20:01:57.660 - UsbComm: Open device <USB>.
02/17/2006 20:01:57.660 - ConnectWizard: Connection Wizard ended.
02/17/2006 20:01:57.660 - UsbComm: Change DTR to 1.
02/17/2006 20:01:57.660 - Serial: Starting device detection at 115200.
02/17/2006 20:01:57.660 - UsbComm: Change DTR to 1.
02/17/2006 20:01:57.660 - AutobaudDetect: Found character <0x00>.
02/17/2006 20:01:59.040 - AutobaudDetect: Found character <C>.
02/17/2006 20:01:59.040 - AutobaudDetect: Found character <L>.
02/17/2006 20:01:59.040 - AutobaudDetect: Found character <I>.
02/17/2006 20:01:59.040 - AutobaudDetect: Found character <E>.
02/17/2006 20:01:59.040 - AutobaudDetect: Found character <N>.
02/17/2006 20:01:59.040 - AutobaudDetect: Found character <T>.
02/17/2006 20:01:59.040 - Serial: Unimodem handshake at 115200.
02/17/2006 20:01:59.040 - Proxy: Change connection state 1.
02/17/2006 20:01:59.040 - Proxy: Created dynamic proxy on port 1026.
02/17/2006 20:01:59.360 - TCP: ....S., 192.168.55.101(1025) =>
192.168.55.100(5679) Seq=17738-17738 Ack=0 Win=32768 Len=64
02/17/2006 20:01:59.360 - Proxy: Connection Attempt on port 5679, dest ip
0x6437a8c0
02/17/2006 20:01:59.360 - TCP: .A..S., 192.168.55.100(5679) =>
192.168.55.101(1025) Seq=8256869-8256869 Ack=17739 Win=8760 Len=44
02/17/2006 20:02:00.300 - TCP: ....S., 192.168.55.101(1026) =>
192.168.55.100(7438) Seq=18672-18672 Ack=0 Win=32768 Len=64
02/17/2006 20:02:00.300 - Proxy: Connection Attempt on port 7438, dest ip
0x6437a8c0
02/17/2006 20:02:00.300 - TCP: .A..S., 192.168.55.100(7438) =>
192.168.55.101(1026) Seq=8257804-8257804 Ack=18673 Win=8760 Len=44
02/17/2006 20:02:00.350 - CesProxy: Accept on port 5679, IsWinsock 0,
hResult 0
02/17/2006 20:02:00.350 - CesProxy: Accept on port 7438, IsWinsock 0,
hResult 0
02/17/2006 20:02:00.790 - Connection: Accepted connection from IP address
127.0.0.1:1337.
02/17/2006 20:02:00.790 - Started desktop passthru TCP2UDP component
02/17/2006 20:02:05.460 - CesProxy: recv failed on Win socket 5679, err =
10054
02/17/2006 20:02:05.460 - CesProxy: Close PPP socket 5679
02/17/2006 20:02:05.460 - TCP: ...R.., 192.168.55.100(5679) =>
192.168.55.101(1025) Seq=8256870-8256870 Ack=17743 Win=0 Len=40
02/17/2006 20:02:05.460 - CesProxy: Close Win socket 5679
02/17/2006 20:02:05.460 - CesProxy: recv failed on PPP socket 5679, err =
10004
02/17/2006 20:02:05.460 - CesProxy: recv failed on Win socket 7438, err =
10054
02/17/2006 20:02:05.460 - CesProxy: Close PPP socket 7438
02/17/2006 20:02:05.460 - TCP: ...R.., 192.168.55.100(7438) =>
192.168.55.101(1026) Seq=8257805-8257805 Ack=17743 Win=0 Len=40
02/17/2006 20:02:05.460 - CesProxy: Close Win socket 7438
02/17/2006 20:02:05.520 - CesProxy: recv failed on PPP socket 7438, err =
10004
02/17/2006 20:02:05.520 - Shut down desktop passthru TCP2UDP component
02/17/2006 20:02:05.520 - Connection: Prep for a new socket connection.
02/17/2006 20:02:22.650 - ConnectWizard: User started Connection Wizard.
02/17/2006 20:02:22.650 - UsbComm: Change DTR to 0.
02/17/2006 20:02:22.650 - Proxy: Change connection state 0.
02/17/2006 20:02:22.650 - CesProxy: Close PPP socket 7438
02/17/2006 20:02:22.650 - UsbComm: Closed device.
02/17/2006 20:02:22.650 - CesProxy: Accept on port 7438, IsWinsock 0,
hResult 80072714
02/17/2006 20:02:22.650 - CesProxy: Close PPP socket 5679
02/17/2006 20:02:22.650 - CesProxy: Accept on port 5679, IsWinsock 0,
hResult 80072714
02/17/2006 20:02:22.650 - CesProxy: Close Win socket 1026
02/17/2006 20:02:22.650 - CesProxy: Accept on port 1026, IsWinsock 1,
hResult 80072736
02/17/2006 20:02:22.650 - CesProxy: Close Win socket 990
02/17/2006 20:02:22.650 - CesProxy: Accept on port 990, IsWinsock 1, hResult
80072736
02/17/2006 20:02:26.280 - Start scan for serial devices.
02/17/2006 20:02:26.390 - COM1 - Available.
02/17/2006 20:02:26.390 - COM2 - Not installed.
02/17/2006 20:02:26.390 - COM4 - Available.
02/17/2006 20:02:26.390 - COM5 - Available.
02/17/2006 20:02:26.390 - End scan for serial devices.
02/17/2006 20:02:26.390 - ConnectWizard: Scan \\.\COM1 for CE device.
02/17/2006 20:02:26.660 - ComSerial: Open device <\\.\COM1>.
02/17/2006 20:02:26.660 - AutobaudDetect: Start.
02/17/2006 20:02:31.660 - AutobaudDetect: CTS serial pin is high and RSLD
serial pin is low, possible cable problem.
02/17/2006 20:02:31.660 - AutobaudDetect: DSR serial pin is high and RSLD
serial pin is low, possible cable problem.
02/17/2006 20:02:31.660 - AutobaudDetect: No device found, detection failed.
02/17/2006 20:02:31.660 - ComSerial: Closed device.
02/17/2006 20:02:31.660 - ConnectWizard: Scan \\.\COM4 for CE device.
02/17/2006 20:02:31.940 - ComSerial: Open device <\\.\COM4>.
02/17/2006 20:02:31.940 - AutobaudDetect: Start.
02/17/2006 20:02:36.930 - AutobaudDetect: CTS serial pin is high and RSLD
serial pin is low, possible cable problem.
02/17/2006 20:02:36.930 - AutobaudDetect: DSR serial pin is high and RSLD
serial pin is low, possible cable problem.
02/17/2006 20:02:36.930 - AutobaudDetect: No device found, detection failed.
02/17/2006 20:02:36.930 - ComSerial: Closed device.
02/17/2006 20:02:36.930 - ConnectWizard: Scan \\.\COM5 for CE device.
02/17/2006 20:02:37.150 - ComSerial: Open device <\\.\COM5>.
02/17/2006 20:02:37.150 - AutobaudDetect: Start.
02/17/2006 20:02:42.150 - AutobaudDetect: CTS serial pin is high and RSLD
serial pin is low, possible cable problem.
02/17/2006 20:02:42.150 - AutobaudDetect: DSR serial pin is high and RSLD
serial pin is low, possible cable problem.
02/17/2006 20:02:42.150 - AutobaudDetect: No device found, detection failed.
02/17/2006 20:02:42.150 - ComSerial: Closed device.
02/17/2006 20:02:58.350 - ConnectWizard: Failed to find device.
02/17/2006 20:02:58.350 - ConnectWizard: Connection Wizard ended.

I’ve also tried synchronizing the above IPAQ to an IBM ThinkPad running
Windows 2000 Professional, Symantec Client Firewall, and Activesync 3.8. I
set up the Symantec Client Firewall so that Activesync is a program that is
permitted and set up the general rule for Activesync. I get the same error
message from Activesync (“Your device was not detected�).

Is this an Activesync problem or an IPAQ problem? What else can I try?

On Fri, 17 Feb 2006 21:12:28 -0800, "Mary"
<> wrote:

>I am using a desktop computer with Windows 98 SE and ActiveSync 3.8 with an
>IPAQ 3635. I connect via the USB plug from the IPAQ cradle. I was able to
>successfully synchronize last year using 3.7.1 but this year cannot make the
>connection. When I plug in the IPAQ, the desktop tries to connect but I get
>the error message: Your device was not detected The Status of the USB Port
>says “USB is available”.
> The Activesynch spinner grays out. At the same time, I can
>look at the Activesync on the IPAQ and it will say “synchronizing with PC”.
>If I go into My Devices when I first plug in the IPAQ, it will list the
>“Compaq IPAQ USB Sync” under Windows CE USB Devices. I’ve looked at Device
>Manager at USB devices (also in safe mode) and have deleted “Unknown Device”
>but Activesync still doesn’t work.
>
>I have searched Microsoft and Compaq forums for possible remedies. I am
>running Norton Internet Security 2005 and have gone in and seen that
>Activesync is one of the programs permitted and have set up the General Rule
>for Activesync as suggested in several forums. I’ve also tried turning the
>firewall off. I was running the same firewall last year when I was able to
>successfully synchronize. I’ve also tried uninstalling Activesynch 3.8 and
>reinstalling 3.7.1. I’ve done multiple soft resets, one hard reset, on the
>IPAQ but it still doesn’t work.

It looks as though communications are still being blocked. Ensure that
wcescomm.exe, wcesmgr.exe, ceappmgr.exe, and rapimgr.exe are listed in
the rules as having full functionality (server mode)

--
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.

"Rob Borek [MS MVP]" wrote:

> On Fri, 17 Feb 2006 21:12:28 -0800, "Mary"
> <> wrote:
>
> >I am using a desktop computer with Windows 98 SE and ActiveSync 3.8 with an
> >IPAQ 3635. I connect via the USB plug from the IPAQ cradle. I was able to
> >successfully synchronize last year using 3.7.1 but this year cannot make the
> >connection. When I plug in the IPAQ, the desktop tries to connect but I get
> >the error message: Your device was not detected The Status of the USB Port
> >says “USB is available�.
> > The Activesynch spinner grays out. At the same time, I can
> >look at the Activesync on the IPAQ and it will say “synchronizing with PC�.
> >If I go into My Devices when I first plug in the IPAQ, it will list the
> >“Compaq IPAQ USB Sync� under Windows CE USB Devices. I’ve looked at Device
> >Manager at USB devices (also in safe mode) and have deleted “Unknown Device�
> >but Activesync still doesn’t work.
> >
> >I have searched Microsoft and Compaq forums for possible remedies. I am
> >running Norton Internet Security 2005 and have gone in and seen that
> >Activesync is one of the programs permitted and have set up the General Rule
> >for Activesync as suggested in several forums. I’ve also tried turning the
> >firewall off. I was running the same firewall last year when I was able to
> >successfully synchronize. I’ve also tried uninstalling Activesynch 3.8 and
> >reinstalling 3.7.1. I’ve done multiple soft resets, one hard reset, on the
> >IPAQ but it still doesn’t work.
>
> It looks as though communications are still being blocked. Ensure that
> wcescomm.exe, wcesmgr.exe, ceappmgr.exe, and rapimgr.exe are listed in
> the rules as having full functionality (server mode)
>
> --
> 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.
>

I added CEAPPMGR.com to the Programs in NIS 2005. I'm not sure what you
mean by "having full functionality" but the Activesync rules in NIS are set
up as follows:

The following rules apply to WCESCOMM.exe and WCESMGR.exe
Microsoft ActiveSync HTTP Outbound Rule
PERMIT; TO OTHER COMPUTERS;ANY COMPUTER; TCP; REMOTE HTTP (PORT 80) REMOTE
PORT 81, 82, 83, REMOTE HTTPS (PORT 443), 1080, 8080, 8088, 11523
ActiveSync TCP-IN Rule
PERMIT; FROM OTHER COMPUTERS;ANY COMPUTER; TCP; LOCAL PORTS 1-65535
Microsoft ActiveSync DNS Rule
PERMIT; TO AND FROM OTHER COMPUTERS;ANY COMPUTER; TCP; REMOTE DOMAIN (PORT 53)

For CEAPPMGR I made up the following rule:
PERMIT; TO AND FROM OTHER COMPUTERS;ANY COMPUTER; TCP AND UDP; LOCAL 5678,
5679 (why?? From something I saw on one of the forums)

I could not find RAPIMGR anywhere on my computer.

When I tried Activesync again, I got the following error message.

“Microsoft ActiveSync cannot recognize this device for one of two reasons:

The device was not connected properly . . .

The device is not a Smartphone of Pocket PC. . .�

The WCESCOMM.LOG file looked like this:

02/18/2006 11:27:30.740 - Windows CE Services (3.8.5004) Communication
Logging.
02/18/2006 11:27:30.740 - Windows CE Services Communication started.
02/18/2006 11:27:30.960 - Connection: Prep for a new socket connection.
02/18/2006 11:28:14.960 - USB: Event 32768, name
\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
02/18/2006 11:28:14.960 - USB: Device Arrival notification
02/18/2006 11:28:14.960 - UsbComm: Open device <USB>.
02/18/2006 11:28:15.010 - UsbComm: Change DTR to 1.
02/18/2006 11:28:15.010 - Serial: Starting device detection at 115200.
02/18/2006 11:28:15.010 - UsbComm: Change DTR to 1.
02/18/2006 11:28:15.010 - AutobaudDetect: Found character <0x00>.
02/18/2006 11:28:45.060 - Proxy: Timeout waiting for CLIENT message.
02/18/2006 11:31:37.740 - USB: Event 32772, name
\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
02/18/2006 11:31:37.740 - USB: Device Remove Complete notification
02/18/2006 11:31:37.740 - UsbComm: Change DTR to 0.
02/18/2006 11:31:37.910 - UsbComm: Closed device.

What else can I try?

Thank you.

On Sat, 18 Feb 2006 13:19:28 -0800, "Mary"
<> wrote:

>I added CEAPPMGR.com to the Programs in NIS 2005. I'm not sure what you
>mean by "having full functionality" but the Activesync rules in NIS are set
>up as follows:
>
>The following rules apply to WCESCOMM.exe and WCESMGR.exe
>Microsoft ActiveSync HTTP Outbound Rule
>PERMIT; TO OTHER COMPUTERS;ANY COMPUTER; TCP; REMOTE HTTP (PORT 80) REMOTE
>PORT 81, 82, 83, REMOTE HTTPS (PORT 443), 1080, 8080, 8088, 11523
>ActiveSync TCP-IN Rule
>PERMIT; FROM OTHER COMPUTERS;ANY COMPUTER; TCP; LOCAL PORTS 1-65535
>Microsoft ActiveSync DNS Rule
>PERMIT; TO AND FROM OTHER COMPUTERS;ANY COMPUTER; TCP; REMOTE DOMAIN (PORT 53)
>
>For CEAPPMGR I made up the following rule:
>PERMIT; TO AND FROM OTHER COMPUTERS;ANY COMPUTER; TCP AND UDP; LOCAL 5678,
>5679 (why?? From something I saw on one of the forums)
>
>I could not find RAPIMGR anywhere on my computer.

Sorry - don't worry about RAPIMGR, that's part of ActiveSync 4.x.

The ports you need open are 990, 999, 5678, 5679, all TCP. If you can
set a rule to allow inbound connections from any computer to your
computer on those ports you should be OK.

--
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.

I added the ports 990 and 999 to the ActiveSync rule that I created. It made
a difference although I still cannot connect. After several minutes of
spinning green and the message "Connecting" in the Activesync window, I
simply got "No partnerships Not connected" No error message. When I looked
at NIS, the WCESCOMM and WCESMGR
"internet access" rules had reverted to Automatic from the Custom I had set
up. The CEAPPMGR still had the Custom rule I had set up.

Here is the wcescomm.log from my last attempt to synch.
02/19/2006 17:08:05.000 - Windows CE Services (3.8.5004) Communication
Logging.
02/19/2006 17:08:05.220 - Windows CE Services Communication started.
02/19/2006 17:08:08.240 - Connection: Prep for a new socket connection.
02/19/2006 17:11:52.120 - USB: Event 32768, name
\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
02/19/2006 17:11:52.120 - USB: Device Arrival notification
02/19/2006 17:11:52.120 - UsbComm: Open device <USB>.
02/19/2006 17:11:52.120 - UsbComm: Change DTR to 1.
02/19/2006 17:11:52.120 - Serial: Starting device detection at 115200.
02/19/2006 17:11:52.180 - UsbComm: Change DTR to 1.
02/19/2006 17:11:52.180 - AutobaudDetect: Found character <0x00>.
02/19/2006 17:11:53.710 - AutobaudDetect: Found character <C>.
02/19/2006 17:11:53.710 - AutobaudDetect: Found character <L>.
02/19/2006 17:11:53.710 - AutobaudDetect: Found character <I>.
02/19/2006 17:11:53.710 - AutobaudDetect: Found character <E>.
02/19/2006 17:11:53.710 - AutobaudDetect: Found character <N>.
02/19/2006 17:11:53.710 - AutobaudDetect: Found character <T>.
02/19/2006 17:11:53.710 - Serial: Unimodem handshake at 115200.
02/19/2006 17:11:53.770 - Proxy: Change connection state 1.
02/19/2006 17:11:53.770 - Proxy: Created dynamic proxy on port 1026.
02/19/2006 17:15:03.430 - USB: Event 32772, name
\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
02/19/2006 17:15:03.480 - USB: Device Remove Complete notification
02/19/2006 17:15:03.480 - UsbComm: Change DTR to 0.
02/19/2006 17:15:03.480 - Proxy: Change connection state 0.
02/19/2006 17:15:03.480 - CesProxy: Close Win socket 1026
02/19/2006 17:15:03.480 - CesProxy: Accept on port 1026, IsWinsock 1,
hResult 80072736
02/19/2006 17:15:03.480 - CesProxy: Close Win socket 990
02/19/2006 17:15:03.480 - CesProxy: Accept on port 990, IsWinsock 1, hResult
80072736
02/19/2006 17:15:03.480 - UsbComm: Closed device.

Would it be a worthwhile test to uninstall NIS and try to run Activesync?
I've tried to turn off NIS but Activesync still doesn't work. Although I
would not permanently want to run without NIS, I'd be willing to try this as
a troubleshooting step to see if the firewall is the problem.

"Rob Borek [MS MVP]" wrote:

> On Sat, 18 Feb 2006 13:19:28 -0800, "Mary"
> <> wrote:
>
> >I added CEAPPMGR.com to the Programs in NIS 2005. I'm not sure what you
> >mean by "having full functionality" but the Activesync rules in NIS are set
> >up as follows:
> >
> >The following rules apply to WCESCOMM.exe and WCESMGR.exe
> >Microsoft ActiveSync HTTP Outbound Rule
> >PERMIT; TO OTHER COMPUTERS;ANY COMPUTER; TCP; REMOTE HTTP (PORT 80) REMOTE
> >PORT 81, 82, 83, REMOTE HTTPS (PORT 443), 1080, 8080, 8088, 11523
> >ActiveSync TCP-IN Rule
> >PERMIT; FROM OTHER COMPUTERS;ANY COMPUTER; TCP; LOCAL PORTS 1-65535
> >Microsoft ActiveSync DNS Rule
> >PERMIT; TO AND FROM OTHER COMPUTERS;ANY COMPUTER; TCP; REMOTE DOMAIN (PORT 53)
> >
> >For CEAPPMGR I made up the following rule:
> >PERMIT; TO AND FROM OTHER COMPUTERS;ANY COMPUTER; TCP AND UDP; LOCAL 5678,
> >5679 (why?? From something I saw on one of the forums)
> >
> >I could not find RAPIMGR anywhere on my computer.
>
> Sorry - don't worry about RAPIMGR, that's part of ActiveSync 4.x.
>
> The ports you need open are 990, 999, 5678, 5679, all TCP. If you can
> set a rule to allow inbound connections from any computer to your
> computer on those ports you should be OK.
>
> --
> 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 Sun, 19 Feb 2006 17:40:15 -0800, "Mary"
<> wrote:

>I added the ports 990 and 999 to the ActiveSync rule that I created. It made
>a difference although I still cannot connect. After several minutes of
>spinning green and the message "Connecting" in the Activesync window, I
>simply got "No partnerships Not connected" No error message. When I looked
>at NIS, the WCESCOMM and WCESMGR
>"internet access" rules had reverted to Automatic from the Custom I had set
>up. The CEAPPMGR still had the Custom rule I had set up.
<snip>
>Would it be a worthwhile test to uninstall NIS and try to run Activesync?
>I've tried to turn off NIS but Activesync still doesn't work. Although I
>would not permanently want to run without NIS, I'd be willing to try this as
>a troubleshooting step to see if the firewall is the problem.

Yes, please try uninstalling NIS. If it works, we know the problem is
with NIS, and we can work from there.

--
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.

I uninstalled NIS 2005, rebooted, and tried Activesync again. After green
spinning for quite a while, all stopped with the message:

No Partnerships Not connected

No other error messages.

Here is the wcescomm.log
02/27/2006 10:49:28.530 - Windows CE Services (3.8.5004) Communication
Logging.
02/27/2006 10:49:28.750 - Windows CE Services Communication started.
02/27/2006 10:49:30.070 - Connection: Prep for a new socket connection.
02/27/2006 10:50:17.800 - ConnectWizard: User started Connection Wizard.
02/27/2006 10:50:58.060 - USB: Event 32768, name
\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
02/27/2006 10:50:58.060 - USB: Device Arrival notification
02/27/2006 10:50:58.060 - UsbComm: Open device <USB>.
02/27/2006 10:50:58.060 - ConnectWizard: Connection Wizard ended.
02/27/2006 10:50:58.120 - Serial: Starting device detection at 115200.
02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1 failed. err = 170
02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1.
02/27/2006 10:50:58.120 - Serial: Starting device detection at 115200.
02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1.
02/27/2006 10:50:58.120 - AutobaudDetect: Found character <0x00>.
02/27/2006 10:50:59.490 - AutobaudDetect: Found character <C>.
02/27/2006 10:50:59.490 - AutobaudDetect: Found character <L>.
02/27/2006 10:50:59.490 - AutobaudDetect: Found character <I>.
02/27/2006 10:50:59.490 - AutobaudDetect: Found character <E>.
02/27/2006 10:50:59.490 - AutobaudDetect: Found character <N>.
02/27/2006 10:50:59.490 - AutobaudDetect: Found character <T>.
02/27/2006 10:50:59.490 - Serial: Unimodem handshake at 115200.
02/27/2006 10:50:59.490 - Proxy: Change connection state 1.
02/27/2006 10:50:59.490 - Proxy: Created dynamic proxy on port 1026.
02/27/2006 10:56:05.210 - USB: Event 32772, name
\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
02/27/2006 10:56:05.210 - USB: Device Remove Complete notification
02/27/2006 10:56:05.210 - UsbComm: Change DTR to 0.
02/27/2006 10:56:05.210 - Proxy: Change connection state 0.
02/27/2006 10:56:05.210 - UsbComm: Closed device.
02/27/2006 10:56:05.210 - CesProxy: Close Win socket 1026
02/27/2006 10:56:05.210 - CesProxy: Accept on port 1026, IsWinsock 1,
hResult 80072736
02/27/2006 10:56:05.210 - CesProxy: Close Win socket 990
02/27/2006 10:56:05.210 - CesProxy: Accept on port 990, IsWinsock 1, hResult
80072736

Is this a USB driver problem?


"Rob Borek [MS MVP]" wrote:

> On Sun, 19 Feb 2006 17:40:15 -0800, "Mary"
> <> wrote:
>
> >I added the ports 990 and 999 to the ActiveSync rule that I created. It made
> >a difference although I still cannot connect. After several minutes of
> >spinning green and the message "Connecting" in the Activesync window, I
> >simply got "No partnerships Not connected" No error message. When I looked
> >at NIS, the WCESCOMM and WCESMGR
> >"internet access" rules had reverted to Automatic from the Custom I had set
> >up. The CEAPPMGR still had the Custom rule I had set up.
> <snip>
> >Would it be a worthwhile test to uninstall NIS and try to run Activesync?
> >I've tried to turn off NIS but Activesync still doesn't work. Although I
> >would not permanently want to run without NIS, I'd be willing to try this as
> >a troubleshooting step to see if the firewall is the problem.
>
> Yes, please try uninstalling NIS. If it works, we know the problem is
> with NIS, and we can work from there.
>
> --
> 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 Mon, 27 Feb 2006 14:41:03 -0800, "Mary"
<> wrote:

>I uninstalled NIS 2005, rebooted, and tried Activesync again. After green
>spinning for quite a while, all stopped with the message:
>
>No Partnerships Not connected
>
>No other error messages.
>
>Here is the wcescomm.log
>02/27/2006 10:49:28.530 - Windows CE Services (3.8.5004) Communication
>Logging.
>02/27/2006 10:49:28.750 - Windows CE Services Communication started.
>02/27/2006 10:49:30.070 - Connection: Prep for a new socket connection.
>02/27/2006 10:50:17.800 - ConnectWizard: User started Connection Wizard.
>02/27/2006 10:50:58.060 - USB: Event 32768, name
>\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
>02/27/2006 10:50:58.060 - USB: Device Arrival notification
>02/27/2006 10:50:58.060 - UsbComm: Open device <USB>.
>02/27/2006 10:50:58.060 - ConnectWizard: Connection Wizard ended.
>02/27/2006 10:50:58.120 - Serial: Starting device detection at 115200.
>02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1 failed. err = 170
>02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1.

There's a USB error here - can you try going into Device Manager and
deleting the device while it's in the cradle, then unplug the device
and reconnect it.

--
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.

It's probably not that. Look for errors in the wcesmgr.log file.



Also, is there something like "COomSession:oInitOOMSession: hr =
0x80004005 - OomSession.cpp" in the wcesmgr.log? Than NIS installed a virus
blocker. Uninstalling NIS doesn't clean this up either.


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



"Rob Borek [MS MVP]" <> wrote in message
news:...
> On Mon, 27 Feb 2006 14:41:03 -0800, "Mary"
> <> wrote:
>
>>I uninstalled NIS 2005, rebooted, and tried Activesync again. After green
>>spinning for quite a while, all stopped with the message:
>>
>>No Partnerships Not connected
>>
>>No other error messages.
>>
>>Here is the wcescomm.log
>>02/27/2006 10:49:28.530 - Windows CE Services (3.8.5004) Communication
>>Logging.
>>02/27/2006 10:49:28.750 - Windows CE Services Communication started.
>>02/27/2006 10:49:30.070 - Connection: Prep for a new socket connection.
>>02/27/2006 10:50:17.800 - ConnectWizard: User started Connection Wizard.
>>02/27/2006 10:50:58.060 - USB: Event 32768, name
>>\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
>>02/27/2006 10:50:58.060 - USB: Device Arrival notification
>>02/27/2006 10:50:58.060 - UsbComm: Open device <USB>.
>>02/27/2006 10:50:58.060 - ConnectWizard: Connection Wizard ended.
>>02/27/2006 10:50:58.120 - Serial: Starting device detection at 115200.
>>02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1 failed. err = 170
>>02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1.
>
> There's a USB error here - can you try going into Device Manager and
> deleting the device while it's in the cradle, then unplug the device
> and reconnect it.
>
> --
> 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.

I went into Device Manager and deleted the IPAQ. Now the Device Manager sees
the IPAQ as an "Unknown Device" and of course, Activesync doesn't do anything
now when I plug in the IPAQ (no spinning green). I went into safe mode and
deleted "Unknown Device" and one of two "Compaq IPAQ USB Sync" under Windows
CE USB Devices.

Is this a USB driver problem? Where can I download the latest? I looked at
the HP/Compaq website but didn't see any.

I also looked at the wcesmgr.log. For the corresponding attempt to use
activesync the entries were:

2006-02-27 10:50:10 FF00CE71 -


**** ActiveSync (3.8.5004 RETAIL) started, Cmd line: ''
2006-02-27 11:00:37 FF00CE71 - **** ActiveSync exiting

This was typical of all the other previous attempts to use activesync. No
messages like the one shown below.

"Carl Wolz [MSFT]" wrote:

> It's probably not that. Look for errors in the wcesmgr.log file.
>
>
>
> Also, is there something like "COomSession:oInitOOMSession: hr =
> 0x80004005 - OomSession.cpp" in the wcesmgr.log? Than NIS installed a virus
> blocker. Uninstalling NIS doesn't clean this up either.
>
>
> --
> Carl Wolz [MSFT]
> This Posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Rob Borek [MS MVP]" <> wrote in message
> news:...
> > On Mon, 27 Feb 2006 14:41:03 -0800, "Mary"
> > <> wrote:
> >
> >>I uninstalled NIS 2005, rebooted, and tried Activesync again. After green
> >>spinning for quite a while, all stopped with the message:
> >>
> >>No Partnerships Not connected
> >>
> >>No other error messages.
> >>
> >>Here is the wcescomm.log
> >>02/27/2006 10:49:28.530 - Windows CE Services (3.8.5004) Communication
> >>Logging.
> >>02/27/2006 10:49:28.750 - Windows CE Services Communication started.
> >>02/27/2006 10:49:30.070 - Connection: Prep for a new socket connection.
> >>02/27/2006 10:50:17.800 - ConnectWizard: User started Connection Wizard.
> >>02/27/2006 10:50:58.060 - USB: Event 32768, name
> >>\\.\0000000000000008#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
> >>02/27/2006 10:50:58.060 - USB: Device Arrival notification
> >>02/27/2006 10:50:58.060 - UsbComm: Open device <USB>.
> >>02/27/2006 10:50:58.060 - ConnectWizard: Connection Wizard ended.
> >>02/27/2006 10:50:58.120 - Serial: Starting device detection at 115200.
> >>02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1 failed. err = 170
> >>02/27/2006 10:50:58.120 - UsbComm: Change DTR to 1.
> >
> > There's a USB error here - can you try going into Device Manager and
> > deleting the device while it's in the cradle, then unplug the device
> > and reconnect it.
> >
> > --
> > 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.
>
>
>