WM6 Activesync with Exchange Server "Waiting for Network" problem

Hello

I have a found a lot of posts on the Internet regarding this problem. After
some exhaustive research and testing on my end, I feel as though I have
narrowed this down a little; unfortunately, I have not resolved the problem
as yet.

I currently have the following hardware/software configuration
* HTC P3600i Phone (Dopod D810X)
* Windows Vista Business (on desktop & laptop) + WMDC for Vista
* Exchange Server 2003 SP2 (on Windows 2003 Server SP1) + latest hotfixes
* Cisco ASA5505 Firewall configured to allow SSL to Exchange Server

When connected to my desktop or laptop, the servername resolves to an
internal IP (192.168.8.1) and when connected OTA via my mobile carrier
(Telstra in Australia), the servername will resolve to the public IP address
of 203.206.x.y etc.

I found a nice screenshot of the exact problem at
http://discussion.treocentral.com/sh...d.php?t=136358 and I have the
following comments to add wrt my findings....

* If I reboot my phone with the USB cable connected, I can use USB but not
OTA sync until I reboot again
* If I reboot my phone and use OTA sync, I cannot use USB until I reboot again
* I found some posts that indicate this to be a DNS Cache problem (sounded
promising as the mail server will resolve to a different IP via USB compared
to OTA sync) but I tried making these registry changes on the Phone with no
success. There seems to be a bit of confusion as to whether this key is
DnsCacheEnable or DNsCacheEnabled. There are references to this reg change
at
http://www.microsoft.com/communities...5f30cfe23c&p=1
but I had no success with either setting.
* I have other clients that also have the same problem and they have a range
of different phone hardware (eg: iMate SP5) and client software (Windows XP),
so it does not seem to be specific to the phone or the PC, more specifically
to Windows Mobile and Exchange Activesync.

Has anyone else got as far as this, or perhaps, further? I would expect
that this is fixable, but knowing what little tweak is needed has escaped me
so far.

Thanks in advance

Cheers
-Brendan

"Brendan Helsham" <> wrote in
message news:543E0D57-4B2B-486F-AE24-...
> Hello
>
> I have a found a lot of posts on the Internet regarding this problem.
> After
> some exhaustive research and testing on my end, I feel as though I have
> narrowed this down a little; unfortunately, I have not resolved the
> problem
> as yet.
>
> I currently have the following hardware/software configuration
> * HTC P3600i Phone (Dopod D810X)
> * Windows Vista Business (on desktop & laptop) + WMDC for Vista
> * Exchange Server 2003 SP2 (on Windows 2003 Server SP1) + latest hotfixes
> * Cisco ASA5505 Firewall configured to allow SSL to Exchange Server
>
> When connected to my desktop or laptop, the servername resolves to an
> internal IP (192.168.8.1) and when connected OTA via my mobile carrier
> (Telstra in Australia), the servername will resolve to the public IP
> address
> of 203.206.x.y etc.
>
> I found a nice screenshot of the exact problem at
> http://discussion.treocentral.com/sh...d.php?t=136358 and I have the
> following comments to add wrt my findings....
>
> * If I reboot my phone with the USB cable connected, I can use USB but not
> OTA sync until I reboot again
> * If I reboot my phone and use OTA sync, I cannot use USB until I reboot
> again
> * I found some posts that indicate this to be a DNS Cache problem (sounded
> promising as the mail server will resolve to a different IP via USB
> compared
> to OTA sync) but I tried making these registry changes on the Phone with
> no
> success. There seems to be a bit of confusion as to whether this key is
> DnsCacheEnable or DNsCacheEnabled. There are references to this reg
> change
> at
> http://www.microsoft.com/communities...5f30cfe23c&p=1
> but I had no success with either setting.
> * I have other clients that also have the same problem and they have a
> range
> of different phone hardware (eg: iMate SP5) and client software (Windows
> XP),
> so it does not seem to be specific to the phone or the PC, more
> specifically
> to Windows Mobile and Exchange Activesync.
>
> Has anyone else got as far as this, or perhaps, further? I would expect
> that this is fixable, but knowing what little tweak is needed has escaped
> me
> so far.
>
> Thanks in advance
>
> Cheers
> -Brendan

Hi,
I suggest that the company allow you to sync with the external IP address
even within the company. This can be done by ensuring that the host name
internally and externally resolves to the external IP.

If this is not done then you may have problems because of the DNS caching of
the IP.


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

Windows Mobile Device Center FAQs -
http://www.pocketpcfaq.com/faqs/wmdc/index.htm
ActiveSync Troubleshooting Guide -
http://www.pocketpcfaq.com/faqs/t-shootactivesync.htm

"Brendan Helsham" <> wrote in
message news:543E0D57-4B2B-486F-AE24-...
> Hello
>
> I have a found a lot of posts on the Internet regarding this problem.
> After
> some exhaustive research and testing on my end, I feel as though I have
> narrowed this down a little; unfortunately, I have not resolved the
> problem
> as yet.
>
> I currently have the following hardware/software configuration
> * HTC P3600i Phone (Dopod D810X)
> * Windows Vista Business (on desktop & laptop) + WMDC for Vista
> * Exchange Server 2003 SP2 (on Windows 2003 Server SP1) + latest hotfixes
> * Cisco ASA5505 Firewall configured to allow SSL to Exchange Server
>
> When connected to my desktop or laptop, the servername resolves to an
> internal IP (192.168.8.1) and when connected OTA via my mobile carrier
> (Telstra in Australia), the servername will resolve to the public IP
> address
> of 203.206.x.y etc.
>
> I found a nice screenshot of the exact problem at
> http://discussion.treocentral.com/sh...d.php?t=136358 and I have the
> following comments to add wrt my findings....
>
> * If I reboot my phone with the USB cable connected, I can use USB but not
> OTA sync until I reboot again
> * If I reboot my phone and use OTA sync, I cannot use USB until I reboot
> again
> * I found some posts that indicate this to be a DNS Cache problem (sounded
> promising as the mail server will resolve to a different IP via USB
> compared
> to OTA sync) but I tried making these registry changes on the Phone with
> no
> success. There seems to be a bit of confusion as to whether this key is
> DnsCacheEnable or DNsCacheEnabled. There are references to this reg
> change
> at
> http://www.microsoft.com/communities...5f30cfe23c&p=1
> but I had no success with either setting.
> * I have other clients that also have the same problem and they have a
> range
> of different phone hardware (eg: iMate SP5) and client software (Windows
> XP),
> so it does not seem to be specific to the phone or the PC, more
> specifically
> to Windows Mobile and Exchange Activesync.
>
> Has anyone else got as far as this, or perhaps, further? I would expect
> that this is fixable, but knowing what little tweak is needed has escaped
> me
> so far.
>
> Thanks in advance
>
> Cheers
> -Brendan

You can't do this because the network uses a Cisco ASA Firewall (not a
router), so it is not possible to connect to the external/public IP from in
side the network.

Cheers

"Chris De Herrera" wrote:

> Hi,
> I suggest that the company allow you to sync with the external IP address
> even within the company. This can be done by ensuring that the host name
> internally and externally resolves to the external IP.
>
> If this is not done then you may have problems because of the DNS caching of
> the IP.
>
>
> --
> Chris De Herrera
> http://www.pocketpcfaq.com
> http://www.tabletpctalk.com
> http://www.pocketpctalk.com
> http://www.mobilitytalk.com
>
> Windows Mobile Device Center FAQs -
> http://www.pocketpcfaq.com/faqs/wmdc/index.htm
> ActiveSync Troubleshooting Guide -
> http://www.pocketpcfaq.com/faqs/t-shootactivesync.htm
>
> "Brendan Helsham" <> wrote in
> message news:543E0D57-4B2B-486F-AE24-...
> > Hello
> >
> > I have a found a lot of posts on the Internet regarding this problem.
> > After
> > some exhaustive research and testing on my end, I feel as though I have
> > narrowed this down a little; unfortunately, I have not resolved the
> > problem
> > as yet.
> >
> > I currently have the following hardware/software configuration
> > * HTC P3600i Phone (Dopod D810X)
> > * Windows Vista Business (on desktop & laptop) + WMDC for Vista
> > * Exchange Server 2003 SP2 (on Windows 2003 Server SP1) + latest hotfixes
> > * Cisco ASA5505 Firewall configured to allow SSL to Exchange Server
> >
> > When connected to my desktop or laptop, the servername resolves to an
> > internal IP (192.168.8.1) and when connected OTA via my mobile carrier
> > (Telstra in Australia), the servername will resolve to the public IP
> > address
> > of 203.206.x.y etc.
> >
> > I found a nice screenshot of the exact problem at
> > http://discussion.treocentral.com/sh...d.php?t=136358 and I have the
> > following comments to add wrt my findings....
> >
> > * If I reboot my phone with the USB cable connected, I can use USB but not
> > OTA sync until I reboot again
> > * If I reboot my phone and use OTA sync, I cannot use USB until I reboot
> > again
> > * I found some posts that indicate this to be a DNS Cache problem (sounded
> > promising as the mail server will resolve to a different IP via USB
> > compared
> > to OTA sync) but I tried making these registry changes on the Phone with
> > no
> > success. There seems to be a bit of confusion as to whether this key is
> > DnsCacheEnable or DNsCacheEnabled. There are references to this reg
> > change
> > at
> > http://www.microsoft.com/communities...5f30cfe23c&p=1
> > but I had no success with either setting.
> > * I have other clients that also have the same problem and they have a
> > range
> > of different phone hardware (eg: iMate SP5) and client software (Windows
> > XP),
> > so it does not seem to be specific to the phone or the PC, more
> > specifically
> > to Windows Mobile and Exchange Activesync.
> >
> > Has anyone else got as far as this, or perhaps, further? I would expect
> > that this is fixable, but knowing what little tweak is needed has escaped
> > me
> > so far.
> >
> > Thanks in advance
> >
> > Cheers
> > -Brendan
>
>
>