- Managing Wi-Fi, VPN, BlackBerry Secure Connect Plus, and other work connections
- Managing work connections using profiles
- Best practice: Creating work connection profiles
- Setting up work Wi-Fi networks for devices
- Setting up work VPNs for devices
- Setting up proxy profiles for devices
- Using BlackBerry Secure Connect Plus for connections to work resources
- Steps to enable BlackBerry Secure Connect Plus
- Server and device requirements for BlackBerry Secure Connect Plus
- Installing additional BlackBerry Secure Connect Plus components in an on-premises environment
- Installing or upgrading the BlackBerry Secure Connect Plus component in a cloud environment
- Enable BlackBerry Secure Connect Plus
- Specify the DNS settings for the BlackBerry Connectivity app
- Optimize secure tunnel connections for Android devices that use BlackBerry Dynamics apps
- Troubleshooting BlackBerry Secure Connect Plus
- Using BlackBerry 2FA for secure connections to critical resources
- Setting up single sign-on authentication for devices
- Setting up DNS profiles for iOS and macOS devices
- Managing email and web domains for iOS devices
- Controlling network usage for apps on iOS devices
- Filtering web content on iOS devices
- Configuring AirPrint and AirPlay profiles for iOS devices
- Configuring Access Point Names for Android devices
- BlackBerry Docs
- BlackBerry UEM 12.18
- Administration
- Securing network connections
- Using BlackBerry Secure Connect Plus for connections to work resources
- Troubleshooting BlackBerry Secure Connect Plus
- BlackBerry Secure Connect Plus does not start
BlackBerry Secure Connect Plus does not start
BlackBerry Secure Connect Plus
does not startPossible cause
The TCP/IPv4 settings
for the
BlackBerry Secure Connect Plus
Adapter might not be
correct.Possible solution
In
Network Connections > BlackBerry Secure Connect Plus
Adapter > Properties > Internet Protocol Version 4 (TCP/IPv4) >
Properties
, verify that Use the following IP
address
is selected, with the following default values:- IP address: 172.16.0.1
- Subnet mask: 255.255.0.0
If necessary, correct these settings and restart the
server.