Is designed for use by NHS Organisations whose computers or servers are or can be made visible to NHSN3.

The IP ports and protocols that are supported can be seen if you click here.

Example 1: A GP Surgery running its main system on a server with IP address 172.1.1.1. Normally this IP address cannot be seen on N3 because the managed router includes firewall functionality that stops outside users seeing the address. The routers firewall can be adopted so that this address can be seen on N3. The router can also be configured to let into the surgery network other known source IP addresses. When a VPN User connects to N3 using the Token Only service they are given a known IP address. This needs to be configured into the N3 managed router on the surgery network. In this way a GP working from home can connect to N3 and attach to his surgery system through the managed router transparently.

Example 2: A Trust is running thin client services for remote users, e.g. Citrix. The IP address of the Citrix server is made visible to N3 either by directly using a registered IP address or employing NAT.The firewall and managed N3 router at the Trust are configured to let into the network from N3 users with known IP addresses (the Trust is given the list of known IP addresses when the service is set up). In this way remote users can work from home and access desktop services through Citrix.

Is designed for use by NHS Organisations whose computers servers are not or cannot be made visible to N3. Or want to provide users with the same logon process from home as they have when working in the office.

In simple terms, the On Site VPN Concentrator enables users to do remotely exactly what they can do when connected directly to the corporate LAN.