October 26, 2012 at 12:42 pm
Ok, here is the issue and my steps to troubleshoot:
I can connect to my SQl server using SSMS by IP and not by server name.
It's the default instance (mssqlserver), so connecting via server name should work. (as it does on all our other servers) This issue occurs to all other admins, not just me.
If I remote desktop into the server and then use SSMS, I can connect by Name and IP.
A side note, I do not have access to the DNS server, nor can we adjust any settings, its controlled by the domain owner. I am trying to test everything on my side before opening a trouble ticket.
SQL Server 2008R2
SQL Server Browser Service - Started
Shared Memory - Enabled
Named Pipes - Enabled
TCP/IP - Enabled
VIA - Disabled
UDP Port 1434 - Open and Listening (verified using PortQry.exe)
NSLOOKUP - Reports correct server name and IP
Registered Server with DNS to see if it helped - No change
Flushed my DNS cache - No change
Added server name and IP to local host file and I can connect via name (TCP/IP really)
Remote desktop to the server - Works fine
Open UNC to local directories on SQL server from my laptop - works fine
Ping IP - Server replys - No timeout
Ping -a IP - Server replys and returns name - No timeout
Ping servername - Server replys - No timeout
Is there anything else I can test on my end to be sure its not my issue?
Thanks in advance!
October 26, 2012 at 12:57 pm
not sure if this helps yet, but i think the issue is a WINS issue when you cannot resolve by name;
For example if you enter SERVER04 instead of a FQDN like SERVER04.mydomain.com, that's a WINS issue, and not a DNS issue, i think.
[this Ms article explains a lot and goes deep into troubleshooting:
http://technet.microsoft.com/en-us/library/cc959203.aspx
I know when i first started playing with VirtualBox, all my virtual servers had the same name, which caused name conflicts, but not IP conflicts.
Lowell
October 26, 2012 at 1:31 pm
not sure if this helps yet, but i think the issue is a WINS issue when you cannot resolve by name;
For example if you enter SERVER04 instead of a FQDN like SERVER04.mydomain.com, that's a WINS issue, and not a DNS issue, i think.
Not necessarily. It depends on what type of node type the server is in. For example if the node type is hybrid it will try to resolve via DNS first regardless whether or not a FQDN or NetBIOS name was specified.
It still could be a WINS vs DNS issue though. What happens when you try and ping the server via the name (both NetBIOS and FQDN)? What response do you get back?
Joie Andrew
"Since 1982"
October 26, 2012 at 1:31 pm
Was the server name changed after SQL Server was installed? If so you'll have to do sp_dropserver/sp_addserver to get the new machine name to take effect inside SQL Server.
October 26, 2012 at 2:44 pm
Joie Andrew (10/26/2012)
not sure if this helps yet, but i think the issue is a WINS issue when you cannot resolve by name;
For example if you enter SERVER04 instead of a FQDN like SERVER04.mydomain.com, that's a WINS issue, and not a DNS issue, i think.
Not necessarily. It depends on what type of node type the server is in. For example if the node type is hybrid it will try to resolve via DNS first regardless whether or not a FQDN or NetBIOS name was specified.
It still could be a WINS vs DNS issue though. What happens when you try and ping the server via the name (both NetBIOS and FQDN)? What response do you get back?
Ping using netbios or fqdn retuns a reply, no issue there.
Intersting development I tryed to connect from SSMS using the FQDN and it does connect! (I thougt I tried that previously, guess I didnt) Any idea what that means? Seems like a name resolution (wins or dns) issue to me.
October 26, 2012 at 2:45 pm
Scott D. Jacobson (10/26/2012)
Was the server name changed after SQL Server was installed? If so you'll have to do sp_dropserver/sp_addserver to get the new machine name to take effect inside SQL Server.
select @@Servername as 'Server Name' returned the correct name.
October 26, 2012 at 3:32 pm
Intersting development I tryed to connect from SSMS using the FQDN and it does connect! (I thougt I tried that previously, guess I didnt) Any idea what that means? Seems like a name resolution (wins or dns) issue to me.
That does sound like a WINS or lmhosts issue. Does the ping using the NetBIOS name return back the same IP address as the ping to the FQDN?
If you open a command prompt and run ipconfig -all what node type does it say you have?
Joie Andrew
"Since 1982"
October 26, 2012 at 4:05 pm
Joie Andrew (10/26/2012)
Intersting development I tryed to connect from SSMS using the FQDN and it does connect! (I thougt I tried that previously, guess I didnt) Any idea what that means? Seems like a name resolution (wins or dns) issue to me.
That does sound like a WINS or lmhosts issue. Does the ping using the NetBIOS name return back the same IP address as the ping to the FQDN?
If you open a command prompt and run ipconfig -all what node type does it say you have?
Ping to netbios or fqdn returns the same hostname and IP.
Ipconfig /all shows its a hybrid node.
October 26, 2012 at 4:13 pm
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?
Joie Andrew
"Since 1982"
October 28, 2012 at 2:53 am
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?
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);October 29, 2012 at 11:11 am
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.
October 29, 2012 at 11:18 am
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.
October 29, 2012 at 11:31 am
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"
October 29, 2012 at 2:45 pm
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);October 30, 2012 at 11:39 am
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 19 total)
You must be logged in to reply to this topic. Login to reply