Realm: rbht.nhs.uk Full
rbht.nhs.uk/rbht-nhs-uk-0/roaming0.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Sun Jan 4 13:27:27 2026
- Last Check
- Sat Jan 17 02:44:26 2026
- Next Check
- Sat Jan 17 02:54:26 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-0/roaming0.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 09:00:49 2025
- Last Check
- Sat Jan 17 02:48:45 2026
- Next Check
- Sat Jan 17 02:58:45 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-0/roaming0.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Wed Jan 7 00:37:09 2026
- Last Check
- Sat Jan 17 02:47:07 2026
- Next Check
- Sat Jan 17 02:57:07 2026
rbht.nhs.uk/rbht-nhs-uk-0/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Fri Dec 5 16:01:04 2025
- Last Check
- Sat Jan 17 02:51:00 2026
- Next Check
- Sat Jan 17 03:01:00 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-0/roaming0.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Jan 8 15:26:49 2026
- Last Check
- Sat Jan 17 02:46:47 2026
- Next Check
- Sat Jan 17 02:56:47 2026
rbht.nhs.uk/rbht-nhs-uk-0/NRPS: roaming1.govroam.uk
(212.219.209.43) -
No Route
/
Host Down
/
Config pending
/
IPS firewall
/
rbht.nhs.uk/rbht-nhs-uk-0/roaming1.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Fri Dec 26 01:31:21 2025
- Last Check
- Sat Jan 17 02:48:19 2026
- Next Check
- Sat Jan 17 02:58:18 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-0/roaming1.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 08:57:37 2025
- Last Check
- Sat Jan 17 02:45:32 2026
- Next Check
- Sat Jan 17 02:55:32 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-0/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Wed Jan 14 16:19:22 2026
- Last Check
- Sat Jan 17 02:47:21 2026
- Next Check
- Sat Jan 17 02:57:21 2026
rbht.nhs.uk/rbht-nhs-uk-0/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Dec 2 08:55:48 2025
- Last Check
- Sat Jan 17 02:43:44 2026
- Next Check
- Sat Jan 17 02:53:44 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-0/roaming1.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Dec 11 06:45:15 2025
- Last Check
- Sat Jan 17 02:45:13 2026
- Next Check
- Sat Jan 17 02:55:13 2026
rbht.nhs.uk/rbht-nhs-uk-0/NRPS: roaming2.govroam.uk
(212.219.247.59) -
No Route
/
Host Down
/
Config pending
/
IPS firewall
/
rbht.nhs.uk/rbht-nhs-uk-0/roaming2.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Tue Dec 2 08:51:12 2025
- Last Check
- Sat Jan 17 02:48:12 2026
- Next Check
- Sat Jan 17 02:58:12 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-0/roaming2.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 08:50:46 2025
- Last Check
- Sat Jan 17 02:48:41 2026
- Next Check
- Sat Jan 17 02:58:41 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-0/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Wed Jan 14 16:21:17 2026
- Last Check
- Sat Jan 17 02:49:15 2026
- Next Check
- Sat Jan 17 02:59:15 2026
rbht.nhs.uk/rbht-nhs-uk-0/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Dec 2 08:53:05 2025
- Last Check
- Sat Jan 17 02:51:02 2026
- Next Check
- Sat Jan 17 03:01:02 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-0/roaming2.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Fri Jan 16 15:21:32 2026
- Last Check
- Sat Jan 17 02:51:28 2026
- Next Check
- Sat Jan 17 03:01:28 2026
rbht.nhs.uk/rbht-nhs-uk-0/NRPS: roaming3.govroam.uk
(195.194.21.203) -
No Route
/
Host Down
/
Config pending
/
IPS firewall
/
rbht.nhs.uk/rbht-nhs-uk-0/roaming3.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Tue Dec 2 08:40:22 2025
- Last Check
- Sat Jan 17 02:47:21 2026
- Next Check
- Sat Jan 17 02:57:21 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-0/roaming3.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 08:40:16 2025
- Last Check
- Sat Jan 17 02:48:11 2026
- Next Check
- Sat Jan 17 02:58:11 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-0/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Sun Jan 11 22:37:52 2026
- Last Check
- Sat Jan 17 02:47:51 2026
- Next Check
- Sat Jan 17 02:57:51 2026
rbht.nhs.uk/rbht-nhs-uk-0/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Dec 2 08:41:09 2025
- Last Check
- Sat Jan 17 02:49:06 2026
- Next Check
- Sat Jan 17 02:59:05 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-0/roaming3.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Thu Dec 25 13:27:56 2025
- Last Check
- Sat Jan 17 02:47:54 2026
- Next Check
- Sat Jan 17 02:57:54 2026
rbht.nhs.uk/rbht-nhs-uk-1/roaming0.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Sun Dec 14 09:01:47 2025
- Last Check
- Sat Jan 17 02:48:47 2026
- Next Check
- Sat Jan 17 02:58:47 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-1/roaming0.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 09:01:29 2025
- Last Check
- Sat Jan 17 02:49:25 2026
- Next Check
- Sat Jan 17 02:59:25 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-1/roaming0.govroam.uk/
Server Shared Secret
- Output
- OK: Good shared secret over last day
- Last State Change
- Wed Jan 7 00:19:06 2026
- Last Check
- Sat Jan 17 02:49:05 2026
- Next Check
- Sat Jan 17 02:59:05 2026
rbht.nhs.uk/rbht-nhs-uk-1/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Dec 2 09:01:11 2025
- Last Check
- Sat Jan 17 02:49:08 2026
- Next Check
- Sat Jan 17 02:59:08 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-1/roaming0.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Tue Dec 2 09:00:37 2025
- Last Check
- Sat Jan 17 02:48:36 2026
- Next Check
- Sat Jan 17 02:58:36 2026
rbht.nhs.uk/rbht-nhs-uk-1/NRPS: roaming1.govroam.uk
(212.219.209.43) -
No Route
/
Host Down
/
Config pending
/
IPS firewall
/
rbht.nhs.uk/rbht-nhs-uk-1/roaming1.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Tue Jan 13 16:44:55 2026
- Last Check
- Sat Jan 17 02:41:54 2026
- Next Check
- Sat Jan 17 02:51:54 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-1/roaming1.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 08:55:26 2025
- Last Check
- Sat Jan 17 02:43:21 2026
- Next Check
- Sat Jan 17 02:53:21 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-1/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Wed Jan 14 16:31:41 2026
- Last Check
- Sat Jan 17 02:49:39 2026
- Next Check
- Sat Jan 17 02:59:39 2026
rbht.nhs.uk/rbht-nhs-uk-1/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Dec 2 08:54:31 2025
- Last Check
- Sat Jan 17 02:42:27 2026
- Next Check
- Sat Jan 17 02:52:27 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-1/roaming1.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Tue Jan 6 14:25:51 2026
- Last Check
- Sat Jan 17 02:45:51 2026
- Next Check
- Sat Jan 17 02:55:50 2026
rbht.nhs.uk/rbht-nhs-uk-1/NRPS: roaming2.govroam.uk
(212.219.247.59) -
No Route
/
Host Down
/
Config pending
/
IPS firewall
/
rbht.nhs.uk/rbht-nhs-uk-1/roaming2.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Sun Jan 11 10:31:20 2026
- Last Check
- Sat Jan 17 02:48:19 2026
- Next Check
- Sat Jan 17 02:58:19 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-1/roaming2.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 08:54:08 2025
- Last Check
- Sat Jan 17 02:42:04 2026
- Next Check
- Sat Jan 17 02:52:04 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-1/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Wed Jan 14 16:00:10 2026
- Last Check
- Sat Jan 17 02:48:08 2026
- Next Check
- Sat Jan 17 02:58:08 2026
rbht.nhs.uk/rbht-nhs-uk-1/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Dec 2 08:51:48 2025
- Last Check
- Sat Jan 17 02:49:45 2026
- Next Check
- Sat Jan 17 02:59:45 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-1/roaming2.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Tue Dec 2 08:53:11 2025
- Last Check
- Sat Jan 17 02:51:10 2026
- Next Check
- Sat Jan 17 03:01:10 2026
rbht.nhs.uk/rbht-nhs-uk-1/NRPS: roaming3.govroam.uk
(195.194.21.203) -
No Route
/
Host Down
/
Config pending
/
IPS firewall
/
rbht.nhs.uk/rbht-nhs-uk-1/roaming3.govroam.uk/
Ping
- Output
- PING CRITICAL - Packet loss = 100%
- Last State Change
- Tue Jan 13 22:06:47 2026
- Last Check
- Sat Jan 17 02:43:46 2026
- Next Check
- Sat Jan 17 02:53:45 2026
- Meaning:
- A failed Ping test means that ICMP packets are either not getting to the server, or the responses aren't getting back.
- Solution:
- Check your firewall logs to see if the packets are arriving. If not, check your routing. If they are, then check to see if they're being DROPed or REJECTed. If you're confident that a response is being sent then please let Jisc know at govroam@jisc.ac.uk
rbht.nhs.uk/rbht-nhs-uk-1/roaming3.govroam.uk/
RADIUS Port
- Output
- CRITICAL: No response. Host down or firewall dropping new connections
- Last State Change
- Tue Dec 2 08:39:52 2025
- Last Check
- Sat Jan 17 02:47:48 2026
- Next Check
- Sat Jan 17 02:57:48 2026
- Meaning:
- A simple port scan of port 1812/udp was attempted and there was no response from the port. This implies that either the port is not open i.e. there isn't a daemon running on it, or that there is a firewall configured to not to respond to such scans. Dropping such packets isn't a problem as long as the server is able to respond to RADIUS auth requests.
- Solution:
- Check the state of the RADIUS daemon and ensure that it's up and running on port 1812/udp. If it is, then check your firewall(s) to see if they're configured to drop incoming connections.
rbht.nhs.uk/rbht-nhs-uk-1/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Dec 2 08:41:56 2025
- Last Check
- Sat Jan 17 02:49:57 2026
- Next Check
- Sat Jan 17 02:59:55 2026
rbht.nhs.uk/rbht-nhs-uk-1/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Dec 2 08:42:54 2025
- Last Check
- Sat Jan 17 02:50:51 2026
- Next Check
- Sat Jan 17 03:00:51 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
rbht.nhs.uk/rbht-nhs-uk-1/roaming3.govroam.uk/
Zombie
- Output
- UNKNOWN: No Data. No data but not marked as down within the last week
- Last State Change
- Tue Dec 2 08:38:21 2025
- Last Check
- Sat Jan 17 02:46:19 2026
- Next Check
- Sat Jan 17 02:56:19 2026
Called Station ID Check
- Output
- WARNING: 100% Missing SSID, as of 2026-01-16 17:49:02. 100% MAC format wrong - should use a '-' to separate hex pairs (last: 2026-01-16 17:49:02)
- Last State Change
- Wed Jan 7 00:11:32 2026
- Last Check
- Sat Jan 17 02:41:28 2026
- Next Check
- Sat Jan 17 02:56:28 2026
- Meaning:
-
The Called-Station-ID contains the MAC address of the device the client
connects to as well as, potentially, the SSID of the wireless network it
connected to. The format of the MAC address is specified in RFC
3580 as
'XX-XX-XX-XX-XX-XX:SSID' with '-' being the only valid separator and all
upper case. The SSID should be appended.
Having the Called-Station-ID included in proxied requests makes it possible to ensure that the SSID being broadcast matches the service requirements. - Solution:
- Configure your wireless system to provide the CSI in the RFC3580 format.
Calling Station ID Check
- Output
- WARNING: 100% MAC format wrong, missing separator (last: 2026-01-16 17:49:02)
- Last State Change
- Wed Jan 7 00:11:39 2026
- Last Check
- Sat Jan 17 02:41:37 2026
- Next Check
- Sat Jan 17 02:56:36 2026
- Meaning:
- Calling Station ID identifies the device making the connection and RFC 3580 states that the format should be XX-XX-XX-XX-XX-XX (i.e. '-' separated and upper case).
- Solution:
- Configure your wireless system to use upper case and '-' separated pairs.
Operator Check
- Output
- OK: 100% Operator-Name present (last: 2026-01-16 17:49:02)
- Last State Change
- Wed Jan 7 00:16:01 2026
- Last Check
- Sat Jan 17 02:46:02 2026
- Next Check
- Sat Jan 17 03:01:00 2026
Realm Syntax Check
- Output
- OK: 100.0% Good syntax (last: 2026-01-16 17:49:02)
- Last State Change
- Wed Jan 7 00:16:50 2026
- Last Check
- Sat Jan 17 02:46:45 2026
- Next Check
- Sat Jan 17 03:01:45 2026
VLAN Check
- Output
- OK: 100% No VLAN attr present (last: 2026-01-16 17:49:02)
- Last State Change
- Wed Jan 7 00:16:57 2026
- Last Check
- Sat Jan 17 02:46:53 2026
- Next Check
- Sat Jan 17 03:01:53 2026