Re: OWA 2003 logon fails when failover to one node of cluster backend

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Well, after a tech call I solved the issue.

It ware rights to the C drive where the exchange software was. Someone had
removed the Domain User from the rights to read the drive. Once they were
added back in OWA worked fine for these users.


"KatPavelka" <k.pavelka@xxxxxxxxxxx> wrote in message
news:%230gi5d%23lFHA.2404@xxxxxxxxxxxxxxxxxxxxxxx
>I have checked this.I also use GPOs on both these machines.
>
> Do you have any idea where else to look?
>
> Thank for your help.
>
> KP
>
> "Doug Blanchard [MSFT]" <dblanch@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:O1t6L99hFHA.320@xxxxxxxxxxxxxxxxxxxxxxx
>>I assume this is using OWA only and also through a Front-End server.
>>
>> Open the local security policy on both nodes. Walk through the settings
>> and see if there are any differences. Specifically look at "Log on
>> Locally and Access this Computer from the Network"
>>
>> Doug Blanchard [MSFT]
>> Microsoft PSS
>>
>> Please do not send email directly to this alias. This alias is for
>> newsgroup
>> purposes only. This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>>
>> "KatPavelka" <k.pavelka@xxxxxxxxxxx> wrote in message
>> news:%23xta2emhFHA.1372@xxxxxxxxxxxxxxxxxxxxxxx
>>>I have an issue that isn't an easy one, or maybe it is.
>>>
>>> I am running win2k3 OS 2-node active/passive cluster on my back-end
>>> exchange
>>> 2003 sp1 system. No I am not running SP1 for win2k3 yet. Haven't tested
>>> it
>>> with the HBAs I have. I had issue with some older ones. I have installed
>>> the
>>> following KBs 832759; 841561; 831464.
>>>
>>> When users logon when the backend is one of the nodes it works great,
>>> but
>>> when I failover to the 2nd node the only people that can log on are
>>> administrators and child domain users.
>>>
>>> I have the following in my IIS log
>>>
>>> NODE2
>>> 2005-07-11 19:00:13 XXX.XXX.XXX.XXX GET /exchange/ - 80 DOMAIN\USERNAME
>>> XXX.XXX.XXX.XXX
>>> Exchange-Server-Frontend-Proxy/6.5+Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
>>> 401 3 5
>>>
>>>
>>>
>>>
>>> NODE1
>>>
>>> 2005-07-11 20:58:30 XXX.XXX.XXX.XXX GET /exchange/ - 80 DOMAIN\USERNAME
>>> XXX.XXX.XXX.XXX
>>> Exchange-Server-Frontend-Proxy/6.5+Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+.NET+CLR+1.1.4322)
>>> 200 0 0
>>>
>>>
>>>
>>> All ip address are the same, but one is throughing a 401 error. I have
>>> looked at all configurations of IIS on each server and can't find
>>> anything
>>> that is different.
>>>
>>>
>>>
>>> Any help would be appreciated.
>>>
>>>
>>>
>>
>>
>
>


.



Relevant Pages

  • Re: default GPOs for a Domain User?
    ... If you don´t manipulate the restricted group settings, the domain user ... Soryy I can´t find a default rights schema, ... Mark Heitbrink - MVP Windows Server ...
    (microsoft.public.win2000.group_policy)
  • Re: display user rights on local and remote machine
    ... into which see what the user rights are for a given domain user or group. ... mouse, select properties, and select security tab. ... >> remote machines. ...
    (microsoft.public.vb.winapi)
  • Re: Question about group
    ... It would mean that domain user can log on to any computer and get admin rights to ... adding the built-in role "INTERACTIVE" to the local Administrators group. ...
    (microsoft.public.win2000.security)
  • Re: Adding domain users as local XP administrators...
    ... Any domain user that logs on to any XP PC in the ... > domain has full rights to the local machine. ... On the actual domain controller server, ... > if the folder security prevents a user from accessing a particular folder ...
    (microsoft.public.windowsxp.security_admin)