Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 Other Forums
 MS Access
 cannot connect to the server check the server nam

Author  Topic 

RC
Starting Member

8 Posts

Posted - 2005-01-17 : 10:27:11
I have SQL Server 2000 evaluation version on DesktopA and the same SQL Server running on DesktopB. I would like to use the SQL Server Enterprise Manager wizard to copy the database from DesktopA to DesktopB. SQL Server is running on both PCs as a local system account. When I start the wizard, it says (local) for the source server and "use windows authentication, the next step asks for the destaination server and lists (local) and DESKTOPB, when I pick DESKTOPB and either Windows and SQL authentication I get the error message, "Cannot connect to the server DESKTOPB. Please check the server name and try again." I am new to this so any ideas of what I should try would be appreciated. I don't know if I need to "register" the servers or anything else I might be leaving out.

Stoad
Freaky Yak Linguist

1983 Posts

Posted - 2005-01-17 : 14:14:18
>I don't know if I need to "register" the servers...

aha. try to register sqlserverB in EM on desktopA (

sqlserverA is already registered there )
Go to Top of Page

RC
Starting Member

8 Posts

Posted - 2005-01-17 : 14:43:06
I ran the SQL Server Enterprise Manager Register wizard on DesktopA and sucessfully registered DESKTOPB, but I still got the same login error message. I went back to check the register wizard again and DESKTOPB was no longer in the list of available servers listed on the left side.
Go to Top of Page

Stoad
Freaky Yak Linguist

1983 Posts

Posted - 2005-01-18 : 02:50:56
RC,
on desktopB: Start -> Programs -> SQL Server Group -> Server Network Utility;
add TCP/IP protocol (with default settings for it (port 1433, etc));
also, it's worth reading about the Utility in Books Online.
Also, on both desktops, run Client Network Utility and in its dropdown choose TCP/IP.

Go to Top of Page

RC
Starting Member

8 Posts

Posted - 2005-01-18 : 08:25:03
Thanks, I tried that and then stopped and restarted both servers and nothing changed.
Go to Top of Page

Stoad
Freaky Yak Linguist

1983 Posts

Posted - 2005-01-18 : 09:10:53
try to choose on both your sqlservers "pure" SQL Server Authentication mode and use only it
Go to Top of Page
   

- Advertisement -