AJL
08-25-2004, 09:22 AM
We have a Windows CE powered Hand held device configured via com1 with Windows NT 4.0 Sp6 (goda stay there as well!!)
When the machine logs on it's fine active sync see's the device no problem, uncradle the HHT and re-seat it Active pops up the following.
Microsoft ActiveSync cannot recognize the device for one of two reasons:
1 the device was not connected properly (then advice on starting over)
2 The device is not a smart phone or pocket PC. (it isn’t)
Now the difference with this build to others we have is the Windows NT 4.0 sp6 build in running inside a Virtual PC we are looking for away to continue this build without having to invest in upgrading the software that runs on the build.
I expect there could be a virtual pc issue but, if I click on the get connected button in active sync and then click cancel it connects to the HHT really funny problem log from active sync below, would appreciate any input..
"WCESCOMM.LOG"
08/25/2004 10:55:43.821 - Windows CE Services (3.7.4034) Communication Logging.
08/25/2004 10:55:43.861 - Logging file auto-purge after a successful device connection.
08/25/2004 10:55:43.901 - Connection: Process connection from IP address 127.0.0.1:1117.
08/25/2004 10:55:44.162 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
08/25/2004 10:55:44.202 - TCP: ....S., 192.168.55.100(1025) => 192.168.55.101(990) Seq=1541636-1541636 Ack=0 Win=8192 Len=44
08/25/2004 10:55:44.853 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1025) Seq=3055182-3055182 Ack=1541637 Win=8760 Len=44
08/25/2004 10:55:45.734 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
08/25/2004 10:55:45.834 - TCP: ....S., 192.168.55.100(1026) => 192.168.55.101(990) Seq=1543209-1543209 Ack=0 Win=8192 Len=44
08/25/2004 10:55:46.185 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1026) Seq=3056532-3056532 Ack=1543210 Win=8760 Len=44
08/25/2004 10:55:47.416 - CesProxy: recv failed on Win socket 990, err = 10054
08/25/2004 10:55:47.476 - CesProxy: Close Win socket 990
08/25/2004 10:55:47.516 - CesProxy: Close PPP socket 990
08/25/2004 10:55:47.557 - TCP: ...R.., 192.168.55.100(1025) => 192.168.55.101(990) Seq=1541827-1541827 Ack=3055223 Win=0 Len=40
08/25/2004 10:55:47.607 - CesProxy: recv failed on PPP socket 990, err = 10004
08/25/2004 10:56:44.248 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
08/25/2004 10:56:44.288 - TCP: ....S., 192.168.55.100(1027) => 192.168.55.101(990) Seq=1601723-1601723 Ack=0 Win=8192 Len=44
08/25/2004 10:56:44.498 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1027) Seq=3115033-3115033 Ack=1601724 Win=8760 Len=44
When the machine logs on it's fine active sync see's the device no problem, uncradle the HHT and re-seat it Active pops up the following.
Microsoft ActiveSync cannot recognize the device for one of two reasons:
1 the device was not connected properly (then advice on starting over)
2 The device is not a smart phone or pocket PC. (it isn’t)
Now the difference with this build to others we have is the Windows NT 4.0 sp6 build in running inside a Virtual PC we are looking for away to continue this build without having to invest in upgrading the software that runs on the build.
I expect there could be a virtual pc issue but, if I click on the get connected button in active sync and then click cancel it connects to the HHT really funny problem log from active sync below, would appreciate any input..
"WCESCOMM.LOG"
08/25/2004 10:55:43.821 - Windows CE Services (3.7.4034) Communication Logging.
08/25/2004 10:55:43.861 - Logging file auto-purge after a successful device connection.
08/25/2004 10:55:43.901 - Connection: Process connection from IP address 127.0.0.1:1117.
08/25/2004 10:55:44.162 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
08/25/2004 10:55:44.202 - TCP: ....S., 192.168.55.100(1025) => 192.168.55.101(990) Seq=1541636-1541636 Ack=0 Win=8192 Len=44
08/25/2004 10:55:44.853 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1025) Seq=3055182-3055182 Ack=1541637 Win=8760 Len=44
08/25/2004 10:55:45.734 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
08/25/2004 10:55:45.834 - TCP: ....S., 192.168.55.100(1026) => 192.168.55.101(990) Seq=1543209-1543209 Ack=0 Win=8192 Len=44
08/25/2004 10:55:46.185 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1026) Seq=3056532-3056532 Ack=1543210 Win=8760 Len=44
08/25/2004 10:55:47.416 - CesProxy: recv failed on Win socket 990, err = 10054
08/25/2004 10:55:47.476 - CesProxy: Close Win socket 990
08/25/2004 10:55:47.516 - CesProxy: Close PPP socket 990
08/25/2004 10:55:47.557 - TCP: ...R.., 192.168.55.100(1025) => 192.168.55.101(990) Seq=1541827-1541827 Ack=3055223 Win=0 Len=40
08/25/2004 10:55:47.607 - CesProxy: recv failed on PPP socket 990, err = 10004
08/25/2004 10:56:44.248 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
08/25/2004 10:56:44.288 - TCP: ....S., 192.168.55.100(1027) => 192.168.55.101(990) Seq=1601723-1601723 Ack=0 Win=8192 Len=44
08/25/2004 10:56:44.498 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1027) Seq=3115033-3115033 Ack=1601724 Win=8760 Len=44