If the DSM SA Connection Service stops, often it is because it is not able to open the port it wants. The default port is 1311. If you locate the iws.ini file in the OMSA install directories you can edit it with Notepad and change the port on the 6th line. It will probably say "port = 1311", just change the port number to something else like 100010, save the file, and see if the service will start. Then access OMSA with:
Thank you for your help! that worked perfectly. Out of curiousity, what are some reasons that port 1311 could be in use? to my knowledge nothing else on the server is using that port. Is this a common issue? Before I posted here i checked netstat -a and port 1311 was listening, and I could also telnet to it. I am just wondering what to look out for in the future.
Another problems is perhaps there is an incompatibility between an older browser and newer OMSA. The newer OMSA requires TLS 1.1 or 1.2 support. Some older browsers will not support that.
Some browsers will support it, but have it turned off by default.
I recommend to enable TLS 1.1 and 1.2 and disable SSL2, SSL3, and TLS 1.0
You can also access the OMSA from another computer using the FQDN in case the one it is on does not have those options...or install a third party modern browser.
DELL-Jeff M
2 Intern
•
793 Posts
1
May 10th, 2011 17:00
If the DSM SA Connection Service stops, often it is because it is not able to open the port it wants. The default port is 1311. If you locate the iws.ini file in the OMSA install directories you can edit it with Notepad and change the port on the 6th line. It will probably say "port = 1311", just change the port number to something else like 100010, save the file, and see if the service will start. Then access OMSA with:
https://server:10010
jwesley123
2 Posts
0
May 10th, 2011 19:00
Thank you for your help! that worked perfectly. Out of curiousity, what are some reasons that port 1311 could be in use? to my knowledge nothing else on the server is using that port. Is this a common issue? Before I posted here i checked netstat -a and port 1311 was listening, and I could also telnet to it. I am just wondering what to look out for in the future.
Thanks again for your help!
TheTechWolf
6 Posts
1
October 25th, 2018 12:00
Another problems is perhaps there is an incompatibility between an older browser and newer OMSA. The newer OMSA requires TLS 1.1 or 1.2 support. Some older browsers will not support that.
Some browsers will support it, but have it turned off by default.
I recommend to enable TLS 1.1 and 1.2 and disable SSL2, SSL3, and TLS 1.0
You can also access the OMSA from another computer using the FQDN in case the one it is on does not have those options...or install a third party modern browser.