July 19, 2011 at 6:04 am
Driving me nuts here..
Installed 2008 r2 then upgraded to SP1.
Remote connections are enabled
SQL Browser is on
Firewall is off
I can ping the server.
Soon as i try a SQL connect via SSMS i get the normal error of:
An error occurred while establishing a connection to server. When connectiing to SQL Server
--
Secondly and possibly related.
Ive downloaded all the 64bit installs for sp1. I ran the "SQLServer2008R2SP1-KB2528583-x64-ENU" and joy. upgrade works. But what is the "SQLManagementStudio_x64_ENU" for? When i try and run it. It comes up like the normal install of SQL Server 2008. So im not sure if i should be Upgrading or adding features to an existing install.
Thanks for any advice
S
July 19, 2011 at 10:15 am
you have tryed both windows and SQL server Authentication ?
July 19, 2011 at 5:48 pm
Hi,
I've been scratching my head on something similar. I couldn't connect to the database from the server on which it was running (test DSN). I tried every combination of creating the database user first, then the login/ vice versa, changed permissions etc all to no avail. i then tried connecting using Windows Authentication and it worked. After a bit more head-scratching, I found out that there is an Authentication Mode setting on the install set by default to Windows Authentication only which you need to change to Windows & SQL Server Authentication. You need to restart teh SQL Server service after this. Also, for remote connections, enable TCP/IP connections.
Hope this helps.
July 20, 2011 at 5:29 am
hi guys thanks for the replies.
so i thought of a few more things that it might be and have still had no joy connecting to it.
1: The new server is on the same domain as the machine that im connecting from.
2: SQL Browser is on
3: TCIP named pipes etc are all on.
4: It is in Mixed mode, And i cant connect via a SQL Account or a Windows domain Account.
5: Tried a restart just to try it.. (Im in IT)
Ive never seen this issue before and been creating quite a few SQL boxs recently. Is it to do with the upgrade to SP 1?
Again for SP1 all i have done is run the SQLServer2008R2SP1-KB2528583-x64-ENU. and dont know what the other one is for.
If anyone can even answer that one it would be good!
Thanks for the help
S
July 20, 2011 at 6:05 am
I had faced something like same 3-4 years back. That day network guy came and did some changes in IP configuration. Most probably DNS Server. Sorry, Do not know actually. But you can check that also.
_____________________________________________
One ounce of practice is more important than tonnes of dreams
July 20, 2011 at 6:14 am
C.K
you got me excited there! Ive managed to put them in the wrong way before and thought that be it! sadly they are in correct 🙁
Still not solved.
Thanks for the idea though
S
July 20, 2011 at 8:32 am
ive tried ip address and ip:1433 (its a default instance, no other instances installed on that machine)
and no joy on either..
July 20, 2011 at 9:08 am
Sorry yes.. I did it that way! getting late in day mind is go a stray. No joy
thanks
Stephen
July 26, 2011 at 3:31 am
Still got this problem
tried the random idea of it being SP1 that caused the problem so removed SP1, but still cant connect.
Suammry:
2008 r2 Dev edt
remote connections allowed
sql browser enabled
Windows firewall is disabled
checked TCP settings. They are correct
I can ping both DNS name and IP
I can remote from the problem machine to any other SQL Server via SSMS
I cant connect with DNS name
I cant connect with IP and port
If i try to connect with SQLCMD i get:
A network-related or in stance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For information see SQL Server Books Online..
SQLCMD: Error: Microsoft SQL Server Native client 10.0 : Login timeout expired.
When i attempt to remote SSMS on. On the problem machine i can see a successful login for the machine im remoting from!?
Any ideas?
thanks
s
July 26, 2011 at 5:13 am
stebennettsjb (7/26/2011)
Still got this problemtried the random idea of it being SP1 that caused the problem so removed SP1, but still cant connect.
Suammry:
2008 r2 Dev edt
remote connections allowed
sql browser enabled
Windows firewall is disabled
checked TCP settings. They are correct
I can ping both DNS name and IP
I can remote from the problem machine to any other SQL Server via SSMS
I cant connect with DNS name
I cant connect with IP and port
If i try to connect with SQLCMD i get:
A network-related or in stance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For information see SQL Server Books Online..
SQLCMD: Error: Microsoft SQL Server Native client 10.0 : Login timeout expired.
When i attempt to remote SSMS on. On the problem machine i can see a successful login for the machine im remoting from!?
Any ideas?
thanks
s
Can you connect using SQLCMD on the Server? (sqlcmd -Syourservername -E) or (sqlcmd -Syourservername -Usqlaccount)
July 26, 2011 at 5:28 am
Sigh...
resolved the problem...
I had apparently checked if tcp and pipes were enabled in 32bit but not 64bit. Once i enabled them and restarted the SQL Service its working...
Very stupid of me..
thanks for all the replies..
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply