Hi Anatoliy,
One other developer I have discussed this issue with has confirmed that if you unregister the remoting channel the Spokes COM connection then works correctly, so there is a potential workaround by unregistering remoting, connect to Spokes then re-register remoting channel.
In the end however that developer worked around the problem by replacing the remoting channel with a simple socket connection.
Hope it helps 
Thanks,
Lewis