We upgraded our login server early this morning, dual Pro 200, NT4/SP3,
128MB, RadiusNT 2.5.124 running as a service, ODBC mode. All had been
pre-installed and tested for about a week - this morning we just stopped
Radius, copied over the current database (Access97), swapped IP addresses,
and brought up the new machine.
Seemed to go very smoothly - for a couple hours at least. Since then, we've
had 3-4 distinct problems where connections are fine for a while and then
start being denied with the error below. The bandaid fix is to stop and
restart RadiusNT, then all is OK again (until the next time).
Any idea what might be causing this? It wasn't happening on the old
machine, and it's the exact same database as before, no changes to table
structures or indexes. Is there a way to determine which table/index is
being referred to? (It just happened again...) Here's a longshot, but is
the dual CPU config an issue at all?