franciske Absent Member.
Absent Member.
1664 views

NFR 2.6 - issue scanning Active Directory server - error 298

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 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: NFR 2.6 - issue scanning Active Directory server - error 298

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 Likes
franciske Absent Member.
Absent Member.

Re: NFR 2.6 - issue scanning Active Directory server - error

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.
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.