• State Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    3
  • Views views
    237
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NFR 2.6 - issue scanning Active Directory server - error 298

MigrationDeletedUser
We have NFR 2.6 installed with eDirectory as the primary identity system, and joined to Active Directory. In the past we have not done scans on the Windows servers but there are now a couple we are interested in reporting on. The Discovery process can identify one of the servers, but the other fails with “The specified network could not be resolved”. The log shows the following –

2015-10-01 12:12:55 -14400 3 8008 4464 1228 SR [mwvmp.meadwestvaco.com]: FAILED to get Shares for server xxx-xxxx-xxxxx. Result: 298.

The nfrproxyrights group is a member of domain administrators and is a member of the local administrators group for each of the servers. I also tried to add user nfrproxy directly to the local administrator group for the server that is failing, but this did not help.

Both servers are Windows 2008 R2. Can you suggest anything else that we should check?
  • 0
    On 10/1/2015 3:46 PM, franciske wrote:
    >
    > We have NFR 2.6 installed with eDirectory as the primary identity
    > system, and joined to Active Directory. In the past we have not done
    > scans on the Windows servers but there are now a couple we are
    > interested in reporting on. The Discovery process can identify one of
    > the servers, but the other fails with �The specified network could not
    > be resolved�. The log shows the following �
    >
    > 2015-10-01 12:12:55 -14400 3 8008 4464 1228 SR [mwvmp.meadwestvaco.com]:
    > FAILED to get Shares for server xxx-xxxx-xxxxx. Result: 298.
    >
    > The nfrproxyrights group is a member of domain administrators and is a
    > member of the local administrators group for each of the servers. I
    > also tried to add user nfrproxy directly to the local administrator
    > group for the server that is failing, but this did not help.
    >
    > Both servers are Windows 2008 R2. Can you suggest anything else that we
    > should check?
    >
    >
    Error '298' is a failure to resolve the network name for the server.
    Make certain the server name can be resolved via DNS and NetBIOS (some
    legacy Windows API calls still require a functioning NetBIOS name
    resolution system.) Double-check that the AD computer object exists and
    has the correct DNS hostname for the server, as well. Thanks.

    --

    -- NFMS Support Team
  • 0
    On 10/1/2015 3:46 PM, franciske wrote:
    >
    > We have NFR 2.6 installed with eDirectory as the primary identity
    > system, and joined to Active Directory. In the past we have not done
    > scans on the Windows servers but there are now a couple we are
    > interested in reporting on. The Discovery process can identify one of
    > the servers, but the other fails with �The specified network could not
    > be resolved�. The log shows the following �
    >
    > 2015-10-01 12:12:55 -14400 3 8008 4464 1228 SR [mwvmp.meadwestvaco.com]:
    > FAILED to get Shares for server xxx-xxxx-xxxxx. Result: 298.
    >
    > The nfrproxyrights group is a member of domain administrators and is a
    > member of the local administrators group for each of the servers. I
    > also tried to add user nfrproxy directly to the local administrator
    > group for the server that is failing, but this did not help.
    >
    > Both servers are Windows 2008 R2. Can you suggest anything else that we
    > should check?
    >
    >
    Error '298' is a failure to resolve the network name for the server.
    Make certain the server name can be resolved via DNS and NetBIOS (some
    legacy Windows API calls still require a functioning NetBIOS name
    resolution system.) Double-check that the AD computer object exists and
    has the correct DNS hostname for the server, as well. Thanks.

    --

    -- NFMS Support Team
  • 0 in reply to 
    The server was in the dns but they had to add alias with the fully qualified name. Discovery is now picking up the server. Thanks for your help.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.