August 5, 2007 at 1:29 pm
I've been installing Interprise client on several machines around the office. All of them can connect to the server, except one. I took the client out of the loop, and tried to connect via sqlcmd on these machines. Again, they all can all connect except the one machine. I believe the machine is XP Pro (and assuming SP2).
I'm not much of a DBA, so any help on what could be the cause of this is greatly appreciated.
August 6, 2007 at 3:17 am
How much of a network engineer are you? Do you have basic network connectivity? Can you see the database via ODBC? Can you ping the database server?
Have you installed the SQL client connectivity tools or are you just using ODBC? If you're just using ODBC there *may* be an MDAC issue, although I think 2.6 is the base standard on XP, and that should work. Does the client login you are using have access rights?
August 6, 2007 at 9:41 am
Is sqlcmd included in SQL 2000 Enterprise manager or are you trying to connect EM tools to SQL 2005? If so that may be the issue. Is you are using EM to connecto SQL 2000 or SSMS/sqlcmd to connect to SQL 2005, then the following steps may help.
Troubleshooting steps to be performed on the difficult XP machine, from a command prompt
1) ping <yourservername here>
If the ping returns Reply(s), proceed to #2, otherwise your basic network connectivity is failing.
2) telnet <yourservername here> 1433
If this is successfuly the screen will clear. This means that no firewall is blocking you and you can connect.
If the screen clears, press; CTRL+] then Q to quit telnet and proceed to #3
If your recieve; Connecting To <yourservername here>...Could not open connection to the host, on port 1433: Connect failed, then you need to open port 1433 in your firewall and/or antivirus program.
3) sqlcmd ...
Verify your sqlcmd command line arguments and retry. Try using a sql login if integrated/trusted connection fails.
[font="Arial"]Clifton G. Collins III[/font]
August 6, 2007 at 1:59 pm
Thanks for the help guys. The problem is resolved and was a result of my fundamental misunderstanding of named pipes. With TCP/IP disabled on the server I could still connect via SQLCMD and the Interprise client on the two machines, but not two others ones. Now that TCP/IP is enabled, both clients can connect.
I'm still confused why two of my clients could connect via SQLCMD to the server via an ip address even though tcp/ip wasn't enabled. I'll have to investigate further to clear up any confusion on my part.
August 7, 2007 at 2:44 am
Just because you're using an IP address to find the server doesn't mean you're communicating with the d/b via TCP/IP, best guess here is that you had different connection options set on the individual SQL clients.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply