Re: Sql Remote Connection issue

Hi Guys,

Sorry to jump into this thread, but as I am having a similar problem, it might be helpful to keep to this thread.

I have gone through the steps to ensure that the SQL Database is setup to accept remote connections.
I have spoken to the server support team and they have confirmed that my firewall settings are correct:

port 1433 TCP Allow
port 1434 TCP Allow
IP Packet filtering have been updated to NO to allow access.

I can access the server via Remote Desktop and can connect to the database via the on server version of studio manager.

My Server is windows server 2008 with SQL 2005 (SQLEXPRESS)

I have tried the following and get these results

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\>osql -S tcp:MYSEVER 1433 -Uxxxx -Pxxxxxxxx
Microsoft (R) SQL Server Command Line Tool
Version 9.00.4035.00 NT INTEL X86
Copyright (c) Microsoft Corporation. All rights reserved.

Note: osql does not support all features of SQL Server 2005.
Use sqlcmd instead. See SQL Server Books Online for details.

usage: osql [-U login id] [-P password]
[-S server] [-H hostname] [-E trusted connection]
[-d use database name] [-l login timeout] [-t query timeout]
[-h headers] [-s colseparator] [-w columnwidth]
[-a packetsize] [-e echo input] [-I Enable Quoted Identifiers]
[-L list servers] [-c cmdend] [-D ODBC DSN name]
[-q "cmdline query"] [-Q "cmdline query" and exit]
[-n remove numbering] [-m errorlevel]
[-r msgs to stderr] [-V severitylevel]
[-i inputfile] [-o outputfile]
[-p print statistics] [-b On error batch abort]
[-X[1] disable commands [and exit with warning]]
[-O use Old ISQL behavior disables the following]
<EOF> batch processing
Auto console width scaling
Wide messages
default errorlevel is -1 vs 1
[-? show syntax summary]

C:\>sqlcmd -SMYSEVER, -Uxxx -Pxxxxxxx
HResult 0x57, Level 16, State 1
SQL Network Interfaces: Connection string is not valid [87].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.


C:\>telnet sMYSEVER 1433
Connecting To MYSEVER...Could not open connection to the host, on port 1433: Connect failed

I have tried to view the server logs, by my version of Studio Manager does not have an option to view error logs ??

Many thanks
Lez


"Sylvain Lafontaine" <sylvainlafontaine2009@xxxxxxxx> wrote in message news:e9XvXp3GKHA.4432@xxxxxxxxxxxxxxxxxxxxxxx
Here's another suggestion: are you sure that the SQL-Server Mixed Authentication is activated and that you are using a sql-server login account, not a windows account?

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server (French)


"Ocean City" <OceanCity@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B027FDF4-F608-4CD2-88A2-E39291854CB5@xxxxxxxxxxxxxxxx
Hi Rick,

Anymore ideas on resolving this issue.

"Rick Byham, MSFT" wrote:

Check the SQL Server error log to see if SQL Server is actually using port
1433 instead of some other port. It should have the port number somewhere
shortly after startup.
--
Rick Byham, MSFT
(Implies no warranty or rights)


"Ocean City" <Ocean City@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A590E21-6BBF-4F60-AB52-BE4A058A8DC1@xxxxxxxxxxxxxxxx
> I'm trying to setup Sql Server 2000 to handle remote connections from > the
> web. I have setup the firewall to allow port 1433 to be redirected > back
> to
> the internal Sql Server which I know is working.
>
> To verify the connection I'm using telnet to verify communications is
> working as advertised, however when I telnet to the box I get the
> following
> error message:
>
> Connecting to 12.X.X.9....Could not open connection to the host, on > port
> 1433: Connect Failed
>
> Any ideas or solutions to the above problem would be greatly > appreciated.
>






.

Relevant Pages

  • Re: Accessing sql server
    ... port, select All ports, in Remote port, select Fixed port and input 1433 ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... | I have now checked and I can access the sql server when creating an ODBC ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL2005: Cannot connect error 11001
    ... I believe the complete Windows auth user access is too complicate, ... which trusted connection is meant? ... it would still be listening on the old port. ... Microsoft, SQL Server Books Online ...
    (microsoft.public.sqlserver.connect)
  • Re: Installing Sql Server Express on Vista Home Premium
    ... It seems that your SQL Server instances are Named Instances, ... Default Instances uses 1433 TCP port by default as a Static Port but not the ... If you change your Connection String as following, ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server 2005 Connection Problems
    ... - it is't completely clear what the SQL Server Browser is for. ... connection reqest was being rejected. ... I think the problem is still likely the the port is blocked by some ... firewall between the server and that client. ...
    (microsoft.public.sqlserver.setup)
  • Re: Cannot connect to SQL Express on 2003 Machine from XP machine
    ... enable network communication ... make sure that the port isn't blocked ... "An error has occurred while establishing connection to the server. ... When connecting to SQL Server 2005, this failure may be caused by the ...
    (microsoft.public.sqlserver)
Quantcast