Showing posts with label remote. Show all posts
Showing posts with label remote. Show all posts

Tuesday, March 27, 2012

Cannot Enable Remote Connections for AS 2005 on clustered instance

Hello SQL pros -

I am having a problem with enabling the remote connections for Analysis
Services 2005, Here's the gist....

--Error Information--
"To configure Analysis Services for Remote Connections, you must be an
adminsitrator for Analysis Services Windows Service (SQLSAC).

Additonal Info
A connection cannot be made. Ensure that service is running
(Microsoft.AnalysisServices)
No connection could be made because the target machine actively refused
it (System)."

--Actions Taken--
1) Analysis Services Windows Service was confirmed to be running.
2) Analysis Services Windows Service was stopped and restarted.
3) Analysis Services Windows Service (and SQL Accounts) confirmed to be
running under domain account with administrator priviledges.
4) Confirmed connectivity to Analysis Services instance through direct
connection (Windows Authentication)

--OS/System Information--
Windows 2000 Service Pack 5

--Clustering Roles--
Primary node for 1 SQL 2000 SP4 instance
Secondary node 1 SQL 2000 SP4 instance
Primary node for 1 Analysis Services 2000 instance
Primary node for 1 SQL 2005 instance, and primary
Primary node for 1 SQL 2005 Analysis Services Instance

I didn't find anything of relevance in the Windows logs or SQL logs.
So I am not sure where else to look. Is this a bug with 2005?

Any Suggestions to help troubleshoot are greatly appreciated!

thanks in advance.

ben

First.

Here some fresh blog post on how to troubleshoot connectivity problems with Analysis Services:

http://www.sqljunkies.com/WebLog/edwardm/

Second.
You saying
"4) Confirmed connectivity to Analysis Services instance through direct
connection (Windows Authentication)"

Analysis Services support only Windows Authentication when connecing through TCP/IP.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Please also note when connecting to clustered Analysis Server you only need to specify "VirtualServer" as a server name , not "VirtualServer\Instace".

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

ANTIVIRUS PROBLEM

uninstall your antivirus and try again

Thursday, March 22, 2012

Cannot deploy

Hello, I attempted to deploy my reports to a remote web server where RS
is installed. The two RS databases exist, as do the two virtuals.
Anyone seen the error below or have any procedure for diagnosing it?
Thanks,
-KJ
************************** error follows ***************
TITLE: Microsoft Report Designer
--
A connection could not be made to the report server
http://10.12.48.97/ReportServer.
--
ADDITIONAL INFORMATION:
Client found response content type of 'text/html; charset=utf-8', but
expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server
Reporting Services 9.00.2047.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt;
COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt;
DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt;
COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300;
TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300;
TEXT-DECORATION:underline}
</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>The report server has encountered a configuration error. See the
report server log files for more information.
(rsServerConfigurationError) </li><ul>
<li>For more information about this error navigate to the report
server on the local server machine, or enable remote errors</li>
</ul><hr width="100%" size="1" color="silver" /><span
class="ProductInfo">SQL Server Reporting Services</span>
</ul>
</body>
--. (Microsoft.ReportingServices.Designer)
--
BUTTONS:
OK
--Cancel this request; after much ado, I got it up and running.
n_o_s_p_a__m@.mail.com wrote:
> Hello, I attempted to deploy my reports to a remote web server where RS
> is installed. The two RS databases exist, as do the two virtuals.
> Anyone seen the error below or have any procedure for diagnosing it?
> Thanks,
> -KJ
> ************************** error follows ***************
> TITLE: Microsoft Report Designer
> --
> A connection could not be made to the report server
> http://10.12.48.97/ReportServer.
> --
> ADDITIONAL INFORMATION:
> Client found response content type of 'text/html; charset=utf-8', but
> expected 'text/xml'.
> The request failed with the error message:
> --
> <html>
> <head>
> <title>
> SQL Server Reporting Services
> </title><meta name="Generator" content="Microsoft SQL Server
> Reporting Services 9.00.2047.00" />
> <meta name="HTTP Status" content="500" />
> <meta name="ProductLocaleID" content="9" />
> <meta name="CountryLocaleID" content="1033" />
> <style>
> BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt;
> COLOR:black}
> H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
> LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt;
> DISPLAY:inline}
> .ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt;
> COLOR:gray}
> A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
> TEXT-DECORATION:none}
> A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#FF3300;
> TEXT-DECORATION:underline}
> A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR:#3366CC;
> TEXT-DECORATION:none}
> A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; color:#FF3300;
> TEXT-DECORATION:underline}
> </style>
> </head><body bgcolor="white">
> <h1>
> Reporting Services Error<hr width="100%" size="1" color="silver" />
> </h1><ul>
> <li>The report server has encountered a configuration error. See the
> report server log files for more information.
> (rsServerConfigurationError) </li><ul>
> <li>For more information about this error navigate to the report
> server on the local server machine, or enable remote errors</li>
> </ul><hr width="100%" size="1" color="silver" /><span
> class="ProductInfo">SQL Server Reporting Services</span>
> </ul>
> </body>
> --. (Microsoft.ReportingServices.Designer)
> --
> BUTTONS:
> OK
> --

Cannot delete remote server

Trying to delete remote server 'DVA'

- When I go to delete the 'DVA' from the list of remote servers I get
- Error 15190: There are still remote logins for the server 'DVA'

I execute the following statement to list remote logins

- execute sp_helpRemoteLogin

the output returns

SERVER | LOCAL | REMOTE | OPTIONS
T1 | Distributor_admin | distributor_admin | trusted
T1 | Distributor_admin | sa | trusted

Fair enough I go to delete those remote logins using

- execute sp_dropremotelogin 'DVA' ,'distributor_admin', 'distributor_admin'
- execute sp_dropremotelogin 'DVA' ,'distributor_admin', 'sa'

but.. get the following error messages

There is no remote user 'Distributor_admin' and 'sa' mapped to the local user 'distributor_admin' from the remote server 'DVA'

Don't understand why it is not finding those logins and how to resolve?It almost sounds like a publication is still active on the server. Is that true.

Can you drop the publication(s) and then check to sede if the remote server is still listed?

Monday, March 19, 2012

Cannot Create New Database

when i am trying to connect to sql server2005 thru Visual studio i am getting an Error:

"SQL Server does not allow remote connections (provider: Named Pipes Provider, error: 40 could not open connection to Sql Server)"

Can any body tell me why is it happening and its Solution....

You will have to enable Remote Connections for your SQL Server instance, by default this is turned off. See the screencast on the screencast section on my website for more details.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Sunday, March 11, 2012

Cannot create an ODBC connection to SQl 2000.

Hi all,

I have SQL 2000 enterprise edition(no service pack) installed on a Windows Server 2003 machine. I can remote access into the server and run SQL but I cannot create an ODBC connection to this from my desktop. From some research it looks like installing service packs might correct this but here is the error:

--connection failed

--sqlstate '01000'

--sql server error 10061

--connection failed

--sqlstate 08001

--sql server error 17

--SQL server does not exist or access denied

Any help would be appreciated.

Verify whether the SQL Server is listening on a TCP port. If it's a default instance it is by default 1433, so you can use

netstat -an | findstr 1433

If not but the TCP protocol is turned on for the server (and set to port 1433) then upgrading to the latest service pack will most likely solve your problem.

|||

It'd better for you to upgrade SQL Server 2000 to latest service pack 4 from here:

http://support.microsoft.com/kb/290211#EOADAA

then make sure following things before you make connection:

1) SQL Service is running

2) If make remote connection, make sure named pipe or TCP was enabled and try Peter's suggestion if you want to connect through tcp.

HTH.

Saturday, February 25, 2012

Cannot connect to SQL Servrer 2005 remotely using another account than sa

Hi there,
I set up an SQL Server 2005 Enterprise Edition, so it is listening on
the network.
I can login successfully from a remote machine using osql:
osql -H sqlhost -U sa
Password: XXX
1>
However I created another user "test" (SQL Auth.) and also a database
which test should be allowed to access but test cannot login remotely
(test _can_ login locally, for example in the management studio)
osql -H sqlhost -U test -d db_test
Password: XXX
Login failed for user 'test'.
What is strange about it, is that it doesn't even show up in the logs
that it did not work. There is no mention of the user "test" in the
logs when the remote login fails.
Any idea what to check? What am I doing wrong? :-(
Regards,
marcNote that you should use -S server_name\instance_name.
Perhaps you are connecting to a local instance.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Marc" wrote:
> Hi there,
> I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> the network.
> I can login successfully from a remote machine using osql:
> osql -H sqlhost -U sa
> Password: XXX
> 1>
> However I created another user "test" (SQL Auth.) and also a database
> which test should be allowed to access but test cannot login remotely
> (test _can_ login locally, for example in the management studio)
> osql -H sqlhost -U test -d db_test
> Password: XXX
> Login failed for user 'test'.
> What is strange about it, is that it doesn't even show up in the logs
> that it did not work. There is no mention of the user "test" in the
> logs when the remote login fails.
> Any idea what to check? What am I doing wrong? :-(
> Regards,
> marc
>|||When you are using 'osql -H sqlhost -U sa' without -S you are connecting to
the default instance on the local computer. Try it and run this to verify
select @.@.servername
go
Ben Nevarez, MCDBA, OCP
Database Administrator
"Ben Nevarez" wrote:
> Note that you should use -S server_name\instance_name.
> Perhaps you are connecting to a local instance.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Marc" wrote:
> > Hi there,
> > I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> > the network.
> > I can login successfully from a remote machine using osql:
> >
> > osql -H sqlhost -U sa
> > Password: XXX
> > 1>
> >
> > However I created another user "test" (SQL Auth.) and also a database
> > which test should be allowed to access but test cannot login remotely
> > (test _can_ login locally, for example in the management studio)
> >
> > osql -H sqlhost -U test -d db_test
> > Password: XXX
> > Login failed for user 'test'.
> >
> > What is strange about it, is that it doesn't even show up in the logs
> > that it did not work. There is no mention of the user "test" in the
> > logs when the remote login fails.
> >
> > Any idea what to check? What am I doing wrong? :-(
> >
> > Regards,
> > marc
> >
> >|||Yes you are right! Thanks!!

Friday, February 24, 2012

cannot connect to SQL Server via Query Analyzer

Hello, I am new to SQL and I would like to connect to a remote sql server.
I have Win 2k Professional installed at my PC and I have installation CD of
SQL Server 2000 Developer Edition.
I have chosen following options during installation:
SQL Server 2000 Components --> Install Database Server --> Local
Computer --> Create a new instance of SQL Server, or install Client
tools --> Client tools only
All installation process has looked good, no error message during it.
Now I am running SQL Query Analyzer and I am trying to connect to our remote
SQL server (which is certainly running) but without any success, the error
message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
access denied." always will appear.
Maybe there is something wrong with my PC as only following ports are opened
there: 80, 135, 139, 445, 1025
I think that also the port 1434 should be opened but it is not and I cannot
open it.
Please help
MarkIf you are connecting to a default instance then, try to use the follwing
for your server name
tcp:<servername>,1433
replace <servername> with your server name.
and make sure the port 1433 is open.
This way we are forcing it to use the tcpip protocol on the specified port.
Be default the default instance listens on port 1433.
hth
--
Vikram Vamshi
Eclipsys Corporation
"Marcello" <marcello@.inetcom.cz> wrote in message
news:%23Ufg2GFIFHA.2860@.TK2MSFTNGP12.phx.gbl...
> Hello, I am new to SQL and I would like to connect to a remote sql server.
> I have Win 2k Professional installed at my PC and I have installation CD
> of
> SQL Server 2000 Developer Edition.
> I have chosen following options during installation:
> SQL Server 2000 Components --> Install Database Server --> Local
> Computer --> Create a new instance of SQL Server, or install Client
> tools --> Client tools only
> All installation process has looked good, no error message during it.
> Now I am running SQL Query Analyzer and I am trying to connect to our
> remote
> SQL server (which is certainly running) but without any success, the error
> message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
> access denied." always will appear.
> Maybe there is something wrong with my PC as only following ports are
> opened
> there: 80, 135, 139, 445, 1025
> I think that also the port 1434 should be opened but it is not and I
> cannot
> open it.
> Please help
> Mark
>

cannot connect to SQL Server via Query Analyzer

Hello, I am new to SQL and I would like to connect to a remote sql server.
I have Win 2k Professional installed at my PC and I have installation CD of
SQL Server 2000 Developer Edition.
I have chosen following options during installation:
SQL Server 2000 Components --> Install Database Server --> Local
Computer --> Create a new instance of SQL Server, or install Client
tools --> Client tools only
All installation process has looked good, no error message during it.
Now I am running SQL Query Analyzer and I am trying to connect to our remote
SQL server (which is certainly running) but without any success, the error
message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
access denied." always will appear.
Maybe there is something wrong with my PC as only following ports are opened
there: 80, 135, 139, 445, 1025
I think that also the port 1434 should be opened but it is not and I cannot
open it.
Please help
Mark
If you are connecting to a default instance then, try to use the follwing
for your server name
tcp:<servername>,1433
replace <servername> with your server name.
and make sure the port 1433 is open.
This way we are forcing it to use the tcpip protocol on the specified port.
Be default the default instance listens on port 1433.
hth
Vikram Vamshi
Eclipsys Corporation
"Marcello" <marcello@.inetcom.cz> wrote in message
news:%23Ufg2GFIFHA.2860@.TK2MSFTNGP12.phx.gbl...
> Hello, I am new to SQL and I would like to connect to a remote sql server.
> I have Win 2k Professional installed at my PC and I have installation CD
> of
> SQL Server 2000 Developer Edition.
> I have chosen following options during installation:
> SQL Server 2000 Components --> Install Database Server --> Local
> Computer --> Create a new instance of SQL Server, or install Client
> tools --> Client tools only
> All installation process has looked good, no error message during it.
> Now I am running SQL Query Analyzer and I am trying to connect to our
> remote
> SQL server (which is certainly running) but without any success, the error
> message "Unable to connect to server xxxxxx: SQL Server doesnot exist or
> access denied." always will appear.
> Maybe there is something wrong with my PC as only following ports are
> opened
> there: 80, 135, 139, 445, 1025
> I think that also the port 1434 should be opened but it is not and I
> cannot
> open it.
> Please help
> Mark
>

Cannot connect to SQL Server 2005 April CTP from remote computer

Hi,

I am trying to connect to a SQL Server on a Windows2003 w/sp1 Server from a remote computer but always seem to get the infamous "Access is denied or Server Does Not Exist" error. However, if I try to connect from the machine that is running the server, there is no problem. (Used sql account, server=mixed authentication)

The windows 2003 Server is a single server installation with .Net 2005 Beta 2 Team Suite, Team Foundation Server and Sql Server - Installing these items took me a while, but eventually I managed to install from scatch to end without any installation errors.

I have triple checked that both TCP 1433 and UDP 1434 is open on my router and under windows firewall.

I have ensured that TCP/IP is enabled in SQL Server Configuration Manager for both "SQL Native Client Configuration" AND "Protocals for MSSQLServer". The default in the registry is DNETLIB (thus the appropriate protocal should be used based on the client)

I have set no Alias' in "SQL Native Client Configuration"

SQL Server is setup for mixed Authentication and I am trying to connect via a sql account.

SQL Server Browser is not running.

Below I have attached the results of running netstat -n, a sql log file and the results of a ipconfig /all

If there is any other information that one might need to help me figure out this problem, just ask.

Thanks for your help!

-Brian

Running netstat -n gives the following results
--
Proto Local Address Foreign Address State
TCP 127.0.0.1:135 127.0.0.1:4760 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1034 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1036 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1042 ESTABLISHED
TCP 127.0.0.1:1025 127.0.0.1:4761 ESTABLISHED
TCP 127.0.0.1:1034 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1035 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1036 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1042 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:4760 127.0.0.1:135 ESTABLISHED
TCP 127.0.0.1:4761 127.0.0.1:1025 ESTABLISHED
TCP 192.168.0.164:389 192.168.0.164:1145 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1147 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1640 ESTABLISHED
TCP 192.168.0.164:1145 192.168.0.164:389 ESTABLISHED
TCP 192.168.0.164:1147 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:1150 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3705 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3706 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3707 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3708 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3720 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3811 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6187 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6188 ESTABLISHED
TCP 192.168.0.164:1640 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:3187 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:3705 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3706 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3707 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3708 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3720 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3811 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:5891 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:5896 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:6157 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6158 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6174 192.168.0.164:2383 TIME_WAIT
TCP 192.168.0.164:6187 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:6188 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:1150 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:3187 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5891 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5896 ESTABLISHED
The following is one of my sql Logs.

Date,Source,Severity,Message
06/17/2005 07:24:14,spid20s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpstar90.dll' version '2000.90.1116' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpsqlbot.dll' version '2000.90.1116' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
06/17/2005 07:19:40,spid11s,Unknown,Service Broker manager has started.
06/17/2005 07:19:40,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid4s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
06/17/2005 07:19:38,spid8s,Unknown,Starting up database 'tempdb'.
06/17/2005 07:19:33,spid13s,Unknown,Starting up database 'rlbss'.
06/17/2005 07:19:32,spid11s,Unknown,Starting up database 'BisDWDB'.
06/17/2005 07:19:32,spid4s,Unknown,Recovery is writing a checkpoint in database 'BisDB' (8). This is an informational message only. No user action is required.
06/17/2005 07:19:26,spid14s,Unknown,Starting up database 'VSTEAMTeamBuild'.
06/17/2005 07:19:23,spid13s,Unknown,Starting up database 'VSTEAMSCCAdmin'.
06/17/2005 07:19:23,spid11s,Unknown,Starting up database 'VSTEAMSCC'.
06/17/2005 07:19:22,spid12s,Unknown,Starting up database 'BisDB'.
06/17/2005 07:19:22,spid12s,Unknown,Recovery is writing a checkpoint in database 'CurrituckDB' (7). This is an informational message only. No user action is required.
06/17/2005 07:19:22,spid8s,Unknown,Clearing tempdb database.
06/17/2005 07:19:20,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.0.164]
06/17/2005 07:19:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1.
06/17/2005 07:19:17,spid14s,Unknown,Starting up database 'CurrituckDB'.
06/17/2005 07:19:17,spid13s,Unknown,Starting up database 'ReportServerTempDB'.
06/17/2005 07:19:17,spid12s,Unknown,Starting up database 'ReportServer'.
06/17/2005 07:19:16,spid11s,Unknown,Starting up database 'msdb'.
06/17/2005 07:19:16,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
06/17/2005 07:19:16,Server,Unknown,The SQL Network Interface library was unable to register SPN. Error: 0x54b.
06/17/2005 07:19:16,Server,Unknown,Error: 26037<c/> Severity: 16<c/> State: 1.
06/17/2005 07:19:16,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
06/17/2005 07:19:16,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
06/17/2005 07:19:16,Server,Unknown,Server shared memory provider is ready for clients to connect to [ \\.\pipe\SQLSm\MSSQLSERVER ].
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
06/17/2005 07:19:16,spid8s,Unknown,Starting up database 'model'.
06/17/2005 07:19:16,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
06/17/2005 07:19:16,spid4s,Unknown,Server name is 'BRIAN-SRV'. This is an informational message only. No user action is required.
06/17/2005 07:19:14,spid4s,Unknown,Starting up database 'mssqlsystemresource'.
06/17/2005 07:19:14,spid4s,Unknown,SQL Trace ID 1 was started by login "sa".
06/17/2005 07:19:14,spid4s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
06/17/2005 07:19:12,spid4s,Unknown,Starting up database 'master'.
06/17/2005 07:19:12,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
06/17/2005 07:19:12,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
06/17/2005 07:19:10,Server,Unknown,Detected 1 CPUs. This is an informational message; no user action is required.
06/17/2005 07:19:10,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
06/17/2005 07:19:10,Server,Unknown,-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
06/17/2005 07:19:10,Server,Unknown,-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
06/17/2005 07:19:10,Server,Unknown,-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
06/17/2005 07:19:10,Server,Unknown,Registry startup parameters:
06/17/2005 07:19:10,Server,Unknown,This instance of SQL Server last reported using a process ID of 640 at 6/17/2005 3:23:15 AM (local) 6/17/2005 7:23:15 AM (UTC). This is an informational message only; no user action is required.
06/17/2005 07:19:10,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
06/17/2005 07:19:10,Server,Unknown,Server process ID is 736.
06/17/2005 07:19:10,Server,Unknown,All rights reserved.
06/17/2005 07:19:10,Server,Unknown,(c) 2004 Microsoft Corporation.
06/17/2005 07:19:10,Server,Unknown,Microsoft SQL Server 2005 - 9.00.1116 (Intel X86) Apr 9 2005 20:56:37 Copyright (c) 1988-2004 Microsoft Corporation Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
results of IPCONFIG /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : brian-srv
Primary Dns Suffix . . . . . . . : brianfurner.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : brianfurner.local
cityxx.phub.net.cable.rogers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cityxx.phub.net.cable.rogers.com
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-2E-44-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.164
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.0.164
Lease Obtained. . . . . . . . . . : Friday, June 17, 2005 7:18:35 AM
Lease Expires . . . . . . . . . . : Friday, June 24, 2005 7:18:35 AM

Also, if you wish to see a list of the services running on my server, please click this link.

http://hoser.hopto.org:97/test.htm

Thanks

|||

I am still trying to get this working, I am pleading, if someone has any ideas, please let me know.

Thanks

|||Is there a reason you chose not to start SQL Browser?

What is the instance name and what are you typing in the connection string of the app.

-Euan|||

Hi,

I did not start SQL Browser, as I read it is not necessary so long as you specifically set the port in TCP/IP settings in Configuration Manager.

I believe the instance name as the same as the computer name. When I hold my mouse over the sql server icon in the taskbar it shows this

BRIAN-SRV - MSSQLServer

The connection string is irrelevant at this point. I was trying to connect using VS.NET 2005 Server explorer. I chose to "Add a Data Connection"

Entered my IP Address as my server name.
my SQL user account and Password and my initial catalog.

THanks.

|||The instance name may be the same as the computer name. Did you install as a named instance or default instance?

You can tell this by looking in the registry for the SQL Server services, if they have something in () after the service name then you have a named instance.

In that case you must run SQL Browser for port resolution or you must fix the port number of the instance(by default named instance ports are dynamic, on the default instance is statically assigned and by default this is 1433).|||Another thought, does the server have a valid IP address, at one point in the log it is listening on 127.0.0.1, thats the loopback connection.

Can you connect locally using sqlcmd?

-Euan|||Hey Euan,

Thanks for your help.

Yes, I can connect locally using sqlcmd.

IN
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

I see a key named InstalledInstances. ITs value is MSSQLSERVER SHAREPOINT

I had also wondered if the server was only loopingback. But I do not know how to change this within SQL Server.

Thanks Euan.|||Hey Euan,

Here is my ip configuration for SQL SERVER.

http://hoser.hopto.org:97/ip1.jpg

http://hoser.hopto.org:97/ip2.jpg

http://hoser.hopto.org:97/ipall.jpg

Thanks again!

-Brian|||Try going to www.grc.com and using shields up to test port 1433 to see if your firewall is open on that port and forwarding it to SQL server.|||Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian|||For those still grappling with this problem, I needed to run SQL Server Configuration Manager and expand the node "SQL Server 2005 Network Configuration/Protocols for <instance name>". I then enabled the TCP/IP protocol and voila! I was able to connect to the 2005 SQL Server using a remote device.|||

I have just installed the ssme ctp on the machine I am running vs2005c#Express and it cant find the connection either. I am not accessing it remotely, although I would like to be able to in the future, but for now I would just like to do all my work on this same machine. Any ideas why I can not get a connection?

Roger

|||I had the same problem, and those jerks at rogers swore up and down

they weren't blocking port 1433, but after changing the port, mine

worked too!

I'm so pissed I'd like to complain to one of their vp's, but that old

saying about &%#^ rolling downhill was probably started at in the

context of rogers.|||

Brian Furner wrote:

Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian

Thank you so much! I had the exact same problem as you, and I was about to tear my hair off, but now I changed the port and it all works like it should.
Indeed your post helps others, and I marked it as such :)

Again, thank you.

Cannot connect to SQL Server 2005 April CTP from remote computer

Hi,

I am trying to connect to a SQL Server on a Windows2003 w/sp1 Server from a remote computer but always seem to get the infamous "Access is denied or Server Does Not Exist" error. However, if I try to connect from the machine that is running the server, there is no problem. (Used sql account, server=mixed authentication)

The windows 2003 Server is a single server installation with .Net 2005 Beta 2 Team Suite, Team Foundation Server and Sql Server - Installing these items took me a while, but eventually I managed to install from scatch to end without any installation errors.

I have triple checked that both TCP 1433 and UDP 1434 is open on my router and under windows firewall.

I have ensured that TCP/IP is enabled in SQL Server Configuration Manager for both "SQL Native Client Configuration" AND "Protocals for MSSQLServer". The default in the registry is DNETLIB (thus the appropriate protocal should be used based on the client)

I have set no Alias' in "SQL Native Client Configuration"

SQL Server is setup for mixed Authentication and I am trying to connect via a sql account.

SQL Server Browser is not running.

Below I have attached the results of running netstat -n, a sql log file and the results of a ipconfig /all

If there is any other information that one might need to help me figure out this problem, just ask.

Thanks for your help!

-Brian

Running netstat -n gives the following results
--
Proto Local Address Foreign Address State
TCP 127.0.0.1:135 127.0.0.1:4760 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1034 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1036 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1042 ESTABLISHED
TCP 127.0.0.1:1025 127.0.0.1:4761 ESTABLISHED
TCP 127.0.0.1:1034 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1035 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1036 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1042 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:4760 127.0.0.1:135 ESTABLISHED
TCP 127.0.0.1:4761 127.0.0.1:1025 ESTABLISHED
TCP 192.168.0.164:389 192.168.0.164:1145 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1147 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1640 ESTABLISHED
TCP 192.168.0.164:1145 192.168.0.164:389 ESTABLISHED
TCP 192.168.0.164:1147 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:1150 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3705 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3706 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3707 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3708 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3720 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3811 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6187 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6188 ESTABLISHED
TCP 192.168.0.164:1640 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:3187 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:3705 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3706 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3707 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3708 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3720 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3811 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:5891 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:5896 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:6157 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6158 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6174 192.168.0.164:2383 TIME_WAIT
TCP 192.168.0.164:6187 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:6188 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:1150 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:3187 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5891 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5896 ESTABLISHED
The following is one of my sql Logs.

Date,Source,Severity,Message
06/17/2005 07:24:14,spid20s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpstar90.dll' version '2000.90.1116' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpsqlbot.dll' version '2000.90.1116' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
06/17/2005 07:19:40,spid11s,Unknown,Service Broker manager has started.
06/17/2005 07:19:40,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid4s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
06/17/2005 07:19:38,spid8s,Unknown,Starting up database 'tempdb'.
06/17/2005 07:19:33,spid13s,Unknown,Starting up database 'rlbss'.
06/17/2005 07:19:32,spid11s,Unknown,Starting up database 'BisDWDB'.
06/17/2005 07:19:32,spid4s,Unknown,Recovery is writing a checkpoint in database 'BisDB' (8). This is an informational message only. No user action is required.
06/17/2005 07:19:26,spid14s,Unknown,Starting up database 'VSTEAMTeamBuild'.
06/17/2005 07:19:23,spid13s,Unknown,Starting up database 'VSTEAMSCCAdmin'.
06/17/2005 07:19:23,spid11s,Unknown,Starting up database 'VSTEAMSCC'.
06/17/2005 07:19:22,spid12s,Unknown,Starting up database 'BisDB'.
06/17/2005 07:19:22,spid12s,Unknown,Recovery is writing a checkpoint in database 'CurrituckDB' (7). This is an informational message only. No user action is required.
06/17/2005 07:19:22,spid8s,Unknown,Clearing tempdb database.
06/17/2005 07:19:20,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.0.164]
06/17/2005 07:19:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1.
06/17/2005 07:19:17,spid14s,Unknown,Starting up database 'CurrituckDB'.
06/17/2005 07:19:17,spid13s,Unknown,Starting up database 'ReportServerTempDB'.
06/17/2005 07:19:17,spid12s,Unknown,Starting up database 'ReportServer'.
06/17/2005 07:19:16,spid11s,Unknown,Starting up database 'msdb'.
06/17/2005 07:19:16,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
06/17/2005 07:19:16,Server,Unknown,The SQL Network Interface library was unable to register SPN. Error: 0x54b.
06/17/2005 07:19:16,Server,Unknown,Error: 26037<c/> Severity: 16<c/> State: 1.
06/17/2005 07:19:16,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
06/17/2005 07:19:16,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
06/17/2005 07:19:16,Server,Unknown,Server shared memory provider is ready for clients to connect to [ \\.\pipe\SQLSm\MSSQLSERVER ].
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
06/17/2005 07:19:16,spid8s,Unknown,Starting up database 'model'.
06/17/2005 07:19:16,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
06/17/2005 07:19:16,spid4s,Unknown,Server name is 'BRIAN-SRV'. This is an informational message only. No user action is required.
06/17/2005 07:19:14,spid4s,Unknown,Starting up database 'mssqlsystemresource'.
06/17/2005 07:19:14,spid4s,Unknown,SQL Trace ID 1 was started by login "sa".
06/17/2005 07:19:14,spid4s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
06/17/2005 07:19:12,spid4s,Unknown,Starting up database 'master'.
06/17/2005 07:19:12,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
06/17/2005 07:19:12,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
06/17/2005 07:19:10,Server,Unknown,Detected 1 CPUs. This is an informational message; no user action is required.
06/17/2005 07:19:10,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
06/17/2005 07:19:10,Server,Unknown,-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
06/17/2005 07:19:10,Server,Unknown,-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
06/17/2005 07:19:10,Server,Unknown,-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
06/17/2005 07:19:10,Server,Unknown,Registry startup parameters:
06/17/2005 07:19:10,Server,Unknown,This instance of SQL Server last reported using a process ID of 640 at 6/17/2005 3:23:15 AM (local) 6/17/2005 7:23:15 AM (UTC). This is an informational message only; no user action is required.
06/17/2005 07:19:10,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
06/17/2005 07:19:10,Server,Unknown,Server process ID is 736.
06/17/2005 07:19:10,Server,Unknown,All rights reserved.
06/17/2005 07:19:10,Server,Unknown,(c) 2004 Microsoft Corporation.
06/17/2005 07:19:10,Server,Unknown,Microsoft SQL Server 2005 - 9.00.1116 (Intel X86) Apr 9 2005 20:56:37 Copyright (c) 1988-2004 Microsoft Corporation Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
results of IPCONFIG /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : brian-srv
Primary Dns Suffix . . . . . . . : brianfurner.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : brianfurner.local
cityxx.phub.net.cable.rogers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cityxx.phub.net.cable.rogers.com
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-2E-44-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.164
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.0.164
Lease Obtained. . . . . . . . . . : Friday, June 17, 2005 7:18:35 AM
Lease Expires . . . . . . . . . . : Friday, June 24, 2005 7:18:35 AM

