September 11, 2012 at 6:23 am
Hello.
I have a SQL 2000 database used by a scheduling application on (we'll call it), Computer A . I also have a SQL 2008 db server (we'll call it) Server B. Computer A & Server B are in separate cities.
I need to create a job on server B that queries the data on Computer A every hour and sends a report. I've tried everything from opening ports 1433, enabling remote connections, enabling TCP/IP and I still can't connect. Can anyone get me some feedback?
Let's start with what should I be typing in the SERVER NAME field when I open up SSMS on Server B? I figure, if I can at least successfully establish a connection, I should be ok. I've tried typing the IP Address / instance name with no success.
Thanks
September 11, 2012 at 6:58 am
Is your instance on Computer A your default instance or is it a named instance?
Do you have a DNS that will solve Computer A name for your Server B?
Do you use the same network or your Computer A is in a different network than your Server B?
If different network, can you connect to your Computer A from Computer A using external IP?
Commonly you would use something like this:
ServerName\InstanceName
ServerName,9999 (ServerName,PortNumber)
192.168.0.5\InstanceName (IPAddress\InstanceName)
192.168.0.5\9999 (IPAddress\PortNumber)
http://www.ServerName.com\InstanceName(URL,InstanceName)
http://www.ServerName.com,9999 (URL,PortNumber)
September 11, 2012 at 8:07 am
Did you create a Linked Server object for which to pass through credentials?
Are the credentials you are using for one server valid on another, or can those credentials at least impersonate the credentials on the other server?
Did you try tracert or ping from Server A to Server B?
September 11, 2012 at 9:02 am
On Computer A, the users can connect by using, "(local)\ABCPOS"
I have the IP Address of COmputer A, and I've tried, "x.x.x.x\ABCPOS" and still not able to connect.
I have no idea what the credential are, but I know that when on Computer A, I can connect using Windows Authentication.
Any other Help Ideas would be much appreciated.
thanks.
September 11, 2012 at 10:02 am
BTW, Computer A uses a default instance (local)
Any help please?
September 11, 2012 at 10:29 am
Actually, you failed to answer the most important question: Are they on the same network?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
September 11, 2012 at 10:42 am
They are not on the same network.
September 11, 2012 at 11:52 am
mike 61998 (9/11/2012)
They are not on the same network.
This sounds like it's a Trust issue. Talk to your network / Active Directory admin and see if they can set up a trusted connection between the domains. That might be the main issue.
September 11, 2012 at 12:02 pm
One is a workstation connected to the internet using Comcast (not on a windows domain), and the other is a workstation on a bellsouth connection (not on windows domain either)
September 11, 2012 at 12:11 pm
Maybe you could look at your cable modem for the network with the 2000 server and see if it needs to forward ports. One hint would be if the 2000 computer has an ip address starting with numbers 192.168. ie., 192.168.x.x
September 11, 2012 at 1:15 pm
mike 61998 (9/11/2012)
One is a workstation connected to the internet using Comcast (not on a windows domain), and the other is a workstation on a bellsouth connection (not on windows domain either)
Ah, that's a horse of a different color.
You're going to need some sort of SSH tunnel or VPN or something to hook these two workstations together.
September 11, 2012 at 1:42 pm
mike 61998 (9/11/2012)
They are not on the same network.
Ah. There's your problem.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
September 11, 2012 at 2:08 pm
I don't get it. both PC's have Static IP Addresses and both have SQL Remote connection settings enabled?
September 11, 2012 at 2:50 pm
mike 61998 (9/11/2012)
I don't get it. both PC's have Static IP Addresses and both have SQL Remote connection settings enabled?
As the other replies indicated, this is about security, not addressing (and not really about SQL specifically either), and there are lot of possible security gates between A and B that could be stopping you (and it's likely not just one thing either).
The first thing to do is to establish whether you can make *ANY* connection between the two boxes. So, can you ping workstation B from workstation A? Can you make any other kind of connection from A to B?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
September 11, 2012 at 2:57 pm
What's the error message you get? Server does not exist or cannot log in? Are you using windows authentication (probably won't work if the workstations aren't authenticating to a domain with a trusted relationship to the server) or SQL authentication?
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply