Can "hit" server from .NET CF code but not from Internet Explorer [Seems Worse with SP2]

  • Thread starter Thread starter Chris Theorin
  • Start date Start date
C

Chris Theorin

I'm pretty "out of whack" when it comes to understanding this ActiveSync
pass through setting for cradled Pocket PCs.

I find a setting combination between the Pass Through setting on the Options
Rules tab of ActiveSync (3.7.1) on my workstation (XP SP1) (either The
Click to expand...
Internet or Work) and both settings (Programs that automatically connect to
the Internet should connect using & Programs that automatically connect to a
private network should connect using) on the Start > Settings > Connections
tab > Connections "app" > Advanced tab > Select Networks button > Network
Management screen of my Pocket PC device (Windows Mobile 2003 H1940 iPAQ)
(either My ISP or My Work Network) which actually allows the code below to
function and then I put the same url in the IE browser on the device and get
the 'Can't Connect' message specifying 'Couldn't connect with current
connection settings. To change your connection settings, tap Settings
(brings me to that "favorite" Network Management screen of mine).



<code>

string url = "http://compName/virDir/thepage.asp";

//string url = "http://compName.domain.com/virDir/thepage.asp"; //
fully-qualified computer name

//string url = "http://DottyIP/virDir/thepage.asp"; // DottyIP ==
255.255.255.255 style of thing

HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url);

request.Method = "POST";

request.Timeout = timeout;

request.AllowWriteStreamBuffering = true;

return (HttpWebResponse)request.GetResponse();

Stream responseStream=response.GetResponseStream();

StreamReader reader=new StreamReader(responseStream);

string fullResponse=reader.ReadToEnd();

</code>



And possibly the worst part... even if there was some group of settings
where a certain "type" of URL is "guaranteed" to work in both my code and
IE... that's definitely NOT optimal. I really, really, really don't want to
try and explain to users of my application how to do all this network
configuration and I don't think that it would be very "nice" of my app to
require them to use my settings anyway. I mean I bet all of these settings
are configurable for some reason... and at some point at least one of my
users is going to want to use that combination which just turns my logic to
hell.

Any comments/examples/encouragement out there? Anyone else trying to do
something like this and having as much trouble as I am? I just get angry,
wasn't the 2003 release of Pocket PC supposed to have something which
sounded like Apple marketing ("Zero-config" internet)?
 
Hey everybody. I might have flown a little off the handle with this post...
sorry 'bout that. While I still don't understand all these settings, I am
confident that IF I can hit a url (whether it be
http://compName/virDir/thePage.asp or http://dottyIP/virDir/thePage.asp)
using the code in the previous post... it will also work in IE (I've
completely left the fully-qualified situation
http://compName.domain.com/virDir/thePage.asp out of all these tests... just
too confusing for this guy).

Attached are some of my test result that you might find useful/interesting
when deciding whether to use the compName or the dottyIP.

You can get the dottyIP from the compName (via .NETCF) by using
System.Net.Dns.Resolve.

Chris
 
Back
Top