InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 03:46:06 GMT20http://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxMike,What OS are your workstations using?Are these stand-alone workstations? Meaning are they the only workstations in their individual environments? Or when you say there is no windows domain, do you mean that there are no servers in these individual environments, just PCs?Wed, 12 Sep 2012 04:20:28 GMTBrandie Tarvinhttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspx[quote][b]David Webb-200187 (9/11/2012)[/b][hr]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?[/quote]Honestly, I don't even see SQL authentication working unless he can build a dedicated connection between the workstations.And notice that he did say workstations, not servers. So with two workstations not in the same building, and connecting to the internet on 2 different ISPs, we've potentially got a lot more problems here than just the basic security one.Wed, 12 Sep 2012 04:18:45 GMTBrandie Tarvinhttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxWhat'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?Tue, 11 Sep 2012 14:57:45 GMTDavid Webb-CDShttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspx[quote][b]mike 61998 (9/11/2012)[/b][hr]I don't get it. both PC's have Static IP Addresses and both have SQL Remote connection settings enabled?[/quote]As the other replies indicated, this is about security, not addressing (and not really about SQL specifically either), and there are [i]lot[/i] 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?Tue, 11 Sep 2012 14:50:54 GMTRBarryYounghttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxI don't get it. both PC's have Static IP Addresses and both have SQL Remote connection settings enabled?Tue, 11 Sep 2012 14:08:58 GMTmike 61998http://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspx[quote][b]mike 61998 (9/11/2012)[/b][hr]They are not on the same network.[/quote]Ah. [i]There's[/i] your problem.Tue, 11 Sep 2012 13:42:30 GMTRBarryYounghttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspx[quote][b]mike 61998 (9/11/2012)[/b][hr]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)[/quote]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.Tue, 11 Sep 2012 13:15:15 GMTBrandie Tarvinhttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxMaybe 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.xTue, 11 Sep 2012 12:11:07 GMTpatrickmcginnis59http://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxOne 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)Tue, 11 Sep 2012 12:02:35 GMTmike 61998http://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspx[quote][b]mike 61998 (9/11/2012)[/b][hr]They are not on the same network.[/quote]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.Tue, 11 Sep 2012 11:52:32 GMTBrandie Tarvinhttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxThey are not on the same network.Tue, 11 Sep 2012 10:42:45 GMTmike 61998http://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxActually, you failed to answer the most important question: Are they on the same network?Tue, 11 Sep 2012 10:29:21 GMTRBarryYounghttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxBTW, Computer A uses a default instance (local)Any help please?Tue, 11 Sep 2012 10:02:28 GMTmike 61998http://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxOn 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.Tue, 11 Sep 2012 09:02:20 GMTmike 61998http://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxDid 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?Tue, 11 Sep 2012 08:07:11 GMTBrandie Tarvinhttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxIs 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\InstanceNameServerName,9999 (ServerName,PortNumber)192.168.0.5\InstanceName (IPAddress\InstanceName)192.168.0.5\9999 (IPAddress\PortNumber)www.ServerName.com\InstanceName(URL,InstanceName)www.ServerName.com,9999 (URL,PortNumber)Tue, 11 Sep 2012 06:58:53 GMTLuis Cazareshttp://www.sqlservercentral.com/Forums/Topic1357354-391-1.aspxHello.I have a SQL 2000 database used by a scheduling application on (we'll call it), [b]Computer A[/b] . I also have a SQL 2008 db server (we'll call it) [b]Server B[/b]. [b]Computer A[/b] & [b]Server B[/b] are in separate cities.I need to create a job on [b]server B[/b] that queries the data on [b]Computer A[/b] 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 [b]Server B[/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.ThanksTue, 11 Sep 2012 06:23:50 GMTmike 61998