I pointed my AP's at the new IP (old one is still there and they can ping it) and it started working.
Thanks From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, January 5, 2015 12:47 PM To: [email protected] Subject: RE: [NTSysADM] Added second IP to NIC, Radius fails I wish my memory was better. hazard of getting old. I've seen this before, and I believe it had to do with the fact that the IP address that Windows uses for IP transmissions is non-deterministic and was no longer working because the new IP address wasn't recognized on the source device. But your problem may be completely different. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of N Parr Sent: Monday, January 5, 2015 10:35 AM To: [email protected] <mailto:[email protected]> Subject: [NTSysADM] Added second IP to NIC, Radius fails Any idea why this would happen? I've checked all the policy rules, there's nothing tying them to a specific IP. I've bounced the IAS service.
