We are setting up netlogin on our network switches to authenticate computers prior to letting them on the network. In the process, the switch will send the MAC address of the computer to the RADIUS server (we are using Windows Server 2003 IAS) to determine what VLAN the computer should be in.
In IAS there is an option for logging where you can log all authentication attempts to a central SQL server (we are using MSSQL Server 2005). This works great... until the SQL server is unavailable. According to Microsoft's own documentation:
If the IAS server cannot establish a connection with SQL Server 2000, the IAS server stops processing authentication and accounting requests and users cannot log on to the network
I couldn't believe what I read, until I tested it. If the logging server is unavailable users cannot log onto the network?!?! Since when is logging a critical function? We have offices in many locations and the SQL server in a central office, so if a link to an outlying office goes down, the users would no longer be able to log onto the network because the SQL server would be unreachable.
Is there any way to log IAS actions without having the whole process fail if the SQL server cannot be reached?