John
Wed May 12 11:55:56 CDT 2004
I've talked with the developer of the Active Sync pass through and I think
he hit the nail on the head here. MSMQ on your WinXP machine is already
listening on the same ports that ActiveSync on your desktop would need to
listen on to forward to the CE device. Hence ActiveSync can't forward
anything on.
You can change the ports that MSMQ on CE listens on and then change
ActiveSync to forward these ports on the desktop to your client. You
obviously want to chose some ports that nothing else is listening on - port
80 would be bad, for instance :). Also be aware that this CE device will
now only talk MSMQ with your desktop via ActiveSync. If you unplugged it
and put on a network it would be using non-default ports other MSMQ clients
wouldn't be using.
You can change the port and pingPort MSMQ listensn on by running the command
line 'msmqadm change port <NewPort#>' and 'msmqadm change port pingport
<NewPort#>'. Visadm.exe is a visual tool that wraps msmqadm.exe and is in
the PPC SDK, there is still a way to enter command strings directly into
visadm to call underlying msmqadm functionality.
The default (in decimal) for MSMQ port is 1801 and MSMQ Ping Port is 3527
should you ever need to change these back again.
--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Let
us know!
https://www.windowsembeddedeval.com/community/newsgroups
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.
"Paul Dunleavy" <anonymous@discussions.microsoft.com> wrote in message
news:ab2e01c43676$4e2f9ac0$a101280a@phx.gbl...
thanks, but this does not seem to work. I'm am connecting
over a USB cable using active sync. What connectivity have
you used? (I may need to switch to a device with bluetooth)
>-----Original Message-----
>Yes, I believe that Active Sync is the culprit here in
blocking requests.
>Here is a snippet about how to allow AS to forward port
requests. I don't
>know if this is documented or officialy supported or not
and it may change
>in some future release of AS. Also I'm pretty sure this
will only forward
>connections being generated from your desktop machine
itself, but not from
>other hosts on the same network with you. So all in all
this is fine for
>development, hopefully for deployment you'll have another
network channel
>you can use.
>
>Here's the info:
><<
>you can add an entry to the registry to establish a well
known port which
>will be proxy-ed back to the device. When the device is
connected via AS,
>AS will bind to the port, and forward connect requests to
the device.
>The key is:
>
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE
Services\ProxyPorts
>
>The registry entries just have to be REG_DWORD, with any
name you like.
>
>
>
>This will allow you to "connect(localhost, <your port
number>)", and reach
>the device.
>
>>>
>--
>John Spaith
>Software Design Engineer, Windows CE
>Microsoft Corporation
>
>Have an opinion on the effectiveness of Microsoft
Embedded newsgroups? Let
>us know!
>https://www.windowsembeddedeval.com/community/newsgroups
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>You assume all risk for your use. © 2003 Microsoft
Corporation. All rights
>reserved.
>
>"Paul Dunleavy" <anonymous@discussions.microsoft.com>
wrote in message
>news:961401c43382$6abe7bd0$a301280a@phx.gbl...
>> I've written a desktop apllication and compact framework
>> application in .NET. The app on the pocket PC can send
and
>> receive messages on a private message queue. It can also
>> send messages to a private queue on my pc. However when
I
>> use my desktop app to send messages to the queue on the
>> pocket pc, MSMQ cannot establish a connection to send.
Why
>> do I only have a one way flow? could activesync be
>> blocking it (I'm connecting through a USB cable)? I
cannot
>> ping my pocket pc even after trying to allocate it a
>> static ip address.
>>
>> I'm using third party COM components to call MSMQ and
get
>> cominterop working on the PPC. (CFCOM and Ken Rabold's
>> MSMQCom.dll)
>
>
>.
>