c# - SoapHttpClientProtocol throws ConnectFailure despite having successfully sent message on WM 6.5 with .NET CF 3.5 -

here's knotty one.

this windows mobile 6.5 device running .net compact framework 3.5.9085.00 simple auto-generated web service call via automatically generated soap proxy, subclass of system.net.soaphttpclientprotocol (c#)

the call doinvoke() throws system.net.webexception not connecting network. indicate kind of web-proxy or connection error, when stick simple logging server @ web service address can see post being received loud , clear, can connect network.

the same code works absolutely fine on device of same model. when use simple logging server can see identical post other device, 1 throws system.net.webexception: operation has timed-out instead (which would, isn't going response).

i'm baffled. there's doubtless configuration difference between 2 that's causing problem i've no idea what.

it's though first device has set write-only connection server , falls on when tries read response, i've never heard of such situation before.

anybody shine light on one?

system.net.webexception: not establish connection network.        @ system.net.httpwebrequest.finishgetresponse()        @ system.net.httpwebrequest.getresponse()        @ system.web.services.protocols.webclientprotocol.getwebresponse(webrequest request)        @ system.web.services.protocols.httpwebclientprotocol.getwebresponse(webrequest request)        @ system.web.services.protocols.soaphttpclientprotocol.doinvoke(string methodname, object[] parameters, webclientasyncresult asyncresult)        ...      exception status: connectfailure     exception message: not establish connection network.     no inner exception.  

turns out odd behaviour due device's wifi network adapter being set 'work' instead of 'the internet'.

this can set through control panel, or adding registry key

hklm\controlpanel\wifi\ethernet 

containing value

"destid"="{436ef144-b4fb-4863-a041-8f905a62c572}" 

(which internet's guid).

'work' seems default if registry key isn't there.

as value set, connection worked fine.

why connection can send not receive in 'work' mode (rather than, say, doing neither) still mystery, how solved.