I tried using the netbios again or fqdn name and got the following error: Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Unable to complete login process due to delay in opening server connection. No, no server alias setup on my local or on the server.įrom my laptop: Used SQLCMD and I was able to login using the netbios name once, ran a few commands and then I disconnected. Yes, all other admins have to connect remotely via SSMS & IP or they RDP into the server first and launch SSMS to connect via name. Sorry for the delay, I dont have access to the server over the weekend 😉 Just curious, what happens when you try and connect using just the NetBIOS name via another utility, like SQLCMD or OSQL? What is the error that is reported back? Is this same result experienced on other computers as well, or just yours? There is not a SQL alias setup on your system, is there? I have never experienced anything like this.
#Dbschema sql server connection server name instance name how to
How to Post Performance Problems - by Gail Shaw. 
Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden. Forum Etiquette: How to post Reporting Services problems. Is there anything else I can test on my end to be sure its not my issue? Ping servername - Server replys - No timeout Ping -a IP - Server replys and returns name - No timeout Open UNC to local directories on SQL server from my laptop - works fine Remote desktop to the server - Works fine Registered Server with DNS to see if it helped - No changeĪdded server name and IP to local host file and I can connect via name (TCP/IP really) NSLOOKUP - Reports correct server name and IP UDP Port 1434 - Open and Listening (verified using PortQry.exe) I am trying to test everything on my side before opening a trouble ticket. If I remote desktop into the server and then use SSMS, I can connect by Name and IP.Ī side note, I do not have access to the DNS server, nor can we adjust any settings, its controlled by the domain owner. (as it does on all our other servers) This issue occurs to all other admins, not just me. It's the default instance (mssqlserver), so connecting via server name should work. I can connect to my SQl server using SSMS by IP and not by server name. Ok, here is the issue and my steps to troubleshoot:
0 kommentar(er)
