|
Home > Archive > microsoft.public.sqlserver.server > October 2002 > Linked Servers - SQLServer to SQLServer - not working
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Linked Servers - SQLServer to SQLServer - not working
|
|
| Liam Caffrey 2002-10-05, 9:12 pm |
| I have difficulty successfully executing a distributed query via a
linked server.
This is a transcript of what I am doing. (I have modified the
parameter values for the purpose of this newsgroup posting)
exec sp_addlinkedserver @server='192.28.111.198\BLADE'
,@srvproduct='SQL Server'
where BLADE is the SQLServer instance name (Version 8) and
192.28.111.198 is the IP address of the machine that the SQLServer
instance is running on.
I get this output...
(1 row(s) affected)
(1 row(s) affected)
Then I...
exec sp_addlinkedsrvlogin @rmtsrvname='192.28.111.198\BLADE'
,@useself='false'
,@rmtuser='tiber1'
,@rmtpassword='tiber1'
getting...
(0 row(s) affected)
(1 row(s) affected)
(0 row(s) affected)
(1 row(s) affected)
When I run a query against this linked server as follows...
select count(1)
from [192.28.111.198\BLADE].Minerals1_commerce.dbo.OrderGroup
I get....
Server: Msg 17, Level 16, State 1, Line 1
SQL Server does not exist or access denied.
I have done a lot of RTFMing and scouring the Net for info on this but
the problem persists. I have tried the extended version of the
addlinkedserver with all the parameters specified both using OLEDB for
SQL Server and ODBC. Same crap.
Both instances are on the same version of SQLServer. They run on their
own seperate domains, each protected by their own firewalls. The 1433
is bi-directionally open on both instances. I have no problem
profiling myself against any remote server using EM or QA. The Tools |
Data Transformation Services | Import/Export features work perfectly
between the instances.
What the hell is going on here? Is there some NT authentication domain
issues going on here. I would really appreciate some feedback on this
as I have spent a lot of time getting nowwhere so far.
Regards
Liam Caffrey
eosys@eircom.net
PS. There is 1 other variant that I have also tried. I got this from a
newsgroup posting but it made no difference.
In HOSTS file I have the entry
192.28.111.198 MyRemoteServer
exec sp_addlinkedserver @server='MyRemoteServer.BLADE0\BLADE'
where BLADE0 is the domain name.
??
| |
| Umachandar Jayachandran 2002-10-05, 9:13 pm |
| >> The 1433 is bi-directionally open on both instances.
UDP 1434 is used to discover ports on which the named instance is
listening on since this could be dynamically assigned at the time of the
service start. So if you don't have UDP 1434 open, then use the connection
string to explicitly specify the port also for the named instance by doing
"Address=192.28.111.198,3714". There are other ways to specify the
connection string attributes.
--
Umachandar Jayachandran
SQL Resources at http://www.umachandar.com/resources.htm
( Please reply only to newsgroup. )
|
|
|
|
|