Also, if you wish to see a list of the services running on my server, please click this link.

http://hoser.hopto.org:97/test.htm

Thanks

|||

I am still trying to get this working, I am pleading, if someone has any ideas, please let me know.

Thanks

|||Is there a reason you chose not to start SQL Browser?

What is the instance name and what are you typing in the connection string of the app.

-Euan|||

Hi,

I did not start SQL Browser, as I read it is not necessary so long as you specifically set the port in TCP/IP settings in Configuration Manager.

I believe the instance name as the same as the computer name. When I hold my mouse over the sql server icon in the taskbar it shows this

BRIAN-SRV - MSSQLServer

The connection string is irrelevant at this point. I was trying to connect using VS.NET 2005 Server explorer. I chose to "Add a Data Connection"

Entered my IP Address as my server name.
my SQL user account and Password and my initial catalog.

THanks.

|||The instance name may be the same as the computer name. Did you install as a named instance or default instance?

You can tell this by looking in the registry for the SQL Server services, if they have something in () after the service name then you have a named instance.

In that case you must run SQL Browser for port resolution or you must fix the port number of the instance(by default named instance ports are dynamic, on the default instance is statically assigned and by default this is 1433).|||Another thought, does the server have a valid IP address, at one point in the log it is listening on 127.0.0.1, thats the loopback connection.

