February 10, 2008 at 3:27 pm
I've searched these forums and the web for the solution to this, and for 3 consecutive days it has eluded me. I'm at my wits end, so I apologize in advance if I sound short. I'm really tired of dealing with this and about to switch to another database platform, permanently because of it.
My problem is connecting to SQL Server 2005 remotely, via TCP/IP. I get the following:
Server Name:
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
I thought the problem was my firewall. I was running Kaspersky Internet Security 7 but have completely disabled it. No dice, I still can't get connected. I re-enabled Windows firewall when I disabled and shut down Kaspersky, tried it again, same problem. I shut down all firewalls, all anti virus software. Again, no joy. I'm using SSMS EE.
I've been connected, twice in the last 2 days for a very brief period but then lost the connection due to shutting down my computer and restarting. I can't tell what I've done differently to get connected and as far as I can tell, I've done nothing. Same user name, same password, same address.
Do SQL Server accounts lock out similar to windows accounts? My understanding is that they do not but I may be mistaken.
Any help you can give would be much appreciated. I've been working on this one ignorant problem all weekend and it's a complete waste.
February 10, 2008 at 9:24 pm
February 19, 2008 at 5:07 pm
Hi,
I am also getting the same problem, "state 1", and searched for a solution. That link posted has very little information regarding state 1, and what people did to resolve it if it was resolved.
The thing is, I have the server setup properly and my collegue can connect to it fine.... but for some reason I cant...
Did you find out the problem Programming?
February 19, 2008 at 5:41 pm
No, I didn't find out the exact cause of the problem. As you found, that link didn't provide the answers that are needed. I had seen the link already as I had researched the problem fairly extensively before deciding to post here.
However, regardless of the exact cause of the problem, I was able to work around it by using the ip address of the server rather than the server name. I don't know why that worked as the server name resolved but it did. You might give that a try...or...confirm that the server name you're using is resolving into a valid ip address for the host server. In addition, confirm that the host server isn't using a named instance that might be reequired.
best of luck
February 19, 2008 at 6:25 pm
Thanks for the reply.
Im just tried with IP address and still no good =( I am trying to connect to a named instance.
Oh well... i'll just keep looking and trying for a solution.
February 19, 2008 at 6:40 pm
SQL accounts (in SQL 2005) can be locked out if you are enforcing password policies & password expiration (only applicable if you have installed on Windows Server 2003).
When connecting to a named instance, make sure you are using servername\instancename.
Is a connection being made to SQL Server at all? Run SQL Profiler & see what happens. Are you getting a Login Failed event? Or nothing at all?
Do you have network issues between your machine and the server?
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
February 19, 2008 at 6:54 pm
Hi,
I think the problem exists with the configuration of Management Studio on my computer. Other people can connect fine, and I dont have an issue with the login/password when i RDP onto the database server and use the Management Studio from there.
I have also tried to reset/unlock/turn off policy check and expire for the login.
February 19, 2008 at 7:01 pm
Another possibility is if the host is remote and not on your network, make sure that your firewall is allowing the connection. The point about the account being locked out is one to check, definitely.
February 19, 2008 at 8:04 pm
@hydralisk: Can you ping the server? By name or IP? Can your colleagues (the ones who can successfully connect at least)? What port is SQL Server listening on? Have you checked the SQL Native Client Configuration protocols on your machine? Specifically TCP/IP.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
February 19, 2008 at 8:16 pm
Dear Scott,
The TCP/IP protocol is enabled as well as the shared memory one. VIA and Named Pipes are disabled.
It could well be a port issue. The listening port is 1321. I dont know how to specify what port when i connect using Management Studio.
I have been able to connect from my computer using SQLCMD -S and able to issue a query.
I checked in my logs and whenever i fail the connection from Management Studio its actually showing a State 8 in the server logs.
I hope that info helps.
February 19, 2008 at 8:22 pm
"The TCP/IP protocol is enabled as well as the shared memory one. VIA and Named Pipes are disabled."
Thats on the server.
On MY machine, TCP/IP, Shared Memory, Named Pipes are enabled, VIA is disabled.
February 19, 2008 at 8:29 pm
Two ways you can try. I believe the syntax to enter the ip adress with a port is something like this
xxx.xxx.xxx.xxx, port
yes, that is a comma not a period
the way I usually see it in other types of software is using a colon, such as
xxx.xxx.xxx.xxx:port
I believe the former will work with either the name of the server, or the ip address. I don't know that the latter will work, but it's worth a try.
February 25, 2008 at 1:12 pm
if you can connect by IP it's not a firewall or connection problem, but probably a DNS resolution issue
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply