Adding an SPN to a SQL Server

From: Jason Cetina (jason.cetina_at_click2learn.com)
Date: 06/25/03


Date: Wed, 25 Jun 2003 11:54:18 -0700


I keep getting the following error message over and over:
SuperSocket info: (SpnRegister) : Error 8344.

I've followed the directions in
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_security_2gmm.asp , but
have had no success in getting rid of the error. I can't
connect to or from this machine using native
authentication.

The side note to all this as that I applied the
baseline.inf security template from the Microsoft
Security Operations Guide. The sql server never appears
to actually run on port 1433 (or any other port). We are
running this in a mixed mode AD domain, and trying to use
a different account for the SQL Server service.

Any suggestions?

--
Jason R. Cetina


Relevant Pages

  • Re: Connecting to an alias fails
    ... Real-world stuff I run across with SQL Server: ... Created a new alias with the SQL Server client network utility. ... Edited the Sql Server Network utility to use port 1433 to use port 0 ... , still no success. ...
    (microsoft.public.sqlserver.connect)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)