Can you connect locally using sqlcmd?

-Euan|||Hey Euan,

Thanks for your help.

Yes, I can connect locally using sqlcmd.

IN
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

I see a key named InstalledInstances. ITs value is MSSQLSERVER SHAREPOINT

I had also wondered if the server was only loopingback. But I do not know how to change this within SQL Server.

Thanks Euan.|||Hey Euan,

Here is my ip configuration for SQL SERVER.

http://hoser.hopto.org:97/ip1.jpg

http://hoser.hopto.org:97/ip2.jpg

http://hoser.hopto.org:97/ipall.jpg

Thanks again!

-Brian|||Try going to www.grc.com and using shields up to test port 1433 to see if your firewall is open on that port and forwarding it to SQL server.|||Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian|||For those still grappling with this problem, I needed to run SQL Server Configuration Manager and expand the node "SQL Server 2005 Network Configuration/Protocols for <instance name>". I then enabled the TCP/IP protocol and voila! I was able to connect to the 2005 SQL Server using a remote device.|||

I have just installed the ssme ctp on the machine I am running vs2005c#Express and it cant find the connection either. I am not accessing it remotely, although I would like to be able to in the future, but for now I would just like to do all my work on this same machine. Any ideas why I can not get a connection?

Roger

|||I had the same problem, and those jerks at rogers swore up and down

