remote desktop into 1

[onressy]

Hi I have a webserver and sql2005 on a 10.10. backbone. The sql server is not connect to the net. Normally i don't need to get into the db server as i can see data using serverSide coding on a web page. but sometimes i need to get into it. Normally i remote desktop into the webserver (since both web and db are on a server farm) then i remove into the db server from the webserver then i instantiate Management studio. Now my question:
Is there a way to use the local management studio, on my compter, to access the db?

 

[SQLBill]

Can you connect to the server from your local computer? If so, then you can register the server in your local Management Studio.

-SQLBill

Posting advice: FAQ481-4875

 

[Catadmin]

If the server is on the same internal network as your PC, you should be able to connect via SSMS. Because of the way 2k5 searches for SQL instances, though, I advise connecting to it with the "ServerName, Port#" syntax instead of the old 2000 method of "ServerName".

Of course, if your instances are named, you'll have to put it after ServerName like: "ServerName\Instance, Port#".

We've actually got a cluster environment where each of our Instances has a different virtual servernames, so we can use that instead of the ServerName\Instance name if we want. Check and see if you have the same set up.



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"

 

[onressy]

Thankyou both!

 

[onressy]

The sql server is not on the same network as my local, i would like to somehow hop thru the webserver to db on the back end, is this possible, maybe with 3rd party software?

Thanks, sorry for the delayed response!

 

[Catadmin]

There are several issues with SQL Servers not on the same network.

1) Is it just a different subnet or a completely different domain/network set up?

2) Has the SysAdmin of the other network given you & your login any permissions on the remote server?

3) Do you have a port open on the firewall to connect to the remote server?

4) Does your domain even trust the other domain? If not, then your chances of getting connected are pretty bad.

5) Have you (and the remote server's SysAdmin) set up linked servers with the two boxes?

Check all these to find out the answers. If the SQL Server is not even on a network (as in on a server that is physically not connected to an internal or external network), then you're not going to be able to connect to it no matter what you do. Also, both servers need to have their services running off domain user (not local system and not domain admin) accounts before you can talk to each other.



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"

 

[onressy]

Thanks Catadmin

to answer your questions:

[1] different domain
[2]yes
[3]yes
[4]yes
[5] yes

Thanks again!

 

[Catadmin]

Does the other domain trust your domain?

You might have to Remote Desktop into the remote server and open up the client tools that way if you can't get connected via the usual connection methods.

Another idea is to do a Tracert from your command prompt to see if it's even reaching the remote server. Or stick a network sniffer on your box and see what happens to the packets.



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"