Cannot Register the server

I've installed an Instance of MSDE on a Win2k Machine and and WinXP Machine.
I'm able to register the Instances locally through EM (v.8.0), but when I
try to register them from a different PC with EM on it, I get the following
error.
SQL Server does not exist or access is denied. ConnectionOpen (Connect()
Is MSDE limited to local Enterprise Management?
Wack
This message will self destruct.
hi Ray,
Ray Lewis wrote:
> I've installed an Instance of MSDE on a Win2k Machine and and WinXP
> Machine. I'm able to register the Instances locally through EM
> (v.8.0), but when I try to register them from a different PC with EM
> on it, I get the following error.
> SQL Server does not exist or access is denied. ConnectionOpen
> (Connect()
> Is MSDE limited to local Enterprise Management?
please verify the network protocols are enabled via Server Network Utility
(svrnetcn.exe)...
MSDE installs by default disabling network protocols in order to prevent
external connections/attacks... you have to provide the
DISABLENETWORKPROTOCOLS=0
parameter at install time in order to force network protocols to be enable,
or, later afte install, use svrnetcn.exe to enable and configure the desired
protocol
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks. I finally discovered that. Also, on XP SP2, you need to allow port
1433 through the firewall.
Wack
This message will self destruct.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:38p2mrF5riea7U1@.individual.net...
> hi Ray,
> Ray Lewis wrote:
> please verify the network protocols are enabled via Server Network Utility
> (svrnetcn.exe)...
> MSDE installs by default disabling network protocols in order to prevent
> external connections/attacks... you have to provide the
> DISABLENETWORKPROTOCOLS=0
> parameter at install time in order to force network protocols to be
enable,
> or, later afte install, use svrnetcn.exe to enable and configure the
desired
> protocol
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

cannot register local SQL server

I had SQL Server running locally on my pc and now I
suddenly can't connect. I deleted the registration and
tried re-registering it in EM. When I use Windows
authentication I get a msg saying "cannot open default
database, using master database instead"..but it doesn't
register.
When I use SQL authentication using the sa login, I get a
msg saying "login failed for sa, not associated with a
trusted SQL Server connection". (The SQL Server service
is still running OK on my pc).
Any ideas as to how to fix it, and why it went wrong in
the first place?
Thanks
DaveLooks like you:
1. Run in Windows authentication mode, no sa is permitted
2. you deleted the database (or sent it offline) you specified as defautl
database for the
Windows user you try to connect.
TO sign on as sa change the reg key use this manual:
---
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q285097
---
INF: How to Change the Default Login Authentication Mode to SQL While
Installing SQL Server 2000 Desktop Engine by Using Windows Installer
---
<snip>
Another way to change the security mode after installation is to stop
SQL Server and set the appropriate registry key for your installation:
Default instance:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode
Named instance:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance
Name\MSSQLServer\LoginMode
to 2 for mixed-mode or 1 for integrated. (Integrated is the default
setup for the SQL Server 2000 Data Engine.)
</snip>
HTH, Jens Süßmeyer.
"dave" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||dave
>When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
Do you have a login like (DOMAIN\Dave) ?
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection".
You can change an authentication settings of the server
Right click on the server ,then Properties ,then under Security Tab change
Authentication to SQL and Windows.
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||> You can change an authentication settings of the server
> Right click on the server ,then Properties ,then under Security Tab change
> Authentication to SQL and Windows.
But if you can´t register you are really f.... :)
Jens Süßmeyer.|||An alternative to change login mode to mixed is to login using ISQL.EXE (it will let you in even if
your default database doesn't exist) and use sp_defaultdb to change the default database to an
existing database.
I do not recommend changing default database for sysadmins (for the very reason we see here).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave|||Thanks Jens
Changed the registry setting to 2 and it worked using SQL authentication.
>--Original Message--
>Looks like you:
>1. Run in Windows authentication mode, no sa is permitted
>2. you deleted the database (or sent it offline) you specified as defautl
>database for the
>Windows user you try to connect.
>TO sign on as sa change the reg key use this manual:
>----
--
>http://support.microsoft.com/default.aspx?scid=3Dkb;EN-
US;q285097
>----
--
>INF: How to Change the Default Login Authentication Mode to SQL While
>Installing SQL Server 2000 Desktop Engine by Using Windows Installer
>----
--
><snip>
>Another way to change the security mode after installation is to stop
>SQL Server and set the appropriate registry key for your installation:
>Default instance:
>HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode
>Named instance:
>HKLM\Software\Microsoft\Microsoft SQL Server\Instance
>Name\MSSQLServer\LoginMode
>to 2 for mixed-mode or 1 for integrated. (Integrated is the default
>setup for the SQL Server 2000 Data Engine.)
></snip>
>HTH, Jens S=FC=DFmeyer.
>
>
>"dave" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
>news:06d901c3b41f$68325220$a001280a@.phx.gbl...
>> I had SQL Server running locally on my pc and now I
>> suddenly can't connect. I deleted the registration and
>> tried re-registering it in EM. When I use Windows
>> authentication I get a msg saying "cannot open default
>> database, using master database instead"..but it doesn't
>> register.
>> When I use SQL authentication using the sa login, I get a
>> msg saying "login failed for sa, not associated with a
>> trusted SQL Server connection". (The SQL Server service
>> is still running OK on my pc).
>> Any ideas as to how to fix it, and why it went wrong in
>> the first place?
>> Thanks
>> Dave
>
>.
>|||just change the loginmode parameter in the register to sa..
It should work
--
Shaju Thomas
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:06d901c3b41f$68325220$a001280a@.phx.gbl...
> I had SQL Server running locally on my pc and now I
> suddenly can't connect. I deleted the registration and
> tried re-registering it in EM. When I use Windows
> authentication I get a msg saying "cannot open default
> database, using master database instead"..but it doesn't
> register.
> When I use SQL authentication using the sa login, I get a
> msg saying "login failed for sa, not associated with a
> trusted SQL Server connection". (The SQL Server service
> is still running OK on my pc).
> Any ideas as to how to fix it, and why it went wrong in
> the first place?
> Thanks
> Dave

