March 27, 2014 at 3:59 pm
Hi Folks,
Problem - Unable to connect to SQL Server 2008 using Windows Authentication from Windows XP Client Systems. The SQL Server is configured in a NEC Cluster. The problem occurs only when I connect to the Virtual cluster Database Name/IP Address. But I am able to connect using hostname(SQL_Primary)/IP Address(192.168.10.101) using windows Authentication.
Observation - The virtual hostname is registered in DNS and it is resolving without any problem. But, when I was trying various options, I figured out by adding the following entry to 'c:\windows\system32\drivers\etc\hosts' file in my Windows XP client, it works fine.
192.168.10.203 "SQL_Virtual" SQL_Virtual.ABC.COM
"SQL_Virtual" is my Virtual Failover Database name and it is not the default database instance name.
Questions:
1. I couldn't figure out why it is working with the above entry in my host file?
2. How to add this in DNS server?
Thanks guys,
Lisa
March 27, 2014 at 5:53 pm
What error do you get when you try to connect to the Virtual Instance ? And do you use static port for the SQL instance or dynamic ports ?
--
SQLBuddy
March 28, 2014 at 6:34 am
lisafox.it (3/27/2014)
Observation - The virtual hostname is registered in DNS and it is resolving without any problem.
What command are you using to test the name resolution?
lisafox.it (3/27/2014)
But, when I was trying various options, I figured out by adding the following entry to 'c:\windows\system32\drivers\etc\hosts' file in my Windows XP client, it works fine.
implies that name resolution is possibly not ok
lisafox.it (3/27/2014)
You will need to consult your system admin to check\complete this for you.
One thing to check on the client is the DNS search suffix list on the NIC advanced properties, ensure that any domains you need to search are listed here
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 28, 2014 at 12:15 pm
What error do you get when you try to connect to the Virtual Instance ?
"Cannot connect to SQL_VIRTUAL
Additional Information
Cannot generate SSPI context (Microsoft SQL Server)"
And do you use static port for the SQL instance or dynamic ports ?
Port 1433
Lisa
March 28, 2014 at 12:32 pm
What command are you using to test the name resolution?
C:\> Nslookup SQL_Virtual
Resolves both forward lookup and reverse lookup
C:\> NSlookup SQL_Virtual.ABC.COM
Resolves both forward lookup and reverse lookup
implies that name resolution is possibly not ok[/b]
I dont disagree. But, I am wondering why only for Windows Authentication in SQL Enterprise Manager and also in ODBC DSN configuration? The name resolution seems to be working fine while using SQL Authentication .
One thing to check on the client is the DNS search suffix list on the NIC advanced properties, ensure that any domains you need to search are listed here
I tried adding abc.com, but it did not help.
March 28, 2014 at 2:09 pm
lisafox.it (3/28/2014)
What error do you get when you try to connect to the Virtual Instance ?"Cannot connect to SQL_VIRTUAL
Additional Information
Cannot generate SSPI context (Microsoft SQL Server)"
And do you use static port for the SQL instance or dynamic ports ?
Port 1433
Lisa
Could you check the SQL Server Errors logs for a more detailed error message ? Usually if you check this message or a bunch of messages before this login failure you can get some clue.
Also check the Windows system\application log for any messages when this error occurs.
BTW, Is this a new cluster installation or it has been working for some time and started getting this issue recently ?
--
SQLBuddy
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply