Nightmare! Now got error code 0x85010018

Any help gratefully accepted.....

We have an sbs 2003 premium network running isa and exchange 2003
We have 2 x trio MDAs. One has been working fine and all syncing. The other
was not.
We had to upgrade our BT router - this was installed and the firewall opened
(using ISA instead)
After the upgrade, the one MDA that was working started to misbehave - I
tried to soft reset the MDA and then ran AS from the PC direct, then I ran
connection manager again on the server but the MDA says says looking for
changes, appears connected then says the server could not be reached with
sup code 0x85010018

I can access the server from RWW and I have made no changes at all to the
ISA firewall. To summarise - the only changes made have been to upgrade the
router (btw, I swapped the old one back in to see if that would help...same
prob).

Thanks



tried to run conenction mgr again
tried soft reset
active sync -

Hi,
The error is a device timeout accessing the HTTP gateway.

Did you configure the timeouts that Microsoft recommends with Exchange
ActiveSync and ISA? See http://support.microsoft.com/kb/905013


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

"JD" <> wrote in message
news:%...
> Any help gratefully accepted.....
>
> We have an sbs 2003 premium network running isa and exchange 2003
> We have 2 x trio MDAs. One has been working fine and all syncing. The
> other was not.
> We had to upgrade our BT router - this was installed and the firewall
> opened (using ISA instead)
> After the upgrade, the one MDA that was working started to misbehave - I
> tried to soft reset the MDA and then ran AS from the PC direct, then I ran
> connection manager again on the server but the MDA says says looking for
> changes, appears connected then says the server could not be reached with
> sup code 0x85010018
>
> I can access the server from RWW and I have made no changes at all to the
> ISA firewall. To summarise - the only changes made have been to upgrade
> the router (btw, I swapped the old one back in to see if that would
> help...same prob).
>
> Thanks
>
>
>
> tried to run conenction mgr again
> tried soft reset
> active sync -

We have ISA 2000 and web listeners don't seem to be there - do you have any
further info - in the meantime, I'll have a search around the net


"Chris De Herrera" <> wrote in message
news:edrem$...
> Hi,
> The error is a device timeout accessing the HTTP gateway.
>
> Did you configure the timeouts that Microsoft recommends with Exchange
> ActiveSync and ISA? See http://support.microsoft.com/kb/905013
>
>
> --
> Chris De Herrera
> http://www.pocketpcfaq.com
> http://www.pocketpctalk.com
> http://www.tabletpctalk.com
> http://www.mobilitytalk.com
>
> "JD" <> wrote in message
> news:%...
>> Any help gratefully accepted.....
>>
>> We have an sbs 2003 premium network running isa and exchange 2003
>> We have 2 x trio MDAs. One has been working fine and all syncing. The
>> other was not.
>> We had to upgrade our BT router - this was installed and the firewall
>> opened (using ISA instead)
>> After the upgrade, the one MDA that was working started to misbehave - I
>> tried to soft reset the MDA and then ran AS from the PC direct, then I
>> ran connection manager again on the server but the MDA says says looking
>> for changes, appears connected then says the server could not be reached
>> with sup code 0x85010018
>>
>> I can access the server from RWW and I have made no changes at all to the
>> ISA firewall. To summarise - the only changes made have been to upgrade
>> the router (btw, I swapped the old one back in to see if that would
>> help...same prob).
>>
>> Thanks
>>
>>
>>
>> tried to run conenction mgr again
>> tried soft reset
>> active sync -
>

Hi and thanks for your help

Have found the way to increase the timeout in ISA 2000 and it now works. If
anyone is having the same issue:

To set the default timeout value
1. In the ISA Server management console, open the Properties page, and then
click the Incoming Web Requests tab.
2. In Connections, click Settings, and then change the Connection timeout
value to a value of 900 seconds or greater.



