SCCM integration failing

[pratiksha5]

Does the mid server needs be on the same machine or it can be on any other machine. 

In my present situation, : mid server is configured on machine A ( service account is local user)

The SCCM database is on machine B.. 

A can discover B but the database connection failed. 

Now we have created a database user, and its an ad account. 

We unchcked the use integrated authentication and tried to test connection. Getting authentication failed. 

java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the host serverA.dmain.com, named instance SCCM failed. Error: "java.net.SocketTimeoutException: Receive timed out". Verify the server and instance names and check that no firewall is blocking UDP traffic to port 1434. For SQL Server 2005 or later, verify that the SQL Server Browser Service is running on the host

Telnet from mid server to sql server failing : tried telnet ip address 1433

Question one 1) the User created on sql needs be local or ad is needed?

2) I can discover windows server from same mid server why it's not able to connect?

Please help

[Anshu_Anand_]

Hi @pratiksha5 

1. In the windows host where your database installed, goto the SQL server configuration manager

2. Start the sql server browser if its not running

3. Now goto SQL server network configuration  -> protocols for sqlexpress.

4. Enable the TCP/IP 

5. In IP addresses section of TCP/IP properties , add the TCP port as 1433 if not added under IPALL section

6. Restart the sql server from windows services

Now try again .

If its helpful, please mark answer as correct.

[pratiksha5]

These were already checked. java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. ClientConnectionId:123

[Anshu_Anand_]

What credentials you are using currently for accessing sccm database?

The error message you receive indicates that SQL Server is configured to use Integrated Authentication (Windows Authentication), but the login is being attempted from a domain that SQL Server does not trust.

[pratiksha5]

I am using Use integrated authentication. It will not need a password. Confirm one thing : if I use integrated authentication and the logon as service is a local account on the mid server then it will not work, right? The log-on as a service needs to be a domain account.