they weren't blocking port 1433, but after changing the port, mine

worked too!

I'm so pissed I'd like to complain to one of their vp's, but that old

saying about &%#^ rolling downhill was probably started at in the

context of rogers.|||

Brian Furner wrote:

Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian

Thank you so much! I had the exact same problem as you, and I was about to tear my hair off, but now I changed the port and it all works like it should.
Indeed your post helps others, and I marked it as such :)

Again, thank you.

Cannot connect to SQL Server 2005 April CTP from remote computer

Hi,

I am trying to connect to a SQL Server on a Windows2003 w/sp1 Server from a remote computer but always seem to get the infamous "Access is denied or Server Does Not Exist" error. However, if I try to connect from the machine that is running the server, there is no problem. (Used sql account, server=mixed authentication)

The windows 2003 Server is a single server installation with .Net 2005 Beta 2 Team Suite, Team Foundation Server and Sql Server - Installing these items took me a while, but eventually I managed to install from scatch to end without any installation errors.

I have triple checked that both TCP 1433 and UDP 1434 is open on my router and under windows firewall.

I have ensured that TCP/IP is enabled in SQL Server Configuration Manager for both "SQL Native Client Configuration" AND "Protocals for MSSQLServer". The default in the registry is DNETLIB (thus the appropriate protocal should be used based on the client)

I have set no Alias' in "SQL Native Client Configuration"

SQL Server is setup for mixed Authentication and I am trying to connect via a sql account.

SQL Server Browser is not running.

Below I have attached the results of running netstat -n, a sql log file and the results of a ipconfig /all

If there is any other information that one might need to help me figure out this problem, just ask.

Thanks for your help!

-Brian

Running netstat -n gives the following results
--
Proto Local Address Foreign Address State
TCP 127.0.0.1:135 127.0.0.1:4760 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1034 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1036 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1042 ESTABLISHED
TCP 127.0.0.1:1025 127.0.0.1:4761 ESTABLISHED
TCP 127.0.0.1:1034 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1035 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1036 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1042 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:4760 127.0.0.1:135 ESTABLISHED
TCP 127.0.0.1:4761 127.0.0.1:1025 ESTABLISHED
TCP 192.168.0.164:389 192.168.0.164:1145 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1147 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1640 ESTABLISHED
TCP 192.168.0.164:1145 192.168.0.164:389 ESTABLISHED
TCP 192.168.0.164:1147 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:1150 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3705 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3706 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3707 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3708 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3720 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3811 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6187 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6188 ESTABLISHED
TCP 192.168.0.164:1640 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:3187 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:3705 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3706 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3707 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3708 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3720 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3811 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:5891 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:5896 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:6157 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6158 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6174 192.168.0.164:2383 TIME_WAIT
TCP 192.168.0.164:6187 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:6188 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:1150 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:3187 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5891 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5896 ESTABLISHED
The following is one of my sql Logs.

Date,Source,Severity,Message
06/17/2005 07:24:14,spid20s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpstar90.dll' version '2000.90.1116' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpsqlbot.dll' version '2000.90.1116' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
06/17/2005 07:19:40,spid11s,Unknown,Service Broker manager has started.
06/17/2005 07:19:40,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid4s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
06/17/2005 07:19:38,spid8s,Unknown,Starting up database 'tempdb'.
06/17/2005 07:19:33,spid13s,Unknown,Starting up database 'rlbss'.
06/17/2005 07:19:32,spid11s,Unknown,Starting up database 'BisDWDB'.
06/17/2005 07:19:32,spid4s,Unknown,Recovery is writing a checkpoint in database 'BisDB' (8). This is an informational message only. No user action is required.
06/17/2005 07:19:26,spid14s,Unknown,Starting up database 'VSTEAMTeamBuild'.
06/17/2005 07:19:23,spid13s,Unknown,Starting up database 'VSTEAMSCCAdmin'.
06/17/2005 07:19:23,spid11s,Unknown,Starting up database 'VSTEAMSCC'.
06/17/2005 07:19:22,spid12s,Unknown,Starting up database 'BisDB'.
06/17/2005 07:19:22,spid12s,Unknown,Recovery is writing a checkpoint in database 'CurrituckDB' (7). This is an informational message only. No user action is required.
06/17/2005 07:19:22,spid8s,Unknown,Clearing tempdb database.
06/17/2005 07:19:20,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.0.164]
06/17/2005 07:19:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1.
06/17/2005 07:19:17,spid14s,Unknown,Starting up database 'CurrituckDB'.
06/17/2005 07:19:17,spid13s,Unknown,Starting up database 'ReportServerTempDB'.
06/17/2005 07:19:17,spid12s,Unknown,Starting up database 'ReportServer'.
06/17/2005 07:19:16,spid11s,Unknown,Starting up database 'msdb'.
06/17/2005 07:19:16,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
06/17/2005 07:19:16,Server,Unknown,The SQL Network Interface library was unable to register SPN. Error: 0x54b.
06/17/2005 07:19:16,Server,Unknown,Error: 26037<c/> Severity: 16<c/> State: 1.
06/17/2005 07:19:16,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
06/17/2005 07:19:16,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
06/17/2005 07:19:16,Server,Unknown,Server shared memory provider is ready for clients to connect to [ \\.\pipe\SQLSm\MSSQLSERVER ].
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
06/17/2005 07:19:16,spid8s,Unknown,Starting up database 'model'.
06/17/2005 07:19:16,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
06/17/2005 07:19:16,spid4s,Unknown,Server name is 'BRIAN-SRV'. This is an informational message only. No user action is required.
06/17/2005 07:19:14,spid4s,Unknown,Starting up database 'mssqlsystemresource'.
06/17/2005 07:19:14,spid4s,Unknown,SQL Trace ID 1 was started by login "sa".
06/17/2005 07:19:14,spid4s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
06/17/2005 07:19:12,spid4s,Unknown,Starting up database 'master'.
06/17/2005 07:19:12,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
06/17/2005 07:19:12,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
06/17/2005 07:19:10,Server,Unknown,Detected 1 CPUs. This is an informational message; no user action is required.
06/17/2005 07:19:10,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
06/17/2005 07:19:10,Server,Unknown,-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
06/17/2005 07:19:10,Server,Unknown,-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
06/17/2005 07:19:10,Server,Unknown,-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
06/17/2005 07:19:10,Server,Unknown,Registry startup parameters:
06/17/2005 07:19:10,Server,Unknown,This instance of SQL Server last reported using a process ID of 640 at 6/17/2005 3:23:15 AM (local) 6/17/2005 7:23:15 AM (UTC). This is an informational message only; no user action is required.
06/17/2005 07:19:10,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
06/17/2005 07:19:10,Server,Unknown,Server process ID is 736.
06/17/2005 07:19:10,Server,Unknown,All rights reserved.
06/17/2005 07:19:10,Server,Unknown,(c) 2004 Microsoft Corporation.
06/17/2005 07:19:10,Server,Unknown,Microsoft SQL Server 2005 - 9.00.1116 (Intel X86) Apr 9 2005 20:56:37 Copyright (c) 1988-2004 Microsoft Corporation Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
results of IPCONFIG /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : brian-srv
Primary Dns Suffix . . . . . . . : brianfurner.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : brianfurner.local
cityxx.phub.net.cable.rogers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cityxx.phub.net.cable.rogers.com
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-2E-44-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.164
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.0.164
Lease Obtained. . . . . . . . . . : Friday, June 17, 2005 7:18:35 AM
Lease Expires . . . . . . . . . . : Friday, June 24, 2005 7:18:35 AM

Also, if you wish to see a list of the services running on my server, please click this link.

http://hoser.hopto.org:97/test.htm

Thanks

|||