Cannot make remote connection to SQL Server Express

I'm having trouble making a remote connection to a SQL Server Express
database. The service is started, and the connection works locally. I
tested it using a .udl. In this local .udl, I use the SQL Native
Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
with username/password log on, and initial catalog.
Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
\SQLEXPRESS. The latter entry is a mock-up of the web server's name,
which is 15 characters long, the last 3 being "WEB". The 'B' is
truncated from the server name.
All these connections work locally on the web server (where SQL
Express is running).
The network administrator has opened TCP port 1433 on the web server.
The service has been configured to allow remote connections on TCP/IP
and Named Pipes.

>From the remote machine, the same .udl is set up, but with a Data
Source modified to use an IP address. The Data Source entry then looks
like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
"Test connection failed because of an error initializing provider.
Login timeout expired."
The network administrator reports attempts to communicate with
152.21.110.58 on port 1433. These attempts are being allowed.
I suspect the data source is the problem. Some documentation indicates
port 1433 must be explicitly stated when connecting remotely to SQL
Server 2005 and its variants (including Express). However, I can't
find any examples of explicit port designation in a .udl.
The alternative to explicit port connection (according to some
sources) is to open port 1434 for SQL Browser. That port was opened
and SQL Browser service started, but the connection failed in the same
fashion.
The application that needs to connect is written in C#/.NET.
Can the .udl be configured to test the remote connection? The
initiator of the connection is an Oracle box, so SQLCMD is not an
option for testing remote connections.
Is there something amiss with the Data Source designation? Everything
I read points to replacing server specs like '.' and '(local)' with IP
designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
Is this correct? The SQL Server is a web server in a DMZ, so DNS
translation is not available.
How do I monitor SQL Express for login attempts, both local and
remote?
Thanks,
Dan
Hi Dan
"dan@.wagers.net" wrote:

