2. VPN Concentrator 3000 RADIUS issue. error = -9 ("ENOBUFS")
we have a Cisco VPN3000 concentrator and a Crypto-Server radius box
for authentication of the users. This setup was working fine for a
number of months and is now playing up, users in existing groups (with
one exception) and newly created groups will not authenticate:
I am seeing a lot of the following errors in the event log on the VPN
Concentrator:
47114 10/17/2007 14:40:31.980 SEV=5 AUTH/2 RPT=42558
Unable to open socket: server = 192.168.1.50, error = -9 ("ENOBUFS")
47115 10/17/2007 14:40:31.980 SEV=4 AUTH/15 RPT=42701
Server name = 192.168.1.50, type = RADIUS,
group = Group_Name, status = Not-in-service
I have spent a few hours on the phone to the guys at CryptoCard and it
appears that the radius server isn't recieving any authentication
requests from the VPN concentrator. none of the servers appear to be
under any serious load. Has anyone come accross an issue like this
before?
Cheers
Guy
3. [ace-bugs] ACE::send*_n_i functions: isn't ENOBUFS a critical error?
4. VPN3000, radius: error = -9 ("ENOBUFS")
5. connect() returning ENOBUFS on linux
6. sendmsg returns ENOBUFS on AIX 5.3
7. [PATCH] mm: return ENOBUFS instead of ENOMEM in generic_file_buffered_write
9. RAW socket when sendto() always return -1(ENOBUFS) ???????
10. ENOBUFS
11. man sendto ENOBUFS desc. wrong
12. Error Error Error OLEXP Loves Errors
13. HPL Loading error with Fatal error in server row processing - SQL error -271 ISAM error -151
14. Error handling error # 1004 Run-time error
15. Server Error: Error 2 opening registry key.. error