setspn -r returns Failed to crack name Domain\Servername into the FQDN, (0) 1 0x2

  • Thread starter Thread starter Charles Braun
  • Start date Start date
C

Charles Braun

Hello,

When I run C:\>setspn -L servername I get the following response:
Registered ServicePrincipalNames for
CN=servername,OU=Servers,OU=Network,DC=domain:

Note that no SPNs are listed.

Then when I run C:\>setspn -R servername I get the following response:
Failed to crack name Domain\Servername into the FQDN, (0) 1 0x2

If I run C:\>setspn -R domain\servername I get the following response:
Could not find account Server's FQDN

Any thoughts on how I can set the SPN for this server? I am running the
command from the console as a domain admin.
 
Charles Braun said:
Hello,

When I run C:\>setspn -L servername I get the following response:
Registered ServicePrincipalNames for
CN=servername,OU=Servers,OU=Network,DC=domain:

Note that no SPNs are listed.

Then when I run C:\>setspn -R servername I get the following response:
Failed to crack name Domain\Servername into the FQDN, (0) 1 0x2

If I run C:\>setspn -R domain\servername I get the following response:
Could not find account Server's FQDN

Any thoughts on how I can set the SPN for this server? I am running the
command from the console as a domain admin.
Click to expand...

No suggestions huh? Bummer :-(
 
If your system is missing the SPN'd then there is probably something else
wrong. Check this out.

start/run adsiedit.msc

Once you are in adsiedit, goto the following:

Domain NC then goto the servers or the dc's ou as need. Highlight the server
name then do a right click and properties. On the attributes tab, goto
Select a property to view and choice the servicePrincipalName property. You
can add then there.

As I mentioned before if you don't see what you need, if possible you might
want to rejoin the server to the domain, as there is probably something else
wrong as to why they weren't added.

--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
 
Charles Braun said:
If your system is missing the SPN'd then there is probably something else
wrong. Check this out.

start/run adsiedit.msc

Once you are in adsiedit, goto the following:

Domain NC then goto the servers or the dc's ou as need. Highlight the
Click to expand...
server name then do a right click and properties. On the attributes tab,
goto Select a property to view and choice the ServicePrincipalName property.
You can add then there.
As I mentioned before if you don't see what you need, if possible you
Click to expand...
might want to rejoin the server to the domain, as there is probably
something else wrong as to why they weren't added.Please reply to the newsgroup so that others may benefit.

Brian,

That did the trick. Thank you. Can I ask, is this tip available somewhere in
the MS KB? I tore apart the KB and googled for at least an hour before
posting here after not finding an answer anywhere. Did I just miss it, or
can you point me to a location where this is documented?

Thanks again,

Charles
 
I got it from the guy who sits across the cube row. :) I'll see if I there
is anything public, if not we'll work on that. :)

--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
Charles Braun said:
If your system is missing the SPN'd then there is probably something else
wrong. Check this out.

start/run adsiedit.msc

Once you are in adsiedit, goto the following:

Domain NC then goto the servers or the dc's ou as need. Highlight the
Click to expand...
server name then do a right click and properties. On the attributes tab,
goto Select a property to view and choice the ServicePrincipalName property.
You can add then there.
As I mentioned before if you don't see what you need, if possible you
Click to expand...
might want to rejoin the server to the domain, as there is probably
something else wrong as to why they weren't added. rights.
Please reply to the newsgroup so that others may benefit.

Brian,

That did the trick. Thank you. Can I ask, is this tip available somewhere in
the MS KB? I tore apart the KB and googled for at least an hour before
posting here after not finding an answer anywhere. Did I just miss it, or
can you point me to a location where this is documented?

Thanks again,

Charles
Click to expand...
 
Back
Top