I am still trying to get this working, I am pleading, if someone has any ideas, please let me know.

Thanks

|||Is there a reason you chose not to start SQL Browser?

What is the instance name and what are you typing in the connection string of the app.

-Euan|||

Hi,

I did not start SQL Browser, as I read it is not necessary so long as you specifically set the port in TCP/IP settings in Configuration Manager.

I believe the instance name as the same as the computer name. When I hold my mouse over the sql server icon in the taskbar it shows this

BRIAN-SRV - MSSQLServer

The connection string is irrelevant at this point. I was trying to connect using VS.NET 2005 Server explorer. I chose to "Add a Data Connection"

Entered my IP Address as my server name.
my SQL user account and Password and my initial catalog.

THanks.

|||The instance name may be the same as the computer name. Did you install as a named instance or default instance?

You can tell this by looking in the registry for the SQL Server services, if they have something in () after the service name then you have a named instance.

In that case you must run SQL Browser for port resolution or you must fix the port number of the instance(by default named instance ports are dynamic, on the default instance is statically assigned and by default this is 1433).|||Another thought, does the server have a valid IP address, at one point in the log it is listening on 127.0.0.1, thats the loopback connection.

Can you connect locally using sqlcmd?

-Euan|||Hey Euan,

Thanks for your help.

Yes, I can connect locally using sqlcmd.

IN
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

I see a key named InstalledInstances. ITs value is MSSQLSERVER SHAREPOINT

I had also wondered if the server was only loopingback. But I do not know how to change this within SQL Server.

Thanks Euan.|||Hey Euan,

Here is my ip configuration for SQL SERVER.

http://hoser.hopto.org:97/ip1.jpg

http://hoser.hopto.org:97/ip2.jpg

http://hoser.hopto.org:97/ipall.jpg

Thanks again!

-Brian|||Try going to www.grc.com and using shields up to test port 1433 to see if your firewall is open on that port and forwarding it to SQL server.|||Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian|||For those still grappling with this problem, I needed to run SQL Server Configuration Manager and expand the node "SQL Server 2005 Network Configuration/Protocols for <instance name>". I then enabled the TCP/IP protocol and voila! I was able to connect to the 2005 SQL Server using a remote device.|||

I have just installed the ssme ctp on the machine I am running vs2005c#Express and it cant find the connection either. I am not accessing it remotely, although I would like to be able to in the future, but for now I would just like to do all my work on this same machine. Any ideas why I can not get a connection?

Roger

|||I had the same problem, and those jerks at rogers swore up and down

they weren't blocking port 1433, but after changing the port, mine

worked too!

I'm so pissed I'd like to complain to one of their vp's, but that old

saying about &%#^ rolling downhill was probably started at in the

context of rogers.|||

Brian Furner wrote:

Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian

Thank you so much! I had the exact same problem as you, and I was about to tear my hair off, but now I changed the port and it all works like it should.
Indeed your post helps others, and I marked it as such :)

Again, thank you.

Cannot connect to SQL Server 2005 April CTP from remote computer

Hi,

I am trying to connect to a SQL Server on a Windows2003 w/sp1 Server from a remote computer but always seem to get the infamous "Access is denied or Server Does Not Exist" error. However, if I try to connect from the machine that is running the server, there is no problem. (Used sql account, server=mixed authentication)

The windows 2003 Server is a single server installation with .Net 2005 Beta 2 Team Suite, Team Foundation Server and Sql Server - Installing these items took me a while, but eventually I managed to install from scatch to end without any installation errors.

I have triple checked that both TCP 1433 and UDP 1434 is open on my router and under windows firewall.

I have ensured that TCP/IP is enabled in SQL Server Configuration Manager for both "SQL Native Client Configuration" AND "Protocals for MSSQLServer". The default in the registry is DNETLIB (thus the appropriate protocal should be used based on the client)

I have set no Alias' in "SQL Native Client Configuration"

SQL Server is setup for mixed Authentication and I am trying to connect via a sql account.

SQL Server Browser is not running.

Below I have attached the results of running netstat -n, a sql log file and the results of a ipconfig /all

If there is any other information that one might need to help me figure out this problem, just ask.

Thanks for your help!

-Brian

Running netstat -n gives the following results
--
Proto Local Address Foreign Address State
TCP 127.0.0.1:135 127.0.0.1:4760 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1034 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1036 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1042 ESTABLISHED
TCP 127.0.0.1:1025 127.0.0.1:4761 ESTABLISHED
TCP 127.0.0.1:1034 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1035 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1036 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1042 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:4760 127.0.0.1:135 ESTABLISHED
TCP 127.0.0.1:4761 127.0.0.1:1025 ESTABLISHED
TCP 192.168.0.164:389 192.168.0.164:1145 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1147 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1640 ESTABLISHED
TCP 192.168.0.164:1145 192.168.0.164:389 ESTABLISHED
TCP 192.168.0.164:1147 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:1150 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3705 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3706 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3707 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3708 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3720 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3811 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6187 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6188 ESTABLISHED
TCP 192.168.0.164:1640 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:3187 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:3705 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3706 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3707 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3708 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3720 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3811 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:5891 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:5896 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:6157 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6158 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6174 192.168.0.164:2383 TIME_WAIT
TCP 192.168.0.164:6187 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:6188 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:1150 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:3187 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5891 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5896 ESTABLISHED
The following is one of my sql Logs.

Date,Source,Severity,Message
06/17/2005 07:24:14,spid20s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpstar90.dll' version '2000.90.1116' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpsqlbot.dll' version '2000.90.1116' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
06/17/2005 07:19:40,spid11s,Unknown,Service Broker manager has started.
06/17/2005 07:19:40,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid4s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
06/17/2005 07:19:38,spid8s,Unknown,Starting up database 'tempdb'.
06/17/2005 07:19:33,spid13s,Unknown,Starting up database 'rlbss'.
06/17/2005 07:19:32,spid11s,Unknown,Starting up database 'BisDWDB'.
06/17/2005 07:19:32,spid4s,Unknown,Recovery is writing a checkpoint in database 'BisDB' (8). This is an informational message only. No user action is required.
06/17/2005 07:19:26,spid14s,Unknown,Starting up database 'VSTEAMTeamBuild'.
06/17/2005 07:19:23,spid13s,Unknown,Starting up database 'VSTEAMSCCAdmin'.
06/17/2005 07:19:23,spid11s,Unknown,Starting up database 'VSTEAMSCC'.
06/17/2005 07:19:22,spid12s,Unknown,Starting up database 'BisDB'.
06/17/2005 07:19:22,spid12s,Unknown,Recovery is writing a checkpoint in database 'CurrituckDB' (7). This is an informational message only. No user action is required.
06/17/2005 07:19:22,spid8s,Unknown,Clearing tempdb database.
06/17/2005 07:19:20,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.0.164]
06/17/2005 07:19:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1.
06/17/2005 07:19:17,spid14s,Unknown,Starting up database 'CurrituckDB'.
06/17/2005 07:19:17,spid13s,Unknown,Starting up database 'ReportServerTempDB'.
06/17/2005 07:19:17,spid12s,Unknown,Starting up database 'ReportServer'.
06/17/2005 07:19:16,spid11s,Unknown,Starting up database 'msdb'.
06/17/2005 07:19:16,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
06/17/2005 07:19:16,Server,Unknown,The SQL Network Interface library was unable to register SPN. Error: 0x54b.
06/17/2005 07:19:16,Server,Unknown,Error: 26037<c/> Severity: 16<c/> State: 1.
06/17/2005 07:19:16,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
06/17/2005 07:19:16,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
06/17/2005 07:19:16,Server,Unknown,Server shared memory provider is ready for clients to connect to [ \\.\pipe\SQLSm\MSSQLSERVER ].
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
06/17/2005 07:19:16,spid8s,Unknown,Starting up database 'model'.
06/17/2005 07:19:16,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
06/17/2005 07:19:16,spid4s,Unknown,Server name is 'BRIAN-SRV'. This is an informational message only. No user action is required.
06/17/2005 07:19:14,spid4s,Unknown,Starting up database 'mssqlsystemresource'.
06/17/2005 07:19:14,spid4s,Unknown,SQL Trace ID 1 was started by login "sa".
06/17/2005 07:19:14,spid4s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
06/17/2005 07:19:12,spid4s,Unknown,Starting up database 'master'.
06/17/2005 07:19:12,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
06/17/2005 07:19:12,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
06/17/2005 07:19:10,Server,Unknown,Detected 1 CPUs. This is an informational message; no user action is required.
06/17/2005 07:19:10,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
06/17/2005 07:19:10,Server,Unknown,-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
06/17/2005 07:19:10,Server,Unknown,-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
06/17/2005 07:19:10,Server,Unknown,-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
06/17/2005 07:19:10,Server,Unknown,Registry startup parameters:
06/17/2005 07:19:10,Server,Unknown,This instance of SQL Server last reported using a process ID of 640 at 6/17/2005 3:23:15 AM (local) 6/17/2005 7:23:15 AM (UTC). This is an informational message only; no user action is required.
06/17/2005 07:19:10,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
06/17/2005 07:19:10,Server,Unknown,Server process ID is 736.
06/17/2005 07:19:10,Server,Unknown,All rights reserved.
06/17/2005 07:19:10,Server,Unknown,(c) 2004 Microsoft Corporation.
06/17/2005 07:19:10,Server,Unknown,Microsoft SQL Server 2005 - 9.00.1116 (Intel X86) Apr 9 2005 20:56:37 Copyright (c) 1988-2004 Microsoft Corporation Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
results of IPCONFIG /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : brian-srv
Primary Dns Suffix . . . . . . . : brianfurner.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : brianfurner.local
cityxx.phub.net.cable.rogers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cityxx.phub.net.cable.rogers.com
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-2E-44-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.164
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.0.164
Lease Obtained. . . . . . . . . . : Friday, June 17, 2005 7:18:35 AM
Lease Expires . . . . . . . . . . : Friday, June 24, 2005 7:18:35 AM

