PocketPC connection not working?

  • Thread starter Thread starter Peter Morris [Droopy eyes software]
  • Start date Start date
P

Peter Morris [Droopy eyes software]

Hi all

My app runs in the emulator, but when trying to run the app on my pocket pc
VS2003 fails. This used to work, and I have no idea what has changed
(except reinstalling the SDK a few times).

Any suggestions?

Thanks

Pete
 
Hi

I have been collecting some additional information, here it is....

1) ActiveSync seems to work fine. It connects + synchronises. A small
window appears on the PPC telling me that the user is being authenticated +
succeeded etc.

2) The simple (default template) WinForm apps when deployed to Pocket PC
2003 emulator

3) When I try to select my Pocket PC device I get the following output....
Deploying to Pocket PC Device using TCP Connect Transport

about 2-3 mins later I get
Error: Cannot establish a connection. Be sure the device is physically
connected to the development computer.


I have installed the ProxyPort.reg files downloaded from microsoft, and they
have unfortunately made no difference. I have also ran that app
"DelDesktopCryptKey.exe" and restarted VS2003, still no luck.


Thanks for your help :-)

Pete
 
For clarity, what version of Windows Mobile is your device running and
what version of ActiveSync are you running?

Does your computer have a network connection? (if not, some folks have
had success by installing the Loopback Adapter)

Have you restarted your computer since you installed ProxyPorts.reg?
(and how about a soft-reset of the device?)

Check out the connectivity section of the FAQ:
http://msdn.microsoft.com/smartclient/understanding/netcf/FAQ/default.aspx#11.0
(in particular, install the WinCE Configuration Add-In:
http://www.microsoft.com/downloads/...086-b0cc-7c6c39b28762&DisplayLang=en#filelist).


I would also encourage a review of the readme for that item:
http://download.microsoft.com/download/c/d/b/cdbff573-73fb-4f9f-a464-c5adc890e1ae/Readme.htm

....and sometimes a hard-reset of the device does the trick.
 
Hi

Very odd. It seems that changing my base IP address on my wireless router
from 192.168.2.100 to 10.0.0.1 did the trick. All of a sudden it all
worked.

Thanks for your time, I really appreciate it!
 
VS2003 is very flakey with regards to connecting to a real device or
emulators. I have not experienced any of these "funnies" with VS2005.

Cheers
Simon.
 
I also disabled my two "virtual" network cards installed by VMWare, maybe
this was an additional factor
 
When I had *many* problems with VS 2003 connectivity, I found rebooting
seemed to fix the problem.
 
Back
Top