Products
Applications
Support
Company
How To Buy
Skip to main content (Press Enter).
Sign in
Skip auxiliary navigation (Press Enter).
Register
Skip main navigation (Press Enter).
Toggle navigation
Search Options
Home
My Communities
Communities
All Communities
Enterprise Software
Mainframe Software
Symantec Enterprise
Blogs
All Blogs
Enterprise Software
Mainframe Software
Symantec Enterprise
Events
All Events
Enterprise Software
Mainframe Software
Symantec Enterprise
VMware
Water Cooler
Groups
Enterprise Software
Mainframe Software
Symantec Enterprise
Members
Endpoint Protection
View Only
Community Home
Threads
Library
Events
Members
Back to Library
After Upgrade SEPM to 14.3 RU1 Client cannot connect
0
Recommend
Dec 22, 2020 10:19 PM
IPA IT Dept
Statistics
0 Favorited
31 Views
1 Files
0 Shares
2 Downloads
Attachment(s)
ssl.png
19 KB
1 version
Uploaded - Dec 22, 2020
Download
Download Document
Please accept the terms of the copyright associated with this attachment before downloading it. Click the link below to read the terms.
Accept
Tags and Keywords
Comments
Joseph Gray
Jan 13, 2021 05:01 PM
We are having a similar problem with our SEP environment - There is a Key mismatch between MSL policies, clients and the management server - however, we are lucky that it does not seem to be a problem On VPN / local to the network. Our persistent problem has been clients not communicating back to the server OFF VPN unless they are running client version 14.0 RU1. We have a case open for this, but Broadcom's proposed short term fix is to downgrade the clients to version 14.0 RU1 while its still supported. 14.2 RU2 seems to negate the mismatch and communicate ONLY while ON VPN or local to the network. I tested a pre-release version of 14.3 and saw the same behavior (14.3 MP1).
Related Entries and Links
No Related Resource entered.
Copyright 2019. All rights reserved.
Powered by Higher Logic