No, this event viewer error doesnt seem to give more info on the problem.
Can you check the ias logs in %windir%\tracing ? This will give more info on
whether IAS was initialized correctly or not.
--
Thanks,
Priya.
------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ben" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi
>
> Thanks for the info - i have found this error in the event viewer:
>
> The description for Event ID ( 13 ) in Source ( IAS ) cannot be found. The
> local computer may not have the necessary registry information or message
> DLL files to display messages from a remote computer. You may be able to
use
> the /AUXSOURCE= flag to retrieve this description; see Help and Support
for
> details. The following information is part of the event: 192.168.1.253.
> Does this help identify the problem
>
>
>
> Thanks Ben
>
> "Priya Raghavan [MSFT]" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>
> > Hi,
> >
> > Your IAS mdb file could be corrupted because of which Windows Auth fails
> > to
> > start. Do you have any Remote Access Policies on your RAS Server ? If
so,
> > check those policies to see if there is any invalid attribute selected.
> >
> > Also, enable logging on the machine using this command:
> > netsh ras set tra * ena
> >
> > And check the IAS logs in %windir%\tracing\ directory to see whether IAS
> > initialization succeeded or not.
> >
> > --
> > Thanks,
> > Priya.
> >
> > ------------------
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> >
> > "Ben" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Hi
> >>
> >> When we configure RRAS on our W2K3 server with windows authentication
it
> >> does not start and it returns this error in the event log:
> >>
> >> The Routing and Remote Access service terminated with service-specific
> > error
> >> 691 (0x2B3).
> >>
> >> If I reconfigure but select RADIUS authentication it will start.
> >>
> >> Any advice would be much appreaciated
> >>
> >> Thanks
> >>
> >> Ben
> >>
> >>
> >
> >
>
>
|