'NT AUTHORITY \ ANONYMOUS LOGON' failed in SQL Server 2012 on remote server

6

I have a cool running application on my local server. I made some changes to it and prepared to publish a test approval environment. Since we are migrating the local banks and servers to a new data center , I decided to test the new application already pointing to the bank in the new data center . The problem is that now, when I change my connection string to the new server and database, when I run the application in Visual Studio I get the following error:

Erro de Servidor no Aplicativo '/'
Falha no logon do usuário 'integracao'.

ConnectionString

    public const string CONNECTION_STRING = @"Data Source=ITVRS-D08;Initial Catalog=Teste; User Id=integracao;Password=integracao;";
    public const string DEPLOYMENT_CONNECTION_STRING = @"Data Source=ITVRS-D08;Initial Catalog=Teste; User Id=integracao;Password=integracao;";

ConnectionString of the application that was running local

    public const string CONNECTION_STRING = @"Data Source=ITVRS-r08;Initial Catalog=Integracao; User Id=integracao;Password=integracao;";
    public const string DEPLOYMENT_CONNECTION_STRING = @"Data Source=ITVRS-R08;Initial Catalog=Integracao; User Id=integracao;Password=integracao;";

The 'integration' user was created on the new server with the same permissions and such. It is not a permission problem, I believe, since all permissions have already been granted.

The only difference in environment is that the local server is SQL Server 2008 and in the new data center is SQL Server 2012.

Does it have anything to do with this? What else can I check to be able to run my application?

    
asked by anonymous 24.09.2014 / 20:50

3 answers

4

Verify the settings of the SQL TCP services in: All Programs \ SQL Management \ Configuration Tools \ SQL Server Configuration \ SQL Network Configuration \ Protocols for MSSQLSERVER \ TCP / IP on the IP Address tab must contain IP Server and Enabled: yes in all, this also directly implies the form that SQL was installed, such as local system authorities, internet and etc. This is my connection string and works perfectly on the net. An effective test is to open your sql on your computer and try to connect to the server by managment studio.

provider connection string="Data Source=.;Initial Catalog=banco;Persist Security Info=True;User ID=sa;Password=senha
    
17.10.2014 / 14:07
1

Possibly port 1433 on your remote server is not open, or remote SQL Server is not configured to accept remote connections.

To configure remote access on the server, follow the steps in this link .

    
09.10.2014 / 21:19
0

Have you verified that the remote database server allows external access to the IP on which your application is hosted? Generally, database servers limit external access, making it necessary for you to add an exception to the IPs that you want to have access to your server.

If this is the case, follow the details on this page to set up your approval server to allow remote access: link

    
22.10.2014 / 13:57