Joie Andrew (10/26/2012)
Interesting. I have never experienced anything like this. 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?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?
Sorry for the delay, I dont have access to the server over the weekend
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.
No, no server alias setup on my local or on the server.
From my laptop: Used SQLCMD and I was able to login using the netbios name once, ran a few commands and then I disconnected. 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.
Just used the IP address and connected from my laptop to the server via SQLCMD and it connects fine.
mister.magoo (10/28/2012)
is your client machine a member the same domain as the server?can you connect using the name if you specifiy tcp/ip in the advanced connection settings?
are you logged in to your client using the same credentials you tested with on the server RDP login?
Yes, I am on the same domain as the server.
Using SSMS and specified tcp/ip in advanced:
Netbios Name: Connection Times out.
FQDN: Connection Times out. (I was able to connect using SSMS and the FQDN last week, now its not working) < I have not made any changes to any settings on my system or the server.
Yes, my same domain account was used for all connections to the remote server thru RDP and SSMS.
A few more questions:
- How many IP addresses is SQL configured to listen on?
- Are there multiple NICs on the server?
- Is NIC teaming used on the server?
Joie Andrew
"Since 1982"
And more questions....
Have you checked the port the instance is listening on ?
- even though it is the default instance, it could be on a port other than 1433.
Have you tried connecting to it using the name and port ? e.g. MYSERVER,1433
How does nslookup respond? nslookup MYSERVER
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
Joie Andrew (10/29/2012)
A few more questions:- How many IP addresses is SQL configured to listen on?
- Are there multiple NICs on the server?
- Is NIC teaming used on the server?
There is one IP address used for listening.
There are multiple NICs (3 of them assigned to this server), this is a virtual server configuration. NICs are assigned/shared with the virtual machines, one is for remote connections and the other two are used for connections to a storage array (non routable IPs to clients)
I do not know if NIC teaming is used or not.
As a side note, the other 2 virtual machines on this server have no communication issues. They are sharepoint front and backend servers and users access them via Netbois names all day long without fail.
Viewing 15 posts - 1 through 15 (of 20 total)
You must be logged in to reply to this topic. Login to reply