Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Running SSIM console through firewall (externally)

Updated: 21 May 2010 | 6 comments
shaun_b's picture
0 0 Votes
Login to vote

Has anyone had any success with running the SSIM console externally through a firewall? Basically we want to be able to use the SSIM console remotely, and I have created the necessary firewall rules to do so. However I keep getting an error with "the notification service is not running" when trying to login. packet dumps show that the only protocol that it's trying to use is HTTPS. However it keeps on failing. I've tried this KB article as well... http://service1.symantec.com/support/ent-gate.nsf/...

anyone do this successfully? without using an SSL VPN or any other remote access software? 

discussion Filed Under:

Comments

Laurent_c's picture
03
Jun
2009
0 Votes 0
Login to vote

I would think only https was

I would think only https was needed to connect to the manager.

Would it be the NATing that cause problem and the packets back from the manager to the console are lost ? Do you see any unusual trace in the tcpdump ?

antilles's picture
04
Jun
2009
0 Votes 0
Login to vote

https & ldaps

I think that also ldaps (636) is needed to connect the manager, because during logon you must be authenticated against SSIM ldap user database.

Intasunta N.'s picture
04
Jun
2009
0 Votes 0
Login to vote

https (443) and ldaps (636)

https (443) and ldaps (636) is prerequisite port to permit/allow if you connect  SSIM console through firewall

Laurent_c's picture
04
Jun
2009
0 Votes 0
Login to vote
Laurent_c's picture
04
Jun
2009
0 Votes 0
Login to vote

And if you really want to

And if you really want to fine tune your firewall use this KB http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

shaun_b's picture
04
Jun
2009
0 Votes 0
Login to vote

Got it...

Was actually related to a local DNS host entry on the SSIM  that conflicted with the external dns name. All i needed was port 443. Thanks all!