Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SEPM NAT Support while remotely exporting the logs

Created: 31 Oct 2013 • Updated: 06 Nov 2013
Infm sec's picture
3 Agree
0 Disagree
+3 3 Votes
Login to vote

Customer can export(save) logs locally from the SEPM. However, it was not happening for the customer to export the logs remotely using Java and Web console from monitors tab in NAT environment

When exporting logs, SEPM firstly generated a CSV file in a temp folder, then returns the file address to the console to save the file. In a NAT environment, for example, external IP was 10.200.42.92, internal IP was 192.168.1.8, the returned URL would be https://192.168.1.8:8445/..., SEPM remote console can't access this URL. So the cause was that the server machine can't get the external IP by current design.

Customer did not face this issue in version 11. So, Customer needed a resolution for this issue in version 12.1 as well.

Customer is central administration team to manage their teams. They support their own internal customers and they manage their internal customer network through the NAT setup.Engineering advised to remove the NAT to resolve the issue. However, It is not possible for them to remove the NAT to get the issue resolved because all the other support has been provided by this SETUP. There is a huge customer base and it is managed by this central team. Everyone is using SEP and customer has stopped upgrading to 12.1 due to this issue and awaiting for the positive response from Symantec to proceed further.

Customer will be very much satisfied if we resolve this scenario and there is no risk for the customer to stay in current version 11. Customer will start upgrading to fixed version if the issue is resolved. So, they can update all their customers to move to this version and it can be managed by this central team.