> I'm having trouble making a remote connection to a SQL Server Express
> database. The service is started, and the connection works locally. I
> tested it using a .udl. In this local .udl, I use the SQL Native
> Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
> with username/password log on, and initial catalog.
> Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
> \SQLEXPRESS. The latter entry is a mock-up of the web server's name,
> which is 15 characters long, the last 3 being "WEB". The 'B' is
> truncated from the server name.
> All these connections work locally on the web server (where SQL
> Express is running).
> The network administrator has opened TCP port 1433 on the web server.
> The service has been configured to allow remote connections on TCP/IP
> and Named Pipes.
> Source modified to use an IP address. The Data Source entry then looks
> like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
> "Test connection failed because of an error initializing provider.
> Login timeout expired."
> The network administrator reports attempts to communicate with
> 152.21.110.58 on port 1433. These attempts are being allowed.
> I suspect the data source is the problem. Some documentation indicates
> port 1433 must be explicitly stated when connecting remotely to SQL
> Server 2005 and its variants (including Express). However, I can't
> find any examples of explicit port designation in a .udl.
> The alternative to explicit port connection (according to some
> sources) is to open port 1434 for SQL Browser. That port was opened
> and SQL Browser service started, but the connection failed in the same
> fashion.
> The application that needs to connect is written in C#/.NET.
> Can the .udl be configured to test the remote connection? The
> initiator of the connection is an Oracle box, so SQLCMD is not an
> option for testing remote connections.
> Is there something amiss with the Data Source designation? Everything
> I read points to replacing server specs like '.' and '(local)' with IP
> designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
> Is this correct? The SQL Server is a web server in a DMZ, so DNS
> translation is not available.
> How do I monitor SQL Express for login attempts, both local and
> remote?
> Thanks,
> Dan
>
By default SQLExpress does not have network protocols enabled by default see
http://msdn2.microsoft.com/en-us/library/ms190198.aspx ,
http://msdn2.microsoft.com/en-us/library/ms143446.aspx
and
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#disablenetworkprotocols
Using the command line installation option of DISABLENETWORKPROTOCOLS with
values of 0 or 2 will enable Shared Memory and TCP/IP (0 also enables named
pipes)
If this has not be done you can still enable remote connections after you
have installed SQLExpress by using the Surface Area Configuration Tool
(SqlSAC.exe)
to enable remote connections see
http://msdn2.microsoft.com/en-us/library/ms173748.aspx
John

Cannot make remote connection to SQL Server Express

I'm having trouble making a remote connection to a SQL Server Express
database. The service is started, and the connection works locally. I
tested it using a .udl. In this local .udl, I use the SQL Native
Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
with username/password log on, and initial catalog.
Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
\SQLEXPRESS. The latter entry is a mock-up of the web server's name,
which is 15 characters long, the last 3 being "WEB". The 'B' is
truncated from the server name.
All these connections work locally on the web server (where SQL
Express is running).
The network administrator has opened TCP port 1433 on the web server.
The service has been configured to allow remote connections on TCP/IP
and Named Pipes.
>From the remote machine, the same .udl is set up, but with a Data
Source modified to use an IP address. The Data Source entry then looks
like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
"Test connection failed because of an error initializing provider.
Login timeout expired."
The network administrator reports attempts to communicate with
152.21.110.58 on port 1433. These attempts are being allowed.
I suspect the data source is the problem. Some documentation indicates
port 1433 must be explicitly stated when connecting remotely to SQL
Server 2005 and its variants (including Express). However, I can't
find any examples of explicit port designation in a .udl.
The alternative to explicit port connection (according to some
sources) is to open port 1434 for SQL Browser. That port was opened
and SQL Browser service started, but the connection failed in the same
fashion.
The application that needs to connect is written in C#/.NET.
Can the .udl be configured to test the remote connection? The
initiator of the connection is an Oracle box, so SQLCMD is not an
option for testing remote connections.
Is there something amiss with the Data Source designation? Everything
I read points to replacing server specs like '.' and '(local)' with IP
designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
Is this correct? The SQL Server is a web server in a DMZ, so DNS
translation is not available.
How do I monitor SQL Express for login attempts, both local and
remote?
Thanks,
DanHi Dan
"dan@.wagers.net" wrote:
> I'm having trouble making a remote connection to a SQL Server Express
> database. The service is started, and the connection works locally. I
> tested it using a .udl. In this local .udl, I use the SQL Native
> Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
> with username/password log on, and initial catalog.
> Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
> \SQLEXPRESS. The latter entry is a mock-up of the web server's name,
> which is 15 characters long, the last 3 being "WEB". The 'B' is
> truncated from the server name.
> All these connections work locally on the web server (where SQL
> Express is running).
> The network administrator has opened TCP port 1433 on the web server.
> The service has been configured to allow remote connections on TCP/IP
> and Named Pipes.
> >From the remote machine, the same .udl is set up, but with a Data
> Source modified to use an IP address. The Data Source entry then looks
> like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
> "Test connection failed because of an error initializing provider.
> Login timeout expired."
> The network administrator reports attempts to communicate with
> 152.21.110.58 on port 1433. These attempts are being allowed.
> I suspect the data source is the problem. Some documentation indicates
> port 1433 must be explicitly stated when connecting remotely to SQL
> Server 2005 and its variants (including Express). However, I can't
> find any examples of explicit port designation in a .udl.
> The alternative to explicit port connection (according to some
> sources) is to open port 1434 for SQL Browser. That port was opened
> and SQL Browser service started, but the connection failed in the same
> fashion.
> The application that needs to connect is written in C#/.NET.
> Can the .udl be configured to test the remote connection? The
> initiator of the connection is an Oracle box, so SQLCMD is not an
> option for testing remote connections.
> Is there something amiss with the Data Source designation? Everything
> I read points to replacing server specs like '.' and '(local)' with IP
> designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
> Is this correct? The SQL Server is a web server in a DMZ, so DNS
> translation is not available.
> How do I monitor SQL Express for login attempts, both local and
> remote?
> Thanks,
> Dan
>
By default SQLExpress does not have network protocols enabled by default see
http://msdn2.microsoft.com/en-us/library/ms190198.aspx ,
http://msdn2.microsoft.com/en-us/library/ms143446.aspx
and
http://msdn2.microsoft.com/en-us/library/ms144259.aspx#disablenetworkprotocols
Using the command line installation option of DISABLENETWORKPROTOCOLS with
values of 0 or 2 will enable Shared Memory and TCP/IP (0 also enables named
pipes)
If this has not be done you can still enable remote connections after you
have installed SQLExpress by using the Surface Area Configuration Tool
(SqlSAC.exe)
to enable remote connections see
http://msdn2.microsoft.com/en-us/library/ms173748.aspx
John

