Radius Server - IAS can't contact w2k3 ad

This is Interesting: Free IT Magazines  
Home > Archive > Radius Server > February 2004 > IAS can't contact w2k3 ad





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author IAS can't contact w2k3 ad
Hans

2004-02-18, 6:33 pm

We recently migrated our w2k domain to w2k3. After the
migration our w2k ias server (located in an other nt4
domain) is unable to contact the w2k3 domain to check if
the user is in the group that is allowed to set up a vpn
tunnel.
IAS gives an error 3 with Reason = The user's account
domain is not accessible. The nt4 domain is trusted by the
w2k3 domain.
Does someone know how I can fix this?

Sam Salhi [MSFT]

2004-02-19, 9:34 am

it's highly recommended that you have your IAS server in the Win2k3 domain.
You can either move it or forward requests to an IAS server in the win2k3
domain


--
========================================
===================
This posting is provided "AS IS" with no warranties and confers no rights
========================================
===================


"Hans" <anonymous@discussions.microsoft.com> wrote in message
news:12d1e01c3f6be$c3f3cda0$a401280a@phx
.gbl...
> We recently migrated our w2k domain to w2k3. After the
> migration our w2k ias server (located in an other nt4
> domain) is unable to contact the w2k3 domain to check if
> the user is in the group that is allowed to set up a vpn
> tunnel.
> IAS gives an error 3 with Reason = The user's account
> domain is not accessible. The nt4 domain is trusted by the
> w2k3 domain.
> Does someone know how I can fix this?
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com