ConnMgrMapURL is the Microsoft API call to Connection Manager that determines which sub-net (My ISP or My Work) will be able provide that connection. The function will return the GUID of the appropriate sub-net (the registry entries that you mentioned in your first post). You can then pass that GUID onto ConnMgrEstablishConnection or ConnMgrEstablishConnectionSync to actual trigger a connection attempt.. There are a lot more details on how to configure and operate Microsoft's Connection Manager on the MSDN at http://msdn.microsoft.com/en-us/library/bb416435.aspx. There is also a useful demo application in the Microsoft SDK called Connection Manager Helper ( http://msdn.microsoft.com/en-us/library/bb158792.aspx) "This code sample is named CmHelper. It demonstrates how to write a simplified Connection Manager client by deriving functionality from a helper class. This results in a client that focuses on only three things:

where the data is
whether a proxy is used
what information to show the user while connecting"

I used the following reg keys to force our device to use "My Work".  This also stopped any pop-up from displaying. [HKEY_LOCAL_MACHINE\Software\Microsoft\WZCSVC\Parameters\Interfaces\PCCARD\PHOTON1] "ActiveSettings"=hex:\       c4,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\       00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\       00,00,07,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\       00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,\       00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\       00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,03,00,\       00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\       00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,\       00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,04,00,00,20,02,00,00,00,00,\       00,01,68,00,00,10,00,00,00,10,00,00,00,dd,e7,51,ae,08,76,09,a3,c6,1b,24,d5,\       ce,ea,42,16,00,00,00,00,04,80,00,00,10,00,00,00,10,00,00,00,28,5f,27,45,f6,\       4f,ad,9a,f3,6f,15,eb,6e,00,7f,1b,20,00,00,00,c1,7c,64,95,82,78,32,47,45,e0,\       56,1c,e6,bd,8d,1b,7a,50,ff,b4,15,be,1e,30,00,c4,90,24,2e,ac,0f,47,14,00,00,\       00,74,56,c1,8d,7f,a3,9d,30,f7,1a,6c,aa,d7,26,98,86,ff,a9,16,4a "ControlFlags"=dword:01818002 "LayoutVersion"=dword:00000006 [HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{EF097F4C-DC4B-4c98-8FF6-AEF805DC0E8E}\HTTP-{18AD9FBD-F716-ACB6-FD8A-1965DB95B814}] "ConnectionGUID"="{B11DCDC3-249B-0BBC-240A-E5EC3CAB9BA9}" "DestId"="{436EF144-B4FB-4863-A041-8F905A62C572}" "Enable"=dword:00000001 "ExtraInfo"="" "Override"="" "Proxy"="new-inet:1159" "SrcId"="{18AD9FBD-F716-ACB6-FD8A-1965DB95B814}" "Type"=dword:00000000 "Username"=""

Richard, Here is the bigger picture.  MC75 in AppCenter with a battery suspended timeout (sleeping).  Enduser attentions the MC75 with a network application and the initial network communication is dialing #777 for Sprint PCS Vision, unless the "My Work Network" is set in Network Management. Its like the MC75, being a phone first and foremost wants to favor EVDO over a valid wireless profile which works fine and would connect if just given a proper delay or wait over dialing #777. If I choose My Work Network for both settings in Network Management, and WiFi is not available it would never dial #777, thus forcing the enduser to get closer to the AP. All of our applications that are called via AppCenter as well as our MSP agent are connected via a public resolved addresses.  So your saying if we know we want to resolve though our AP's VPN tunnel to corporate we should then direct our calls though the tunnel, then attempt a public reference if the tunnel wasn't successful. Brad

What url are you supplying to ConnMgrMapURL and what is its response?

Richard, Well, I'm not familar with ConnMgrMapURL.  I assume its an EMDK call of some sort? Brad

Can you explain what the end result of doing this is supposed to be? Connection Manager is designed to setup routing on the terminal based on a string based examination of the url given to it (note this is not DNS, it is string matching). Thus, by default, http:// www.somewhere.com/file.txt (and http://10.0.0.1/file.txt) will be routed to the 'My ISP' sub-net. http://server/file.txt will be routed to 'My Work'. If the required sub-net (usually 'My ISP') is usable but not active (such as a non-connected GPRS/EDGE network) then Connection Manager will start it up and re-work the routing so that it is then usable. Depending on which adapters are placed in which sub-net (by assigning them using the registry, control panel or provisioning xml) the possible choices for Connection Manager can be forced (both for 'My Work' and 'My ISP'). However this is sort of back to front. The easy choice can be made by using the appropriate url which will then configure the terminal as required to achieve connection. There are applications which just rely on someting else setting the routing up without directly calling Connection Manager but these are much more difficult to guarantee working in all cases. So the short answer to your question is Connection Manager can be configured by the registry, the control panel and xml configuring. The url you subsequently use will then determine which of theose configurations are then used.