"JD" <> wrote in message
news:...
> We have ISA 2000 and web listeners don't seem to be there - do you have
> any further info - in the meantime, I'll have a search around the net
>
>
> "Chris De Herrera" <> wrote in message
> news:edrem$...
>> Hi,
>> The error is a device timeout accessing the HTTP gateway.
>>
>> Did you configure the timeouts that Microsoft recommends with Exchange
>> ActiveSync and ISA? See http://support.microsoft.com/kb/905013
>>
>>
>> --
>> Chris De Herrera
>> http://www.pocketpcfaq.com
>> http://www.pocketpctalk.com
>> http://www.tabletpctalk.com
>> http://www.mobilitytalk.com
>>
>> "JD" <> wrote in message
>> news:%...
>>> Any help gratefully accepted.....
>>>
>>> We have an sbs 2003 premium network running isa and exchange 2003
>>> We have 2 x trio MDAs. One has been working fine and all syncing. The
>>> other was not.
>>> We had to upgrade our BT router - this was installed and the firewall
>>> opened (using ISA instead)
>>> After the upgrade, the one MDA that was working started to misbehave - I
>>> tried to soft reset the MDA and then ran AS from the PC direct, then I
>>> ran connection manager again on the server but the MDA says says looking
>>> for changes, appears connected then says the server could not be reached
>>> with sup code 0x85010018
>>>
>>> I can access the server from RWW and I have made no changes at all to
>>> the ISA firewall. To summarise - the only changes made have been to
>>> upgrade the router (btw, I swapped the old one back in to see if that
>>> would help...same prob).
>>>
>>> Thanks
>>>
>>>
>>>
>>> tried to run conenction mgr again
>>> tried soft reset
>>> active sync -
>>
>

Thanks for sharing the answer for ISA Server 2000.


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

"JD" <> wrote in message
news:...
> Hi and thanks for your help
>
> Have found the way to increase the timeout in ISA 2000 and it now works.
> If anyone is having the same issue:
>
> To set the default timeout value
> 1. In the ISA Server management console, open the Properties page, and
> then click the Incoming Web Requests tab.
> 2. In Connections, click Settings, and then change the Connection timeout
> value to a value of 900 seconds or greater.
>
>
>
> "JD" <> wrote in message
> news:...
>> We have ISA 2000 and web listeners don't seem to be there - do you have
>> any further info - in the meantime, I'll have a search around the net
>>
>>
>> "Chris De Herrera" <> wrote in message
>> news:edrem$...
>>> Hi,
>>> The error is a device timeout accessing the HTTP gateway.
>>>
>>> Did you configure the timeouts that Microsoft recommends with Exchange
>>> ActiveSync and ISA? See http://support.microsoft.com/kb/905013
>>>
>>>
>>> --
>>> Chris De Herrera
>>> http://www.pocketpcfaq.com
>>> http://www.pocketpctalk.com
>>> http://www.tabletpctalk.com
>>> http://www.mobilitytalk.com
>>>
>>> "JD" <> wrote in message
>>> news:%...
>>>> Any help gratefully accepted.....
>>>>
>>>> We have an sbs 2003 premium network running isa and exchange 2003
>>>> We have 2 x trio MDAs. One has been working fine and all syncing. The
>>>> other was not.
>>>> We had to upgrade our BT router - this was installed and the firewall
>>>> opened (using ISA instead)
>>>> After the upgrade, the one MDA that was working started to misbehave -
>>>> I tried to soft reset the MDA and then ran AS from the PC direct, then
>>>> I ran connection manager again on the server but the MDA says says
>>>> looking for changes, appears connected then says the server could not
>>>> be reached with sup code 0x85010018
>>>>
>>>> I can access the server from RWW and I have made no changes at all to
>>>> the ISA firewall. To summarise - the only changes made have been to
>>>> upgrade the router (btw, I swapped the old one back in to see if that
>>>> would help...same prob).
>>>>
>>>> Thanks
>>>>
>>>>
>>>>
>>>> tried to run conenction mgr again
>>>> tried soft reset
>>>> active sync -
>>>
>>
>