Cannot make remote connection to SQL Server Express

I'm having trouble making a remote connection to a SQL Server Express
database. The service is started, and the connection works locally. I
tested it using a .udl. In this local .udl, I use the SQL Native
Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
with username/password log on, and initial catalog.
Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
\SQLEXPRESS. The latter entry is a mock-up of the web server's name,
which is 15 characters long, the last 3 being "WEB". The 'B' is
truncated from the server name.
All these connections work locally on the web server (where SQL
Express is running).
The network administrator has opened TCP port 1433 on the web server.
The service has been configured to allow remote connections on TCP/IP
and Named Pipes.

>From the remote machine, the same .udl is set up, but with a Data
Source modified to use an IP address. The Data Source entry then looks
like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
"Test connection failed because of an error initializing provider.
Login timeout expired."
The network administrator reports attempts to communicate with
152.21.110.58 on port 1433. These attempts are being allowed.
I suspect the data source is the problem. Some documentation indicates
port 1433 must be explicitly stated when connecting remotely to SQL
Server 2005 and its variants (including Express). However, I can't
find any examples of explicit port designation in a .udl.
The alternative to explicit port connection (according to some
sources) is to open port 1434 for SQL Browser. That port was opened
and SQL Browser service started, but the connection failed in the same
fashion.
The application that needs to connect is written in C#/.NET.
Can the .udl be configured to test the remote connection? The
initiator of the connection is an Oracle box, so SQLCMD is not an
option for testing remote connections.
Is there something amiss with the Data Source designation? Everything
I read points to replacing server specs like '.' and '(local)' with IP
designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
Is this correct? The SQL Server is a web server in a DMZ, so DNS
translation is not available.
How do I monitor SQL Express for login attempts, both local and
remote?
Thanks,
DanHi Dan
"dan@.wagers.net" wrote:

