Re: 127.0.0.1/localhost in ActiveSync, Windows Mobile 5
- From: "John Spaith [MS]" <jspaith@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Feb 2006 08:18:39 -0800
I've spoken with our ActiveSync devs about this, here's what they say:
The actual exchange server name should be entered in the activesync client,
not localhost
--
John Spaith
Development Lead, Windows CE
Microsoft Corporation
Check out the CE Networking Team Blog at http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2006 Microsoft Corporation. All rights
reserved.
"Stull" <Stull@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:616A38C9-C042-40D1-9F8F-AA1FC6741711@xxxxxxxxxxxxxxxx
Hello!
I have a SSL vpn tunnel that works well prior to Windows Mobile 5. Since
WM5
have problem with
127.0.0.1.(http://blogs.msdn.com/cenet/archive/2005/06/06/425799.aspx) The
workaround is to use 'localhost' in web browser and mail client. it works
fine.
The problem occurs in the client ActiveSync application. It dosn't work
when
entering 'localhost' as server address.
Any workaround for this? All input on this is appreciated.
Regards,
Stefan Ullgren, PortWise
.
- Prev by Date: Pocket Access
- Next by Date: Re: Pocket Access
- Previous by thread: Pocket Access
- Next by thread: SHNotificationUpdate to remove the notification icon
- Index(es):
Relevant Pages
|
