SQL Server Authentication across domains

• Craig-222689

  SSC Enthusiast

  Points: 132

  More actions

  August 31, 2006 at 6:24 am

  #67743

  Visual Studio 2003; ASP.Net; .Net Framework 1.1, SQL Server 2000

  Hi,

  We have two domains in our network - prod.domain.com and dev.domain.com. There is no trust relationship between the two domains. I am trying to connect to an SQL Server in dev.domain.com using SQL Server Authentication from prod.domain.com. My connection string uses the fully qualified domain name (xxxxxx.dev.domain.com) to connect. The error I receive is SQL Server does not exist or access denied. I can access the database through SQL Query Analyser and SQL Enterprise Manager across the domains with no problems. I can also connect through a .udl file using the same SQL Server Authentication information.

  If I run my application from dev.domain.com accessing a database that sits in prod.domain.com then the connection is fine.

  Can someone point me in the direction of any areas I can troubleshoot to see what is preventing the connection please? The only things I can see on the web are details of windows authentication across domains which isn't relevant to me in this instance. I've been pulling what little hair I have out over this for the last week.

  Thanks in advance.

• Rudyx - the Doctor

  SSC-Forever

  Points: 43695

  More actions

  September 1, 2006 at 9:43 am

  #658074

  Since you are using SQL Server authentication the issue of different domains should not matter. I'd first try to ping the SQL Server. If that works then try a telnet to port 1433 or the port that the target SQL Server is listening on. My guess is that both of these will fail. If that is the case then look at:

  • firewalls
  • IPSec
  • vlan routing

  RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

• Craig-222689

  SSC Enthusiast

  Points: 132

  More actions

  September 1, 2006 at 9:46 am

  #658075

  Thanks Rudy - it was something to do with the ports.