Also, if you wish to see a list of the services running on my server, please click this link.

http://hoser.hopto.org:97/test.htm

Thanks

|||

I am still trying to get this working, I am pleading, if someone has any ideas, please let me know.

Thanks

|||Is there a reason you chose not to start SQL Browser?

What is the instance name and what are you typing in the connection string of the app.

-Euan|||

Hi,

I did not start SQL Browser, as I read it is not necessary so long as you specifically set the port in TCP/IP settings in Configuration Manager.

I believe the instance name as the same as the computer name. When I hold my mouse over the sql server icon in the taskbar it shows this

BRIAN-SRV - MSSQLServer

The connection string is irrelevant at this point. I was trying to connect using VS.NET 2005 Server explorer. I chose to "Add a Data Connection"

Entered my IP Address as my server name.
my SQL user account and Password and my initial catalog.

THanks.

|||The instance name may be the same as the computer name. Did you install as a named instance or default instance?

You can tell this by looking in the registry for the SQL Server services, if they have something in () after the service name then you have a named instance.

In that case you must run SQL Browser for port resolution or you must fix the port number of the instance(by default named instance ports are dynamic, on the default instance is statically assigned and by default this is 1433).|||Another thought, does the server have a valid IP address, at one point in the log it is listening on 127.0.0.1, thats the loopback connection.

Can you connect locally using sqlcmd?

-Euan|||Hey Euan,

Thanks for your help.

Yes, I can connect locally using sqlcmd.

IN
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

I see a key named InstalledInstances. ITs value is MSSQLSERVER SHAREPOINT

I had also wondered if the server was only loopingback. But I do not know how to change this within SQL Server.

Thanks Euan.|||Hey Euan,

Here is my ip configuration for SQL SERVER.

http://hoser.hopto.org:97/ip1.jpg

http://hoser.hopto.org:97/ip2.jpg

http://hoser.hopto.org:97/ipall.jpg

Thanks again!

-Brian|||Try going to www.grc.com and using shields up to test port 1433 to see if your firewall is open on that port and forwarding it to SQL server.|||Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian|||For those still grappling with this problem, I needed to run SQL Server Configuration Manager and expand the node "SQL Server 2005 Network Configuration/Protocols for <instance name>". I then enabled the TCP/IP protocol and voila! I was able to connect to the 2005 SQL Server using a remote device.|||

I have just installed the ssme ctp on the machine I am running vs2005c#Express and it cant find the connection either. I am not accessing it remotely, although I would like to be able to in the future, but for now I would just like to do all my work on this same machine. Any ideas why I can not get a connection?

Roger

|||I had the same problem, and those jerks at rogers swore up and down

they weren't blocking port 1433, but after changing the port, mine

worked too!

I'm so pissed I'd like to complain to one of their vp's, but that old

saying about &%#^ rolling downhill was probably started at in the

context of rogers.|||

Brian Furner wrote:

Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian

Thank you so much! I had the exact same problem as you, and I was about to tear my hair off, but now I changed the port and it all works like it should.
Indeed your post helps others, and I marked it as such :)

Again, thank you.

Cannot connect to SQL Server 2005 April CTP from remote computer

Hi,

I am trying to connect to a SQL Server on a Windows2003 w/sp1 Server from a remote computer but always seem to get the infamous "Access is denied or Server Does Not Exist" error. However, if I try to connect from the machine that is running the server, there is no problem. (Used sql account, server=mixed authentication)

The windows 2003 Server is a single server installation with .Net 2005 Beta 2 Team Suite, Team Foundation Server and Sql Server - Installing these items took me a while, but eventually I managed to install from scatch to end without any installation errors.

I have triple checked that both TCP 1433 and UDP 1434 is open on my router and under windows firewall.

I have ensured that TCP/IP is enabled in SQL Server Configuration Manager for both "SQL Native Client Configuration" AND "Protocals for MSSQLServer". The default in the registry is DNETLIB (thus the appropriate protocal should be used based on the client)

I have set no Alias' in "SQL Native Client Configuration"

SQL Server is setup for mixed Authentication and I am trying to connect via a sql account.

SQL Server Browser is not running.

Below I have attached the results of running netstat -n, a sql log file and the results of a ipconfig /all

If there is any other information that one might need to help me figure out this problem, just ask.

Thanks for your help!

-Brian

Running netstat -n gives the following results
--
Proto Local Address Foreign Address State
TCP 127.0.0.1:135 127.0.0.1:4760 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1034 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1036 ESTABLISHED
TCP 127.0.0.1:389 127.0.0.1:1042 ESTABLISHED
TCP 127.0.0.1:1025 127.0.0.1:4761 ESTABLISHED
TCP 127.0.0.1:1034 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1035 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1036 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:1042 127.0.0.1:389 ESTABLISHED
TCP 127.0.0.1:4760 127.0.0.1:135 ESTABLISHED
TCP 127.0.0.1:4761 127.0.0.1:1025 ESTABLISHED
TCP 192.168.0.164:389 192.168.0.164:1145 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1147 ESTABLISHED
TCP 192.168.0.164:1025 192.168.0.164:1640 ESTABLISHED
TCP 192.168.0.164:1145 192.168.0.164:389 ESTABLISHED
TCP 192.168.0.164:1147 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:1150 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3705 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3706 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3707 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3708 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3720 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:3811 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6187 ESTABLISHED
TCP 192.168.0.164:1433 192.168.0.164:6188 ESTABLISHED
TCP 192.168.0.164:1640 192.168.0.164:1025 ESTABLISHED
TCP 192.168.0.164:3187 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:3705 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3706 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3707 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3708 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3720 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:3811 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:5891 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:5896 192.168.0.164:8080 ESTABLISHED
TCP 192.168.0.164:6157 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6158 192.168.0.164:8080 TIME_WAIT
TCP 192.168.0.164:6174 192.168.0.164:2383 TIME_WAIT
TCP 192.168.0.164:6187 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:6188 192.168.0.164:1433 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:1150 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:3187 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5891 ESTABLISHED
TCP 192.168.0.164:8080 192.168.0.164:5896 ESTABLISHED
The following is one of my sql Logs.

