Re: Exchange 2003 OMA problem

From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 09/18/04 

Date: Sat, 18 Sep 2004 10:03:54 -0400

Are you trying to access this OMA via the WAPBROWSER (I assume so from the
logs and the t610 spec)?
Let me point out another difference to you
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
and suggest that you look at WAP browser for the desktop while you work this
out. I believe there's one from OpenWave SDK for mobile phones
(http://developer.openwave.com/dvl/tools_and_sdk/openwave_mobile_sdk/)
As you've noticed, it's not the same to use IE to check this out. The SDK
browswer will give some error codes and such that may be helpful in figuring
this out.

Let us know what you find..

"Frustrated Tom working on OMA" <exchange-help@ofir.dk> wrote in message
news:5b34d60.0409180538.54c98437@posting.google.com...
> Hello !
>
> I have an Exchange 2003 SP1 running on a Windows 2003 Server. No FE/BE
> configuration, ie it runs on a single server.
>
> In a Windows 2000 DC domain.
>
> OWA using SSL, works fine.
>
> I've reinstalled Dupdate 4.0 and also done the
> ExchangeVDir workaround
>
> I was wondering if anyone could help me solve a problem I have with
> OMA:
>
> Using a browser I can connect fine, but using a mobile phone I get
> Communication Error
>
> Checking the Security log the Authorization process is the same for
> both the browser and the mobile phone
>
> Checking the IIS log I can only spot 1 difference between the 2
> connections:
>
> 2004-09-17 07:55:04 SERVER-IP GET /oma/oma.aspx - 80 USER WAPGATEWAY
> SonyEricssonT610/R401+Profile/MIDP-1.0+Configuration/CLDC-1.0 302 0 0
>
> 2004-09-17 07:55:26 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP PROPFIND /exoma/murriel/Indbakke/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP PROPFIND /exoma/murriel/Indbakke/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP SEARCH /exoma/murriel/Kalender/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP SEARCH /exoma/murriel/Opgaver/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:55:26 SERVER-IP GET /oma/oma.aspx - 80 USER WAPGATEWAY
> SonyEricssonT610/R401+Profile/MIDP-1.0+Configuration/CLDC-1.0 200 0 64
>
>
>
>
> 2004-09-17 07:57:22 SERVER-IP GET /oma/oma.aspx - 80 USER
> 192.168.69.27
> Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 302 0 0
>
> 2004-09-17 07:57:22 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP PROPFIND /exoma/murriel/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP PROPFIND /exoma/murriel/Indbakke/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP PROPFIND /exoma/murriel/Indbakke/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP SEARCH /exoma/murriel/Kalender/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP SEARCH /exoma/murriel/Opgaver/ - 80
> DOMAIN\USER SERVER-IP - 207 0 0
> 2004-09-17 07:57:22 SERVER-IP GET /oma/oma.aspx - 80 USER
> 192.168.69.27
> Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.1.4322)
> 200 0 0
>
>
> The Ericsson has a 200 0 64, whereas a browser has 200 0 0
>
> Now the 200 0 64 translates:
> 200 Authorized
> 0 (no subcode)
> 64 The network name has been deleted.
>
>
> Does anyone know why this happens and wow to fix it ?

Relevant Pages

  • Re: XP home network
    ... I'm going to bet that you have a browser conflict here. ... logs from ... workstation", from each computer, so we can diagnose the problem. ... But the binding of NetBT to the OptusNet adapter, on Pats, could be a problem. ...
    (microsoft.public.windowsxp.network_web)
  • UserConcurrency
    ... I increment the count field in my database ... If the user refreshes his browser, ... logs in, I create the cookie. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: OMA - 500 Internal Server Error
    ... Don't setup signature ":" in ISA, then OMA can work! ... > My cell phone is Motorola A768i, the browser is Motorola browser v2.2. ...
    (microsoft.public.exchange.admin)
  • RE: After installing SP2 on E2K3 servers OMA ActiveSynch is not workin
    ... with some mobile phone i'm able to browse OMA, ... > Logon Failure: ... > Caller User Name: DMZEXCH2$ ...
    (microsoft.public.exchange.connectivity)
  • Re: OMA
    ... I just set up OMA and it seems to work pretty well on a standard WAP ... browser. ... is there any way to get rid of the "unsupported device" message ...
    (microsoft.public.windows.server.sbs)