64bit server not accepting logins
-
I have a SQL2005 64 bit sql server on windows 2003 64 bit server. I can login to the server as local admin and run management studio and do all that needs doing. My network account is a local administrator on the server and I should be able to connect remotely via management studio and do all the things I need to do. I can't connect using my windows account, or the sa account. The box is configured to allow remote connections using tcpip. The engine runs under the local system account and I dont see why I am getting any problems.
All 32bit sql servers are set-up in a similar fashion and I have no problems.
At the moment I am wondering if it is the security settings for Windows 2003 64bit server rather than a SQL problem. Any ideas out there?
-
What is the Authentication Method (SQL or BOTH(SQL/NT)
Also Enable both Named Pipes and TCPIP on the Server.
When you open SQL Server Management Studio.
It Open a Dialogbox to "connect to Server" Specify the Servername then
goto OPTIONS>> Click on Network Protocols then Select Shared Memory from the Drop Down, then try to connect.... See if you are able to connect this way...
Good Practise will be to get SQLServer Service running under a domain account.
Maninder
www.dbanation.com -
There's no difference between the 2 platforms so you shouldn't be having this issue as a result of being on 64bit.
And if you're positive that you've got it setup for remote connections then I'd say make sure you can ping that box from your workstation and try to connect to sql with the exact name you used to ping. Try it by IP, DNS and netbios. If you still can't connect, then look at the firewall both on your workstation and the network. Maybe you've got something along the way blocking 1433.
Failing that, post the exact message and we'll take it from there.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
-
OK it went like this
last week the chief of infrastructure asked all members of my team (sql development and DBA's) to stop and disable the ComputerBrowser service on their pc's and servers because the wrong servers were being promoted to master and backup browser roles. (having worked in network as well as SQL support and devlopment I thought he was barking up the wrong tree but hey its his domain) So we complied with the request, it didnt seem to be affecting anything. All live servers are 32 bit and I had no problem with any of them. 64 bit server is a new beast and in the process of being brought online with new services, so I had no reason to do anything to until today. I spent most of the day trying to trawl the error logs for some kind of reason for the problem until......
I wouldn't have made the connection but I was unable to browse to another server on the network so as an experiment I turned Browser service back on and would'nt you know it no connection problems.
Problem seems to have gone away but I am non the wiser to the underlying cause.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply