How to solve TCP connection issue to debug on a PocketPC ?

[netcoupe.net]

Hi,

I'm currently developping a Windows application for PocketPC with Visual
Studio 2003.
Since our HHP 9500 Dolphin PocketPC has no USB cradle, we cannot use
ActiveSync (else it conflicts with the utility tool in charge of the
connection to the Ethernet base)

To debug via TCP/IP, we tried (and succeeded) to change Tools / periph TCP
transport configuration, replacing the option "IP adress provided by
ActiveSync" by the option "static IP address", this IP address set to the IP
of the slot receiving the PocketPC.
Few days ago, debug worked fine using this settings.

However, I have not been able to reproduce that way of debugging today...
Visual Studio attempts to establish a connection but fails with a message
"Unable to establish the connection. Check ..."

I think that PocketPC <=> computer connection is actually good, since ping
work in both directions, and I can use a tool which replicates the screen of
the PocketPC on the screen of the computer (this tool is setup to use TCP
transport, and not ActiveSync)

Could you tell me some advice on the possible causes of that issue, and the
way to solve the problem ?
Thanks a lot for your time.

Regards,
Samuel

 

[Paul G. Tobey [eMVP]]

Note that I don't work with PPC devices, but regular Windows CE devices, so
this information may be a bit off... If you can ping the PPC device from
your development workstation, I think it's safe to conclude that
communication is OK. There are also authentication issues and it's possible
that a reset of the device could leave it in a state where it won't work
with network communications and VS.NET until you've reestablished an
ActiveSync connection. You might give that a quick try, setting a
partnership, if appropriate, etc.

If that doesn't work, you could try the Smart Device Authentication
application, which has been discussed as a non-ActiveSync method of
attaching to Windows CE devices here in the past. You have to download some
add-ons from Microsoft, potentially copy a couple of files to the device,
run a program on the device, run a corresponding program on the desktop and
enter the IP of the device, etc. A quick search from the page referenced
below for "sdauthutildevice.exe" should find the step-by-step instructions,
I think:

http://groups-beta.google.com/group...tframework?hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8

Paul T.

 

[netcoupe.net]

Thank you very much. I will try t establish partnership as soon as I have a
solution to connect directly the PPC to the desktop (probably using infrared
since no direct USB is available).

Regards,
Samuel