Date,Source,Severity,Message
06/17/2005 07:24:14,spid20s,Unknown,Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpstar90.dll' version '2000.90.1116' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
06/17/2005 07:19:45,spid53,Unknown,Using 'xpsqlbot.dll' version '2000.90.1116' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
06/17/2005 07:19:40,spid11s,Unknown,Service Broker manager has started.
06/17/2005 07:19:40,spid11s,Unknown,The Database Mirroring protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid11s,Unknown,The Service Broker protocol transport is disabled or not configured.
06/17/2005 07:19:40,spid4s,Unknown,Recovery is complete. This is an informational message only. No user action is required.
06/17/2005 07:19:38,spid8s,Unknown,Starting up database 'tempdb'.
06/17/2005 07:19:33,spid13s,Unknown,Starting up database 'rlbss'.
06/17/2005 07:19:32,spid11s,Unknown,Starting up database 'BisDWDB'.
06/17/2005 07:19:32,spid4s,Unknown,Recovery is writing a checkpoint in database 'BisDB' (8). This is an informational message only. No user action is required.
06/17/2005 07:19:26,spid14s,Unknown,Starting up database 'VSTEAMTeamBuild'.
06/17/2005 07:19:23,spid13s,Unknown,Starting up database 'VSTEAMSCCAdmin'.
06/17/2005 07:19:23,spid11s,Unknown,Starting up database 'VSTEAMSCC'.
06/17/2005 07:19:22,spid12s,Unknown,Starting up database 'BisDB'.
06/17/2005 07:19:22,spid12s,Unknown,Recovery is writing a checkpoint in database 'CurrituckDB' (7). This is an informational message only. No user action is required.
06/17/2005 07:19:22,spid8s,Unknown,Clearing tempdb database.
06/17/2005 07:19:20,Logon,Unknown,Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 192.168.0.164]
06/17/2005 07:19:20,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1.
06/17/2005 07:19:17,spid14s,Unknown,Starting up database 'CurrituckDB'.
06/17/2005 07:19:17,spid13s,Unknown,Starting up database 'ReportServerTempDB'.
06/17/2005 07:19:17,spid12s,Unknown,Starting up database 'ReportServer'.
06/17/2005 07:19:16,spid11s,Unknown,Starting up database 'msdb'.
06/17/2005 07:19:16,Server,Unknown,SQL Server is now ready for client connections. This is an informational message; no user action is required.
06/17/2005 07:19:16,Server,Unknown,The SQL Network Interface library was unable to register SPN. Error: 0x54b.
06/17/2005 07:19:16,Server,Unknown,Error: 26037<c/> Severity: 16<c/> State: 1.
06/17/2005 07:19:16,Server,Unknown,Dedicated admin connection support was established for listening locally on port 1434.
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4> 1434].
06/17/2005 07:19:16,Server,Unknown,Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
06/17/2005 07:19:16,Server,Unknown,Server shared memory provider is ready for clients to connect to [ \\.\pipe\SQLSm\MSSQLSERVER ].
06/17/2005 07:19:16,Server,Unknown,Server is listening on [ 'any' <ipv4> 1433].
06/17/2005 07:19:16,spid8s,Unknown,Starting up database 'model'.
06/17/2005 07:19:16,Server,Unknown,A self-generated certificate was successfully loaded for encryption.
06/17/2005 07:19:16,spid4s,Unknown,Server name is 'BRIAN-SRV'. This is an informational message only. No user action is required.
06/17/2005 07:19:14,spid4s,Unknown,Starting up database 'mssqlsystemresource'.
06/17/2005 07:19:14,spid4s,Unknown,SQL Trace ID 1 was started by login "sa".
06/17/2005 07:19:14,spid4s,Unknown,Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
06/17/2005 07:19:12,spid4s,Unknown,Starting up database 'master'.
06/17/2005 07:19:12,Server,Unknown,Database mirroring has been enabled on this instance of SQL Server.
06/17/2005 07:19:12,Server,Unknown,Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
06/17/2005 07:19:11,Server,Unknown,Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.
06/17/2005 07:19:10,Server,Unknown,Detected 1 CPUs. This is an informational message; no user action is required.
06/17/2005 07:19:10,Server,Unknown,SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
06/17/2005 07:19:10,Server,Unknown,-l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
06/17/2005 07:19:10,Server,Unknown,-e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
06/17/2005 07:19:10,Server,Unknown,-d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
06/17/2005 07:19:10,Server,Unknown,Registry startup parameters:
06/17/2005 07:19:10,Server,Unknown,This instance of SQL Server last reported using a process ID of 640 at 6/17/2005 3:23:15 AM (local) 6/17/2005 7:23:15 AM (UTC). This is an informational message only; no user action is required.
06/17/2005 07:19:10,Server,Unknown,Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
06/17/2005 07:19:10,Server,Unknown,Server process ID is 736.
06/17/2005 07:19:10,Server,Unknown,All rights reserved.
06/17/2005 07:19:10,Server,Unknown,(c) 2004 Microsoft Corporation.
06/17/2005 07:19:10,Server,Unknown,Microsoft SQL Server 2005 - 9.00.1116 (Intel X86) Apr 9 2005 20:56:37 Copyright (c) 1988-2004 Microsoft Corporation Beta Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
results of IPCONFIG /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : brian-srv
Primary Dns Suffix . . . . . . . : brianfurner.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : brianfurner.local
cityxx.phub.net.cable.rogers.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cityxx.phub.net.cable.rogers.com
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-0B-6A-2E-44-A4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.164
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1
192.168.0.164
Lease Obtained. . . . . . . . . . : Friday, June 17, 2005 7:18:35 AM
Lease Expires . . . . . . . . . . : Friday, June 24, 2005 7:18:35 AM

Also, if you wish to see a list of the services running on my server, please click this link.

http://hoser.hopto.org:97/test.htm

Thanks

|||

I am still trying to get this working, I am pleading, if someone has any ideas, please let me know.

Thanks

|||Is there a reason you chose not to start SQL Browser?

What is the instance name and what are you typing in the connection string of the app.

-Euan|||

Hi,

I did not start SQL Browser, as I read it is not necessary so long as you specifically set the port in TCP/IP settings in Configuration Manager.

I believe the instance name as the same as the computer name. When I hold my mouse over the sql server icon in the taskbar it shows this

BRIAN-SRV - MSSQLServer

The connection string is irrelevant at this point. I was trying to connect using VS.NET 2005 Server explorer. I chose to "Add a Data Connection"

Entered my IP Address as my server name.
my SQL user account and Password and my initial catalog.

THanks.

|||The instance name may be the same as the computer name. Did you install as a named instance or default instance?

You can tell this by looking in the registry for the SQL Server services, if they have something in () after the service name then you have a named instance.

In that case you must run SQL Browser for port resolution or you must fix the port number of the instance(by default named instance ports are dynamic, on the default instance is statically assigned and by default this is 1433).|||Another thought, does the server have a valid IP address, at one point in the log it is listening on 127.0.0.1, thats the loopback connection.

Can you connect locally using sqlcmd?

-Euan|||Hey Euan,

Thanks for your help.

Yes, I can connect locally using sqlcmd.

IN
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

I see a key named InstalledInstances. ITs value is MSSQLSERVER SHAREPOINT

I had also wondered if the server was only loopingback. But I do not know how to change this within SQL Server.

Thanks Euan.|||Hey Euan,

Here is my ip configuration for SQL SERVER.

http://hoser.hopto.org:97/ip1.jpg

http://hoser.hopto.org:97/ip2.jpg

http://hoser.hopto.org:97/ipall.jpg

Thanks again!

-Brian|||Try going to www.grc.com and using shields up to test port 1433 to see if your firewall is open on that port and forwarding it to SQL server.|||Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian|||For those still grappling with this problem, I needed to run SQL Server Configuration Manager and expand the node "SQL Server 2005 Network Configuration/Protocols for <instance name>". I then enabled the TCP/IP protocol and voila! I was able to connect to the 2005 SQL Server using a remote device.|||

I have just installed the ssme ctp on the machine I am running vs2005c#Express and it cant find the connection either. I am not accessing it remotely, although I would like to be able to in the future, but for now I would just like to do all my work on this same machine. Any ideas why I can not get a connection?

Roger

|||I had the same problem, and those jerks at rogers swore up and down they weren't blocking port 1433, but after changing the port, mine worked too!
I'm so pissed I'd like to complain to one of their vp's, but that old saying about &%#^ rolling downhill was probably started at in the context of rogers.
|||

Brian Furner wrote:

Thanks Paul!

Through the help of everyone, Euan, Paul and some other friends, we discovered the problem was much more simple then meets the eye.

I should have guessed because I am perfect that it would not be a problem with my settings :P (joke)

Rogers High Speed Internet ISP blocks port 1433 because it is a common port for virus attacks.

I set my router to redirect external traffic on a different port to 1433 internally and voila, successful connection.

I hope this post will help others.

THanks again for everyones help!

-Brian

Thank you so much! I had the exact same problem as you, and I was about to tear my hair off, but now I changed the port and it all works like it should.
Indeed your post helps others, and I marked it as such :)

Again, thank you.