Routing and Remote access - Windows Accounting

We have Wndows 2003 R@ x64 running as a DC. The other day I attempted to
setup a Routing and Remote for a VPN with limited success. The only
exception discovered during the setup was the accounting provider - "Windows
Accounting" It was not accessible because of a failed 'user' and 'password'.
I have look almost everywhere for some guidance about 'Windows Accounting'
without success. How/Where would I find this service/program or other and
How would I setup a user name and password? Any comments or suggestion would
be appreicated
--
Developing Peopleware Solutions with Microsoft Framework

A warning first. Configuring a DC as a remote access server is a bad
idea, and is not recommended. As soon as you manage to get a remote user to
connect, your DC becomes multihomed, causing all sorts of odd behavior.

There are two things involved with setting up authentication for remote
access. The first is to configure the account name and password in the AD
accounts database and set the account to use remote access policy. The
second is to configure the remote access policy to allow access subject to
the conditions you wish to set.

"White Rock" <(E-Mail Removed)> wrote in message
news:2759A29F-BC38-4D18-A2E1-(E-Mail Removed)...
> We have Wndows 2003 R@ x64 running as a DC. The other day I attempted to
> setup a Routing and Remote for a VPN with limited success. The only
> exception discovered during the setup was the accounting provider -
> "Windows
> Accounting" It was not accessible because of a failed 'user' and
> 'password'.
> I have look almost everywhere for some guidance about 'Windows Accounting'
> without success. How/Where would I find this service/program or other and
> How would I setup a user name and password? Any comments or suggestion
> would
> be appreicated
> --
> Developing Peopleware Solutions with Microsoft Framework

Hi Bill,

Thanks for the reply and your insights. Do you feel the multihome condition
has caused the failure of "Windows Accounting"

I doubt it. Your server only becomes multihomed after you connect. The
server gets an additional IP for the internal RRAS interface. If you are
having authentication problems you haven't connected yet. I would thing it
was either the account setup or remote access policy which is prventing
authentication.

Is the account you are using set up to allow remote access based on
remote access policy? Is remote access policy set to allow access? (It is
set to deny access by default).

"White Rock" <(E-Mail Removed)> wrote in message
news:9413DB2B-3877-49E9-82DF-(E-Mail Removed)...
> Hi Bill,
>
> Thanks for the reply and your insights. Do you feel the multihome
> condition
> has caused the failure of "Windows Accounting"
>
>
>
>

Hi Bill

Thanks for your reply.

To answer the question about the access permission is that the remote policy
is set to accept the connection. The Authentication method and Accounting
provider methods for Routing and Remote Access is setup prior to the remote
policy. The authentication method choosen is "Windows Authentication" but
we've select "none" for the Accounting provider. Otherwise it does fail
because of the user and password issue mentioned earlier in this thread. Any
suggestions are appreciated. We haven't found any references anywhere to
"Windows Accounting" as a service. --
Developing Peopleware Solutions with Microsoft Framework


"Bill Grant" wrote:

> I doubt it. Your server only becomes multihomed after you connect. The
> server gets an additional IP for the internal RRAS interface. If you are
> having authentication problems you haven't connected yet. I would thing it
> was either the account setup or remote access policy which is prventing
> authentication.
>
> Is the account you are using set up to allow remote access based on
> remote access policy? Is remote access policy set to allow access? (It is
> set to deny access by default).
>
> "White Rock" <(E-Mail Removed)> wrote in message
> news:9413DB2B-3877-49E9-82DF-(E-Mail Removed)...
> > Hi Bill,
> >
> > Thanks for the reply and your insights. Do you feel the multihome
> > condition
> > has caused the failure of "Windows Accounting"
> >
> >
> >
> >
>
>
>

I haven't used any non-Windows remote access systems so I always leave
the Accounting option at the default. As far as I know it is only
significant if you are using RADIUS and want some other application to
handle the accounting.

In any case I doubt that the accounting provider setting would affect
authentication. If you are set up for Windows authentication and have remote
access policy set to accept connections and have the user account on the
Windows server set to use remote access policy, it should work.

"White Rock" <(E-Mail Removed)> wrote in message
news:75EE2DBD-8B07-4E7A-A26C-(E-Mail Removed)...
> Hi Bill
>
> Thanks for your reply.
>
> To answer the question about the access permission is that the remote
> policy
> is set to accept the connection. The Authentication method and Accounting
> provider methods for Routing and Remote Access is setup prior to the
> remote
> policy. The authentication method choosen is "Windows Authentication"
> but
> we've select "none" for the Accounting provider. Otherwise it does fail
> because of the user and password issue mentioned earlier in this thread.
> Any
> suggestions are appreciated. We haven't found any references anywhere to
> "Windows Accounting" as a service. --
> Developing Peopleware Solutions with Microsoft Framework
>
>
> "Bill Grant" wrote:
>
>> I doubt it. Your server only becomes multihomed after you connect. The
>> server gets an additional IP for the internal RRAS interface. If you are
>> having authentication problems you haven't connected yet. I would thing
>> it
>> was either the account setup or remote access policy which is prventing
>> authentication.
>>
>> Is the account you are using set up to allow remote access based on
>> remote access policy? Is remote access policy set to allow access? (It is
>> set to deny access by default).
>>
>> "White Rock" <(E-Mail Removed)> wrote in message
>> news:9413DB2B-3877-49E9-82DF-(E-Mail Removed)...
>> > Hi Bill,
>> >
>> > Thanks for the reply and your insights. Do you feel the multihome
>> > condition
>> > has caused the failure of "Windows Accounting"
>> >
>> >
>> >
>> >
>>
>>
>>