> I'm having trouble making a remote connection to a SQL Server Express
> database. The service is started, and the connection works locally. I
> tested it using a .udl. In this local .udl, I use the SQL Native
> Client as the provider, and a Data Source entry of (local)\SQLEXPRESS,
> with username/password log on, and initial catalog.
> Other Data Source entries that work are .\SQLEXPRESS and LOTSAYOWSAWE
> \SQLEXPRESS. The latter entry is a mock-up of the web server's name,
> which is 15 characters long, the last 3 being "WEB". The 'B' is
> truncated from the server name.
> All these connections work locally on the web server (where SQL
> Express is running).
> The network administrator has opened TCP port 1433 on the web server.
> The service has been configured to allow remote connections on TCP/IP
> and Named Pipes.
>
> Source modified to use an IP address. The Data Source entry then looks
> like 152.21.110.58\SQLEXPRESS. I test the connection and get the error
> "Test connection failed because of an error initializing provider.
> Login timeout expired."
> The network administrator reports attempts to communicate with
> 152.21.110.58 on port 1433. These attempts are being allowed.
> I suspect the data source is the problem. Some documentation indicates
> port 1433 must be explicitly stated when connecting remotely to SQL
> Server 2005 and its variants (including Express). However, I can't
> find any examples of explicit port designation in a .udl.
> The alternative to explicit port connection (according to some
> sources) is to open port 1434 for SQL Browser. That port was opened
> and SQL Browser service started, but the connection failed in the same
> fashion.
> The application that needs to connect is written in C#/.NET.
> Can the .udl be configured to test the remote connection? The
> initiator of the connection is an Oracle box, so SQLCMD is not an
> option for testing remote connections.
> Is there something amiss with the Data Source designation? Everything
> I read points to replacing server specs like '.' and '(local)' with IP
> designations like 152.21.110.68, and keeping the '\SQLEXPRESS' part.
> Is this correct? The SQL Server is a web server in a DMZ, so DNS
> translation is not available.
> How do I monitor SQL Express for login attempts, both local and
> remote?
> Thanks,
> Dan
>
By default SQLExpress does not have network protocols enabled by default see
http://msdn2.microsoft.com/en-us/library/ms190198.aspx ,
http://msdn2.microsoft.com/en-us/library/ms143446.aspx
and
l]
Using the command line installation option of DISABLENETWORKPROTOCOLS with
values of 0 or 2 will enable Shared Memory and TCP/IP (0 also enables named
pipes)
If this has not be done you can still enable remote connections after you
have installed SQLExpress by using the Surface Area Configuration Tool
(SqlSAC.exe)
to enable remote connections see
[url]http://msdn2.microsoft.com/en-us/library/ms173748.aspx" target="_blank">http://msdn2.microsoft.com/en-us/li...y/ms173748.aspx
John

cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scottsorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David|||many thanks for reply.
i think you are right about this.
Cheers
Scott

cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scott
sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?
|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David
|||many thanks for reply.
i think you are right about this.
Cheers
Scott

cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scottsorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <i
pv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David|||many thanks for reply.
i think you are right about this.
Cheers
Scott

Cannot install BI Developement Studio

I am able to install SSRS, and it works from my local machine. I also
installed SQL Server 2005 locally so the ReportServer and ReportServerTempDB
can be created locally on my computer. However, BI Development Studio will
not install. I get an message about APPCOMPAT. I tried another install with
JUST BI development studio selected
I have Visual Studio 2003, and we are a SQL Server 2000 shop. Could those
be issues?BI Development studio is a version of VS 2005, however, it will install side
by side with VS 2003 (I am running this way). What operating system are you
on?
Also, I assume this configuration is for development. At some point RS will
be on another box. Keep in mind that whatever box RS 2005 is on you have to
have a SQL 2005 license for that box. Also, you can have ReportServer and
ReportServerTempDB residing on SQL 2000. I.e. you can run RS 2005 on a SQL
2000 box without upgrading the db to 2005 as long as you have a 2005 license
(I did this for awhile as well).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:0393291F-4711-4BF0-A70F-14DB2375513C@.microsoft.com...
>I am able to install SSRS, and it works from my local machine. I also
> installed SQL Server 2005 locally so the ReportServer and
> ReportServerTempDB
> can be created locally on my computer. However, BI Development Studio will
> not install. I get an message about APPCOMPAT. I tried another install
> with
> JUST BI development studio selected
> I have Visual Studio 2003, and we are a SQL Server 2000 shop. Could those
> be issues?|||Hi Bruce,
i've installed RS 2005 developer edition on a pc which i've installed
SQL Server 2000 developer edition as well. The SQL 2000 is used to
store reportserver db.
i've configured everything using RS Configuration and everything has
green tick...
however, when i browse Report Manager using IE , it just wouldn't show
- The page could not be displayed.
No error message. Anything else i should be checking ?
When i browse report manager from IIS, it doesn't display as well...
pls help...