| James McIllece [MS] 2006-09-01, 7:50 pm |
| =?Utf-8?B?TWlrZSBBZGFtcw==?= <MikeAdams@discussions.microsoft.com> wrote
in news:1B8A0165-7657-4964-A4D2-704C0C0AF7F3@microsoft.com:
> I have set up RRAS for dial-in. By itself it works great. Now I've
> added IAS on the same box. The IAS is not to be responding. I've
> pointed the RRAS to the IAS and add RAS as a client
>
> Any help
>
It sounds like you don't really need IAS as well as RRAS. The only reason
you need IAS is to manage authentication and authorization for multiple
RRAS and/or other network access servers, or if you want to use advanced
logging features (SQl server logging).
That said, if you do want to use IAS you need to create a new remote access
policy in IAS for dial-in connection requests. Create the policy using the
New Remote Access Policy wizard, then open the policy and enable it. Also
set the 'Remote Access Permission" setting in the dial-in properties of
user accounts to either "Allow access" or "Control access through remote
access policy."
Note that the option "Control access through remote access policy" is
available only if your domain functional level is Windows Server 2003, if I
recall correctly. Make sure you read AD documentation on the subject before
you consider raising your domain functional level though.
--
James McIllece, Microsoft
Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.
This posting is provided "AS IS" with no warranties, and confers no rights.
|