Error 18483 Could Not Connect To Server

additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.

log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL+Server&ProdVer=2000.80.760.0&EvtID=18483&EvtSrc=MSSQLServer are voted up and rise to the top SQL Server Error 18483 - When Setting Up SQL Distribution up vote 2 down vote favorite I'm trying to synchronize a couple tables in one SQL Server 2000 database into another SQL Server 2005 database using replication. When I am attempting to set up my SQL Server as a distributor, I'm getting the following error: SQL Server Enterprise Manager could not configure 'VIPER' as the Distributor http://dba.stackexchange.com/questions/6845/sql-server-error-18483-when-setting-up-sql-distribution for 'VIPER' . Error 18483: Could not connect to server 'VIPER' because 'distributor_admin' is not defined as a remote login at the server. In doing research, I found several sources and articles that show that my machine name, and the actual name of the server are not the same. When I check the sysservers view in master, I see that: 0 1089 VMSSERV SQL Server SQLOLEDB VMSSERV 4/23/2008 9:50:41 AM 1 1601 repl_distributor SQL Server SQLOLEDB VIPER 10/12/2011 1:23:18 PM 2 1184 CHARLIE SQL Server SQLOLEDB CHARLIE 2/18/2011 1:32:14 PM The first line is the original database that was setup, and that I intend on using. You can see (kinda) that the original name is VMSSERV and the actual machine name is VIPER. So, from the results of my extensive web search, I ran this in Query Analyzer: USE MASTER GO SELECT @@SERVERNAME, SERVERPROPERTY('ServerName') This returns: VMSSERV VIPER Most of my web searches show that I should refer to http://support.microsoft.com/kb/818334, which instructs to use: -- Use the Master database USE master GO -- Declare local variables DECLARE @serverproperty_servername varchar(100), @servername varchar(100) -- Get the value returned by the SERVERPROPERTY system function SELECT @serverproperty_servername = CONVERT(varchar(100), SERVERPROPERTY('ServerName')) -- Get the value returned by @@SERVERNAME global variable SELECT @servername = CONVERT(varchar(100), @@SERVERNAME) -- Drop the server with incorrect name EXEC sp_drop

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/2953383/help-with-linked-server-error more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users https://www.experts-exchange.com/questions/21585274/SQL-server-Replication-distributor-admin.html Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Help with Linked Server Error up vote 0 down vote favorite In SSMS 2008, I am trying to execute a stored procedure in a database on another error 18483 server. The call looks something like the following: EXEC [RemoteServer].Database.Schema.StoredProcedureName @param1, @param2 The linked server is set up correctly, and has both RPC and RPC OUT set to true. Security on the linked server is set to Be made using the login's current security context. When I attempt to execute the stored procedure, I get the following error: Msg 18483, Level 14, State 1, Line 1 Could not connect to server 'RemoteServer' because '' is not error 18483 could defined as a remote login at the server. Verify that you have specified the correct login name. I am connected to the local server using Windows Authentication. Anyone know why I would be getting this error? sql-server share|improve this question asked Jun 1 '10 at 21:13 Randy Minder 24.8k21107206 Just a guess but maybe a kerberos double hop issue? blogs.msdn.com/b/sql_protocols/archive/2006/08/10/694657.asp‌x –Martin Smith Jun 1 '10 at 21:17 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted 'Be made using the login's current security context' translates as impersonation (aka. as 'self-mapping' in SQL Server linked in terms). Access a remote server under an impersonated context means delegation. So you need to set up the constraint delegation, see Configuring Linked Servers for Delegation: Requirements for the Client The Windows user must have access permissions to SQLSERVER1 and SQLSERVER2. The user AD property Account is sensitive and cannot be delegated must not be selected. The client computer must be using TCP/IP or named pipes network connectivity. Requirements for the First/Middle Server (SQLSERVER1) The server must have an SPN registered by the domain administrator. The account under which SQL Server is running must be trusted for delegation. The server must be using TCP/IP or named pipes network connectivity. The linked server logins must be configured for self mapping. Requirements for the Second Server (SQL

for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > SQL server Replication - distributor_admin Want to Advertise Here? Solved SQL server Replication - distributor_admin Posted on 2005-10-05 MS SQL Server 1 Verified Solution 5 Comments 3,924 Views Last Modified: 2008-05-28 Hi I am trying to setup replication in SQL server 2000. 1. selected distributor 2. Configure the sql server agent service to start automatically 3. specified snapshot folder on a shared drive 4. Customized the distribution database 5. Gave database name and folder path for the db and log 6. Enabled server to use the distributor 7. Enable publication database 8. Did not select subscribers When the wizard is completed and the setup runs, it breaks at 'Configuring Distributor' i get the following issue. SQL Server Enterprice Manager could not configure [server name] as the Distributor for 'server name' Error 18483: Could not connect to server 'xxxxxxxx' because 'distributor_admin' is not defined as a remote login at the server. Help is appreciated. 0 Question by:sansoftura Facebook Twitter LinkedIn Google Best Solution bymaxomedia You need to run sp_dropserver first, then go for sp_addserver. No worries, it does not delete your database. Do you have Publication and Distribution on the same server ? If you do, and you have Go to Solution 4 Comments Message Expert Comment by:maxomedia2005-10-07 Hello Check to make sure SELECT @@SERVERNAME returns correct servername. If not then you will need to run sp_dropserver and sp_addserver , local. Quite a helpful article on this topic is that one http://support.microsoft.com/default.aspx?scid=kb;en-us;321822 Cheers, Toby 0 LVL 6 Overall: Level 6 MS SQL Server 1 Message Author Comment by:sansoftura2005-10-10 I went through the article and chenge the alias name for the SQL server. That did not fix the problem. Also i trided creating a 'distributor_admin' and gave full access to the DB. It still fails I get the error SQL Server Enterprise Manager could not configure [server name] as the Distributor for '[server name] ' Error 18483: Could not connect to server '[server name] ' because 'distributor_admin' is not defined as a remote login at the server. Does it matter if i try