Skip to main content

Security direct access to Enterprise Server Monitor and Control

  • February 16, 2013
  • 2 replies
  • 0 views

Created On:  01 July 2010

Problem:

Security is enabled for the server.  When the user directly accesses ESMAC using http://server.name:port/esmac/casrdo5, They are not challenged for security credentials.  The user is taken directly into ESMAC with the MFUSER.

Resolution:

The solution is to go to http://server.name:port/esmac/casrdo00.  This sets the logon screen and prompts the user to logon.
Incident #2461272
Old KB# 31354

#MFDS
#EnterpriseDeveloper

2 replies

  • Author
  • Rocketeer
  • 19312 replies
  • September 4, 2014
Created On:  01 July 2010

Problem:

Security is enabled for the server.  When the user directly accesses ESMAC using http://server.name:port/esmac/casrdo5, They are not challenged for security credentials.  The user is taken directly into ESMAC with the MFUSER.

Resolution:

The solution is to go to http://server.name:port/esmac/casrdo00.  This sets the logon screen and prompts the user to logon.
Incident #2461272
Old KB# 31354

#MFDS
#EnterpriseDeveloper

I think this does not work the same way now like it used to. When I try this, using “localhost” for the servername and “86” for the port, it takes me to a page which says it can’t be displayed.


  • Author
  • Rocketeer
  • 19312 replies
  • September 5, 2014
Created On:  01 July 2010

Problem:

Security is enabled for the server.  When the user directly accesses ESMAC using http://server.name:port/esmac/casrdo5, They are not challenged for security credentials.  The user is taken directly into ESMAC with the MFUSER.

Resolution:

The solution is to go to http://server.name:port/esmac/casrdo00.  This sets the logon screen and prompts the user to logon.
Incident #2461272
Old KB# 31354

#MFDS
#EnterpriseDeveloper

Rich: MFDS is definitely still part of Enterprise Developer and Enterprise Server (as it always has been). It's MFDS that provides the "Enterprise Server Administration" GUI hosted on port 86. Your system may not be running the MFDS service for some reason; or it may not be resolving "localhost" correctly; or there may be a firewall issue; etc.

Without more information there's really no way to diagnose this.