Bindings (ports) not working on new SM upgrad to current release
Question asked by Ben Conner - February 10 at 10:19 AM
Unanswered
Good morning,

I updated SM to the current release from an older version (14.5).  While long, the upgrade went well, until I tested port access.  SM shows the bindings assigned to ports (25/110/587/etc) but none of them respond to a telnet command (telnet 10.0.1.16 110/25/etc or telnet 127.0.0.1 25/etc).  I can get to the web UI without issues.

I did populate the localhost binding with 25 and 110 prior to testing that.

TCPView also shows no open ports on the standard mail ports.

Any ideas on what might be happening?

Thanks!

--Ben

1 Reply

Reply to Thread
0
Sébastien Riccio Replied
Is that a licensed SM ? The installer/updater asks you for your license at install time, but it's ignored. You need to re-license it from the web admin after te install to have it fully registered.
In our cas this was preventing services to answer until we register it again...

Reply to Thread