neilmurphy Absent Member.
Absent Member.
5094 views

NFRAdmin Login Issues

Hi,

I may be going over old ground here but here it goes.

I am evaluating NFR without using NRM. I have installed and configured the following on a Windows 2008 SP1 server:


  • NFR Active Directory Service Interface
  • NFR Engine
  • NFR Admin


When I launch NFR Admin I get a login interface. I am assuming that the port number should be 3033 and my login name should be some user that is a member of the NFRAdmins group.

Every time I login I get a warning "Could not communicate with the engine".

I have checked that all services are running. I have disabled my IE proxy settings. I also created a NFRAdmin.exe.config file as suggested in a previous thread. Nothing seems to work.

Has anybody got any further suggestions?

Neil.
0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: NFRAdmin Login Issues

Neil,
When logging in with NFRAdmin you will need to log into the DSI on port
3009, if using the defaults.

thanks,
NFMS Team

On 4/8/2010 12:16 PM, neilmurphy wrote:
>
> Hi,
>
> I may be going over old ground here but here it goes.
>
> I am evaluating NFR without using NRM. I have installed and configured
> the following on a Windows 2008 SP1 server:
>
>
> - NFR Active Directory Service Interface
> - NFR Engine
> - NFR Admin
>
>
> When I launch NFR Admin I get a login interface. I am assuming that the
> port number should be 3033 and my login name should be some user that is
> a member of the NFRAdmins group.
>
> Every time I login I get a warning "Could not communicate with the
> engine".
>
> I have checked that all services are running. I have disabled my IE
> proxy settings. I also created a NFRAdmin.exe.config file as suggested
> in a previous thread. Nothing seems to work.
>
> Has anybody got any further suggestions?
>
> Neil.
>
>

0 Likes
neilmurphy Absent Member.
Absent Member.

Re: NFRAdmin Login Issues

Hi,
When I use port 3009, I get this error:

"Could not get File Reporter Engine URL (149)"

I have used default port numbers throughout.

Neil.

Novell File Management Suite Team;1960151 wrote:
Neil,
When logging in with NFRAdmin you will need to log into the DSI on port
3009, if using the defaults.

thanks,
NFMS Team

On 4/8/2010 12:16 PM, neilmurphy wrote:
>
> Hi,
>
> I may be going over old ground here but here it goes.
>
> I am evaluating NFR without using NRM. I have installed and configured
> the following on a Windows 2008 SP1 server:
>
>
> - NFR Active Directory Service Interface
> - NFR Engine
> - NFR Admin
>
>
> When I launch NFR Admin I get a login interface. I am assuming that the
> port number should be 3033 and my login name should be some user that is
> a member of the NFRAdmins group.
>
> Every time I login I get a warning "Could not communicate with the
> engine".
>
> I have checked that all services are running. I have disabled my IE
> proxy settings. I also created a NFRAdmin.exe.config file as suggested
> in a previous thread. Nothing seems to work.
>
> Has anybody got any further suggestions?
>
> Neil.
>
>
0 Likes
jjader Absent Member.
Absent Member.

Re: NFRAdmin Login Issues

Shouldn't the port be 8009?

- Joakim Jader
0 Likes
neilmurphy Absent Member.
Absent Member.

Re: NFRAdmin Login Issues

jjader;1961264 wrote:
Shouldn't the port be 8009?


I've tried that. I get "Could not communicate with the engine"
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: NFRAdmin Login Issues

Neil,
I understand that your using the non NSM integrated version of the DSI
for AD, correct?

In order to login you will need to log into the DSI's ip address with
the 3009 port number if on AD. Is the DSI service running?

The 8009 port number is only used with the NSM Integrated eDirectory
version where the NSMEngin.NLM acts as the DSI.

thanks,
NFMS Team

On 4/13/2010 9:06 AM, neilmurphy wrote:
>
> jjader;1961264 Wrote:
>> Shouldn't the port be *8*009?

>
> I've tried that. I get "Could not communicate with the engine"
>
>

0 Likes
neilmurphy Absent Member.
Absent Member.

Re: NFRAdmin Login Issues

Correct, I am not using the NSM integrated version. DSI is installed and running on the same server.

Having tried repeatedly to get NFM running in standalone, I have now uninstalled it and am trying to install it along with NSM but I am now getting all sorts of authentication errors. I am now going to transfer all my issues to the NSM forrum.


Novell File Management Suite Team;1962007 wrote:
Neil,
I understand that your using the non NSM integrated version of the DSI
for AD, correct?

In order to login you will need to log into the DSI's ip address with
the 3009 port number if on AD. Is the DSI service running?

The 8009 port number is only used with the NSM Integrated eDirectory
version where the NSMEngin.NLM acts as the DSI.

thanks,
NFMS Team

On 4/13/2010 9:06 AM, neilmurphy wrote:
>
> jjader;1961264 Wrote:
>> Shouldn't the port be *8*009?

>
> I've tried that. I get "Could not communicate with the engine"
>
>
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.