Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to Remote Access, different domain

Status
Not open for further replies.
May 24, 2006
219
US
I would like to administer a remote SQL Server (2000) from our office using our local copy of SQL Server Enterprise Manager.

I can telnet using port 1433, and the SQL Server is using 1433.

I can connect to the remote server using Remote Desktop and can see the following:

Under Properties > Security of the remote SQL Server, SQL Server and Windows authentication is chosen.

Under "Edit SQL Server Registration" Use Windows authentication is chosen.

I know the sa password.. but I am in a totally different domain, and I am NOT set up as a user in the remote Active Directory. There are no trust relationships set up between our two domains.

I have full admin privileges on the remote AD and SQL Server, but I just don't know how to complete this connection. Since "Use Windows Authentication" is chosen on the remote SQL Server, do I have to set myself up as a user in its AD? Recall that I'm logged in to a different domain here... How can I add my login here as an authenticated user on the remote AD? And thus in SQL Server? Or do I even need to?
 
Also, I'm using the external IP address in my EM here... the same IP address that I can telnet to...

BUT from the remote SQL Server, if I go to I see a different IP address than I used to telnet to... and that I Remote Desktop to.

Should I be using the IP address that I can telnet to and Remote Desktop to, or the whatismyip address? (I think the former.)
 
Since there is no domain trust between the domains, you'll have to setup a SQL Server account on the remote machine, and connect with that account. You won't be able to connect Windows Auth.

The problem with this is that by default the connection isn't encrypted so the username and password will be transmitted over the internet via plain text. You'll want to enable encryption on the connection so that your sysadmin username and password aren't in plain text.

You will want to connect via the IP Address that you can connect with (the former of the two you gave).

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
If you can't get access to the server on the remote domain, you'll have to ask someone on that domain to set you up with access to the server.

One of my clients had a windows account added to the remote domain, then mapped the remote AD account to SQL as well as getting it set up to where he could use Remote Desktop Connection to get into the server. Once that was done, all he had to do was put in the public IP of the remote SQL Server and he could manage it from a terminal services session on his own PC.

Hope that helps.


Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top