Re: Error number: 5

Tech-Archive recommends: Fix windows errors by optimizing your registry

David King wrote:

> Thanks! I'll have to keep "net helpmsg" around for future use, that really
> helped.
>
> In case anyone else comes across this, it turned out to be an incorrect
> setting of "authflags" in the IIS metabase for one of the ASP pages
> associated with the IISADMPWD application (which would explain why it
> worked in some places, but not others).
>
> "Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:if8m519166qh1f548dmr94ojej4m3o9fi5@xxxxxxxxxx
>> "David King" <davidking@xxxxxxxxxxxxxxxxxxx> wrote:
>>
>> > This may not be the best place for this, but here goes: I have
> several
>> >remote users on Exchange 2003 Standard using Outlook 2003, with
>> >RPC-over-HTTP. Since there's no "pretty" way to have them change their
>> >passwords, every 60 days they are have to log into OWA to change their
>> >password there using the IISADMPWD application with IIS 6.0.
>> > That'd be great, but when they type out their user name, old
> password,
>> >new password, etc, they are presented with a less-than-explanatory
>> >"Error Number: 5."
>>
>> Error 5 is "Access is Denied".
>>
>>
>> You can use "net helpmsg 5" from the command line to translate numbers
>> to meanngful (well, semi-meaningful) text. Replace "5" with the error
>> number.
>>
>> --
>> Rich Matheisen
>> MCSE+I, Exchange MVP
>> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm

I'm getting this same error (5 access denied) when trying to run the Active
Directory migration tool.

I built a Windows 2003 SBS Server and want to migrate over all of the
NT4.0/Exchange 5.0 user and mail stuff (without disturbing the production
network).

I established a trust relationship between the production PDC and my new
domain server that of course has a different domain name. When I did this,
the PDC said that it couldn't veruify that the trust relationship was
established and said to check on the Windows 2003 server to see if the
trusting relationship exists (I don't know how to do this).

I'm guessing it doesn't otherwise I wouldn't be getting this "access denied"
error message.

I am *NOT* a Microsoft expert.... any pointers on where I need to go from
here?

TIA!

.

Relevant Pages

  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... For Windows 2000 and 2003 these settings may be applied/configured via ... Digitally sign communications (if server ... With NT4 the only way to verify the settings is with the Regedt32 tool. ... Failed to create a trust relationship between NT4 and 2003 AD ...
    (microsoft.public.windows.server.migration)
  • Re: Permission Errors
    ... >a domain account so that it can be validated on the win2k server machine. ... However I have discovered that I can deploy the web service to the W2K ... domain server and there it runs with no problems, ... for me to decide that the new XP dev machine is up and usable. ...
    (microsoft.public.dotnet.general)
  • Re: Domain Confusion
    ... You cannot log into another domain without a trust relationship between the two domains. ... Microsoft MVP - Terminal Server ... the DMZ one and the 'newdomain' on the LAN. ... a W2k Server in 'newdomain' hosts the Exchange server. ...
    (microsoft.public.windows.terminal_services)
  • NT4 to 2003 migration
    ... Yet another migration question... ... trying to upgrade using 2003 SBS server, ... Windows 2003 install went fine. ... guessing the trust relationship capability. ...
    (microsoft.public.windows.server.migration)
  • Re: trust relationship
    ... Domain B with Windows 2000 server, one member server in domian A installed ... Trust relationship between 2 domains work fine, can access folders, ... authentication (IIS for instance can work EITHER way; ...
    (microsoft.public.win2000.networking)