June 9, 2011 at 12:02 am
Hi everybody,
I am not able to login sqlserver through Network.that login is windows login ,But i am able to SQL SERVER SA login.
this is the error i am facing
Cannot connect to 19?.??.??.??
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
Regards
venkat
June 9, 2011 at 4:19 am
GAIL i am waiting for your reply
please
Regards
venkat
June 9, 2011 at 4:27 am
is the windows account active? Check the status of windows account in active directory.
----------
Ashish
June 9, 2011 at 4:42 am
yes my login is active.
two servers like source server and destination server are i am not able to login but i am able to login SA login .the version is SQL SERVER 2005 SP4
please find the snapshot in attachment
Regards
venkat
June 9, 2011 at 4:50 am
Assuming there is no change in policy for this account in server, i will like to know:-
were you ever able to access the sql server via the mentioned windows login?
The other possibility I can think of is, you logged into machine with some other windows login and when connecting sql, its being connected by logged in windows user and not by the one which you want. Correct me if I am wrong here.
Try of to open the ssms by run as and mention that windows account.
----------
Ashish
June 9, 2011 at 5:02 am
Thank you for replied Ashish
I have configured logshipping primary server is local and secondary server is different location.i am able to login in sql server 2008 R2 both servers through windows .
same logshipping implemented in sql server 2005 sp4 also.
local account is login and when i am tring to login secondary server.
i am getting the error
Regards
venkat
June 9, 2011 at 5:12 am
i am able to login in sql server 2008 R2 both servers through windows .
Sorry cant understand, your server is sql 2005(as per screenshot) or 2008R2.
same logshipping implemented in sql server 2005 sp4 also.
local account is login and when i am tring to login secondary server.
i am getting the error
1)
If you saying that your primary is on 2008R2 and secondary on 2005 then I dont think your logshipping will work ever as SQL allows only upgrade. You cant restore the higher version backup to lower version of sql.
2)
If you saying you both server are on same version of sql then your database on secondary is on restoration phase(if not configured with standby), and you will not be able to connect if the account have the default database login to the one which is restoring.
----------
Ashish
June 9, 2011 at 5:26 am
no asish,
Sorry cant understand, your server is sql 2005(as per screenshot) or 2008R2.
both servers are sql server 2005 sp4 only.
If you saying you both server are on same version of sql then your database on secondary is on restoration phase(if not configured with standby), and you will not be able to connect if the account have the default database login to the one which is restoring
No ,i configured logshipping succesfully both servers using SA LOGIN..
sorry , i confused to you
Regards
venkat
June 9, 2011 at 5:46 am
No ,i configured logshipping succesfully both servers using SA LOGIN..
did you configured that windows account on secondary server as well?
If not then configure the account on secondary server and you will be able to login.
You might be thinking that its same database then why the login not workin on secondary. But the fact is there are 2 things in sql server, one is user and other is login.
You moved the users and now configure the login for that user on secondary.
----------
Ashish
June 9, 2011 at 5:54 am
both the local servers able to connect windows login only.but when i am trying to connect(windows login only) another sql server(other server).At the same time i am facing error
Cannot connect to 19?.??.??.??
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
hello Guys please provide the solution
Regards
venkat
Regards
venkat
June 13, 2011 at 9:42 am
silly question but did you create the user account using the 2005 add login gui in SQL Server mgmnt studio?? I came across an error in 2008 that may exist in 2005 SP4 where logins added using windows / AD groups using the gui don't work but if you add the login using sql command it works fine.
Try deleting the user in SQL and re adding using...
CREATE LOGIN [<domainName>\<loginName>] FROM WINDOWS;
GO
June 14, 2011 at 6:06 am
What does your SQL Server log show?
Is it showing a "failed login"? "Login failed for user"?
To me it seems as though you're not getting to the database server instance.
June 14, 2011 at 7:15 am
Steve-3_5_7_9 (6/14/2011)
What does your SQL Server log show?Is it showing a "failed login"? "Login failed for user"?
To me it seems as though you're not getting to the database server instance.
Hi guys,
sorry , i am busy with another issue.In sql server error log not showing any thing.please check below the link image
http://www.sqlservercentral.com/Forums/Attachment8979.aspx
Regards
venkat
June 14, 2011 at 7:41 am
To me this is more indicative of network, or AD than failed login since you are not seeing anything in the SQL Log. A failed login would show something like "login failed for "NT/AUTHORITY" or "Login failed for USER..."
You're timing out during the connection which might mean the windows login is not being authenticated to the Active Directory.
To clarify, when you connect via SA are you using the same "screen print", SSMS, that you posted or is this local on the server?
Did you check the SQL Server Logs and not just the ERRORLOG?
Have you tried connecting via IP,port?
June 14, 2011 at 11:05 pm
Steve-3_5_7_9 (6/14/2011)
To me this is more indicative of network, or AD than failed login since you are not seeing anything in the SQL Log. A failed login would show something like "login failed for "NT/AUTHORITY" or "Login failed for USER..."You're timing out during the connection which might mean the windows login is not being authenticated to the Active Directory.
To clarify, when you connect via SA are you using the same "screen print", SSMS, that you posted or is this local on the server?
Did you check the SQL Server Logs and not just the ERRORLOG?
Have you tried connecting via IP,port?
Hi,
Thank you for the reply,
I already checked sql server error log and event viewer also but there nothing.
To clarify, when you connect via SA are you using the same "screen print", SSMS, that you posted or is this local on the server?
both servers are different segments.source server is local and another server is diffrent server.Recently i have implemented logshipping in both servers.In my company given approval for open the firewall ports and files sharing ports also.finallly Configured logshippping successfully using SA login ONLY.but i am not able connect in secondary server(destination server) in local using with windows login.both servers having same windows logins.
Regards
venkat
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply