Connecting to SQL Server

I installed MSDE today using the setup.exe file, so the syntax was

setup SAPWD=mypassword securitymode=SQL

it worked, I reboot and I see the SQL Server running...

I opened my web matrix, went into the data section and tried to make a new connection to then create databases etc, and it bombs...

I click on SQL Authentication
username sa
password mypassword
and I tried to create a new database

it says either SQL doesn't exsist, or access denied...

any idea's what I did wrong?

Thanks
CadenUPDATE:

I downloaded the new web matrix and everything works just peachy now

Connecting to SQL or MSDE difficulty !

Hey guys,
I am a newbie here, so please bear with me. I have installed SQL Server 2005 CTP on Machine A and MSDE on Machine B. Both these contain the PUBS database beside others. On Machine C, I have installed "ASP.Net Web Matrix" and I want to be able to connect to either Machine A or B to access the PUBS database. It connects to Machine B, when I put in the Servers IP address. But everytime I try to connect to Machine A, it gives me an error saying, "Unable to connect to the database. To connect to this server you must use SQL Server Management Studio or SQL Server Management objects(SMO) ".
I heard that connection strings are needed to access the SQL Server 2005 but I have no idea where to begin. Do I need to create special users to access the Server or will Windows authentication work ? Could anyone help me out in connecting to the SQL Server 2005 CTP?

Management studio is a separate install under management tools, within SQL Server you don't need permissions if you use integrated. When you install the management studio you can register the MSDE. Hope this helps.

|||I had no problems connecting to the MSDE-based server. It's the SQL Server 2005 that's the problem. Could you tell me what I have to do in Management Studio to get the ASP.Net Application that is running on a client machine to connect to it ? Is there some connection string I have to use ? What about this SMO thing ?
|||Try the link below for a walk through tutorial and related link and I would not use SMO (SQL Server Management Object) it is Microsoft property and experience have thought me not to use Microsoft property in my code when using SQL Server. Hope this helps.
http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx|||I tried all that but nothing seems to work. Could the firewall cause a problem ? If yes, then what can I do to rectify it ?|||Yes the firewall usually removes either TCP/IP or Named Pipes from your protocol stack in SQL Server, right click in Management studio and go to properties then Network Configuration and make sure both TCP/IP and Named Pipes is enabled. Hope this helps.|||I get connected to the SQL Server 2000 from a client machine using Web Matrix. I do this by entering the Server name of the SQL Server, say X250-122 and then connecting to a database on that Server. It gives me no problem at all.
When I try the same but in this case trying to connect to an instance of MSDE instead, named NetSDK, i.e. X250-122\NetSDK, on the same Server where SQL Server 2k is installed, then it gives me the following error :

" Unable to connect to the database. SQL Server does not exist or access denied. ConnectionOpen(Connect())".
I tried everything in my capacity that I could but there doesn't seem to be any solution. The protocols ( TCP/IP, Named Pipes) are enabled too. Could you please tell me how to go about this dilemma I am in. Is there a specific way of connecting to an MSDE instance from a client machine ? Please help !!|||The problem was Asp.net account permissions on the MSDE, register it in the full version and go to the security section in Enterprise Manager and configure the server permissions and then to the database and configure the database permissions for Asp.net in the MSDE instance. Another option is to run sp_grantlogin and sp_grantdbaccess in Query Analyzer against the database in the MSDE instance. Hope this helps.
|||I tried doing what you asked and it was already set by default. Ok, let me give you some more details...
I have a local account on each of these machines A, B, C, named say ROOT. SQL Server 2000 and an instance of MSDE named NetSDK is installed on Machine A. All 3 machines have Windows XP Professional with SP 2. Now if I try connecting M/c B or M/c C to the SQL Server on M/c A through the ROOT logins on each of those machines and using ASP.Net Web Matrix, it connects without any problems. But if I do the same trying to connect to NetSDK, it gives me the error I told you about.
I have given ROOT permissions on the SQL Server and the MSDE instance too. But only SQL Server goes through. Thanks for the help, by the way. I appreciate it !!
P.S. By registering the MSDE instance, what did you mean ? I have to register it under Enterprise Manager right ? Because I did that and under Security, there are logins for Machine A\ASPNET, Machine A\ROOT, etc. These are exactly the same as the ones on the SQL Server.
|||Another Problem has just cropped up !! I tried connecting from Machine A to SQL Server 2005 installed on Machine B using the same ROOT login and it didn't work giving me the following error - Unable to connect to the Database. To connect to this Server you must use SQL Server Management Studio or SQL SMO.
But when I tried connecting to Machine B from Query Analyzer i.e. FILE > Connect > Machine B...it works fine. Could you resolve this problem too besides the MSDE one. Thanks !!|||

By registering a server you can access all SQL Server in your network as local access and you do that at the very top of Enterprise Manager. What you do under security is creating a user access to the server not server registration. I have registered 68 SQL Servers in one XP pro box so you will not run into problem with the few instances you have. hope this helps.

|||I did register both the SQL Server and the MSDE instance named NetSDK, but just the SQL Server is granting access to users over the network and it's giving the same error as before. Is my way of accessing correct...i.e. say X250-122\NetSDK ?|||I tried this too... I created a user named ASPNET on the SQL Server machine and I granted the user access under EM for the MSDE instance NetSDK on the same machine. Then I tried logging in from another machine through WebMatrix and it logged in only to the SQL Server and not the NetSDK instance, giving me this error...Unable to connect to the database, Login Failed. Not associated with a trusted SQL Server connection. What could be the reason for that. I am getting access through all the accounts to the SQL Server but not the MSDE instance !!|||Create a new database in the MSDE do an INSERT INTO from the old database then create permissions for the Server under the security section for Asp.net and for the database in the database. Then you may have to delete the old database, I think you have run into orphaned permissions that are created in the Master but not usable in the database. Run a search for orphaned permissions in the BOL (books online). Hope this helps.|||Thanks...it works fine now. I appreciate your help !!

Connecting to SQL Issue

I have a mdf file and log file from msde. I have successfully connected to it in my Visual Studios ASP.net 2.0 Desktop. I am having a problem where it connects. fine but it does not list the tables , diagrams etc. I am trying to build the intake screen with this data but have no tables. Can some one give me a couple of suggestions of why? I am very new to ASP.net and would appreciate any help .How did you connect to the MSDE mdf file? Can you create a Data Connection to it in Server Explorer? Which SQL instance are you using (MSED,SQL Express, etc.)?|||

Hello,

I am using SQL Server Management Studio that came with my visual studios .net 2005.

I open my web application to the design desktop select the tab labeled Server Express the click on the data base to connect it tell me it is connected but no tables show. I was told today by some one I need to be running SQL Server Studio Express I dont understand is the one I have better? The also told me the mdf file was a backup file which they said I need to create a database and then import the mdf backup file into it . I can figure out how to do this I am very new to SQL Server. Help please

Thanks

|||Where does the mdf file come from? Anyways you should attach it to your current SQL instance before you can use it. To do this in Managment Studio, right click Databases in Object Explorer->choose Attach->locate the mdf file. If attach succeeds, you'll see the new attached database under the Databases tree.|||

Thank you,

I found the mdf file to be a bak file I created anew database and restored over the database I created. All tables showed up ok. I only have on question everything seem to work fine except I have no diagrams under the database is this normal not to have this information?

sqlsql

Connecting to SharePoint MSDE Database

I have a SharePoint server that I want to be able to connect to its database
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.
OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:

> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>
sqlsql

Connecting to SharePoint MSDE Database

I have a SharePoint server that I want to be able to connect to its database
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.Hi,
You should be able to connect to any instance of MSDE, whether or not it
is a default or named instance. In fact you are already connecting to a
named instance (the BACKUPEXEC one). Named instances are identified as
follows:
server_name\instance_name
Default instances are identified just by the server (host) name.
Furthermore you cannot change which instance is the default instance on
your server. There is no such thing as a DEFAULT property associated
with an instance. A default instance is one that uses the name of the
host server. Named instances are a development over SQL Server 7.0 in
which only one instance could be installed per Windows server. To get
around this in SQL Server 2000 and later you can install multiple
instances. You can choose to give them all a unique name or you could
give up to one instance no name. It assumes the name of the host and is
called the default instance.
As far as your problem is concerned, in order to help further you need
to tell us what error message you are getting when you attempting a
connection.
Jonathan
APT SA wrote:
> I have a SharePoint server that I want to be able to connect to its databa
se
> and pull info off. When I installed the Sharepoint server it installed an
> instance of msde. For the life of me I cannot remotely connect to this MS
DE
> instance. I am able to remotely connect to the backup exec instance on th
e
> same server and I am able to connect to it when logged in locally. I read
> somewhere that you can only connect to the default instance of msde, is th
is
> true? If so is there a way to change the sharepoint instance to the defau
lt
> instance? any suggestions to this would be greatly appreciated.|||OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:

> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>|||Hi,
Look at the SQL Server error log under c:\program files\microsoft sql
server\mssql\log. The file ERRORLOG should tell you what ip address(es)
and port number(s) the service is listening on. Maybe you could get
more info on what's going wrong in there.
Jonathan
APT SA wrote:[vbcol=seagreen]
> OK, the error I get when attempting to connect to the sharepoint instance
> from computer on LAN on port 1433 is:
> SQL server does not exist or access denied
> I can connect to Backup Exec instance from same computer on LAN. This
> instance uses port 1207
> I can connect to Sharepoint instance when logged on locally to the
> sharepoint server.
> I have port scanned the server and it is listening on port 1207 but not on
> port 1433. I can telnet to port 1207 but not to 1433.
> I have attempted to change the port # for the sharepoint instance and stil
l
> no success. There are no firewalls inbetween the connection.
> I am running MSDE for 2000 with sp4 on it
> TCP/IP and Named Pipes are enabled on both instances of MSDE.
> We are discussing connecting to backupexec instance and linking servers to
> sharepoint instance and then pull data off but this is kind of backwards w
ay
> of doing this...
>
>
> "JPD" wrote:
>

Connecting To Remote MSDE With Server Management Studio

Hello,
I am having issues connecting to an MSDE instance on a remote machine
using MSSQL 9's Server Management Studio.
I am also have issues connecting to a remote instance of MSSQL v7 using
Server Management Studio. Later, I will have to connect to MSSQL v8.
If there is a step-by-step guide somewhere, I would like a URL for it.
Otherwise, I would just like to have input regarding what I should be
checking.
The MSDE was installed without an instance name, so I believe the
instance name is the name of the machine. I believe that I need to
specify the machine and the instance name in the Server Management
Studio connection dialog. I believe the format is
MachineName\InstanceName
In all cases I am using TCP/IP to connect.
All authentication is SQL Auth. The MSDE machine is configured to use
SQL Auth. The MSSQL v7 machine is too.
I was a bit surprised to see the requests on port 1434 instead of 1433.
I'll learn about the reason(s) for this later. Right now, I want to
know if there are any considerations regarding this.
There are firewalls involved, they have been configured to allow
access. This is confirmed by being able to use the MSSQL v7 tools to
connect to both the MSDE and the v7 servers.
The error I receive when connecting to the MSDE machine is:
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (Microsoft SQL Server, Error: -1)
The error I use when connecting to the v7 machine is:
(provider: TCP Provider, error: 0 - A socket operation encountered a
dead network.) (Microsoft SQL Server, Error: 10050)
Any thoughts or ideas?
hi,
> The MSDE was installed without an instance name, so I believe the
> instance name is the name of the machine. I believe that I need to
> specify the machine and the instance name in the Server Management
> Studio connection dialog. I believe the format is
> MachineName\InstanceName
as long as you did not install a named instance, you only have to provide
the MachineName..

> In all cases I am using TCP/IP to connect.
obviously the relative network protocol has been enabled on the remote
server..

> All authentication is SQL Auth. The MSDE machine is configured to use
> SQL Auth. The MSSQL v7 machine is too.
> I was a bit surprised to see the requests on port 1434 instead of
> 1433. I'll learn about the reason(s) for this later. Right now, I
> want to know if there are any considerations regarding this.
TCP/IP 1433 is the IANA assigned port to Microsoft SQL Server, and is the
default port for default instances of SQL Server... named instances usually
adopt the dynamic allocation of a port, so another service is involved,
running on UDP 1434 port, which resolves the connection enquiry redirecting
to the appropriate named instace's used TCP port..

> There are firewalls involved, they have been configured to allow
> access. This is confirmed by being able to use the MSSQL v7 tools to
> connect to both the MSDE and the v7 servers.
> The error I receive when connecting to the MSDE machine is:
> (provider: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (Microsoft SQL Server, Error: -1)
> The error I use when connecting to the v7 machine is:
> (provider: TCP Provider, error: 0 - A socket operation encountered a
> dead network.) (Microsoft SQL Server, Error: 10050)
>
> Any thoughts or ideas?
try having a look at
http://support.microsoft.com/default...b;en-us;905618 ...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Connecting to Named Instance

Hi,

How can i connect to Named Instance of MSDE on remote server from Enterprice Manager in my local computer ?

Instance name is Helm

I can connect inside server like

osql -S -E .\Helm

But how i access from remote machine using Enterprice Manager ?

Regards,

Yujin Bobymachinename\Helm

Connecting to MSDE2000RelA

I was able to install MSDE into WXP and migrated my Access
databases through Windows Integrated Authentication Method.
But whenever I tried connecting to MSDE by SQL login it
gives me the following error:
Invalid username and/or password, you are using a windows
login that is not your own, or server does not exist.
Please help.
Tnx,
Jess
hi Jess,
jess.tayag@.dhl.com wrote:
> I was able to install MSDE into WXP and migrated my Access
> databases through Windows Integrated Authentication Method.
> But whenever I tried connecting to MSDE by SQL login it
> gives me the following error:
> Invalid username and/or password, you are using a windows
> login that is not your own, or server does not exist.
>
if the raised error is
"Login failed for user 'UserName'. Reason: Not associated with a trusted SQL
Server connection."
the reason is MSDE is only allowing WindowsNT trusted connections and not
SQL Server authenticated connections, and this can be solved as explained in
http://support.microsoft.com/default...b;en-us;285097 in the part
regarding the Windows registry modification, while the
"SQL Server does not exists or access denied"
message is usually related to other kind of troubles, as indicated in
http://support.microsoft.com/default...06&Product=sql
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

Connecting to MSDE w/read only file?

Hi,
Does anyone know how I can connect to an MSDE db using VB with a
read-only file? The file will be on a CD, and is actually just archived
data off a SQL server. I would like to package my app on a CD along
with the data file and allow users to pop in the CD and run the app,
assuming they already have MSDE running. Any help?

Thanks,
Jasonhi Jason,
"Jason" <jnorsworthy@.etrade.com> ha scritto nel messaggio
news:1104275382.477692.322310@.z14g2000cwz.googlegr oups.com
> Hi,
> Does anyone know how I can connect to an MSDE db using VB with a
> read-only file? The file will be on a CD, and is actually just
> archived data off a SQL server. I would like to package my app on a
> CD along with the data file and allow users to pop in the CD and run
> the app, assuming they already have MSDE running. Any help?
> Thanks,
> Jason

actually this is possible, providing you mark the database as available on
CD using system stored procedure sp_create_removable and
sp_certify_removable...
this method requires at least 3 physical files, 1 database system data file
that MUST reside on read/write device, 1 data file that will contain all
application's data and that will reside on the removable device, and 1
transaction log file...

please have a look at
http://msdn.microsoft.com/library/d...des_03_92hx.asp
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--- remove DMO to reply

Connecting to MSDE via client

Hope someone can explain why this happened.
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============

connecting to MSDE using SSPI

Please advise: I have created a simple ASPX page to test if I can connect to MSDE on a Server 2003 system. The connection string that works ok is:

server=WS1;database=northwind;integrated security=false;user id=sa;password=xxx;

but the string that does not work is:

server=WS1;database=northwind;integrated security=SSPI;

which is the string I would like to use for normal web access. This string works fine on my development system (where I use XP Pro and IIS 5.1)

In IIS6 on the "production server" the directory security on the virtual dir is set to allow anonymous access, using user IUSR_WS1 (where WS1 is the name of the system) and to integrated security.

Please help! Thank you

John BI forgot to say the error message I am getting is:

login failed for user 'NTAUTHORITY\NETWORK SERVICE'|||There is a KB for this problem:PRB: "Login Failed" Error Message When You Create a Trusted Data Connection from ASP.NET to SQL Server. See if any of the 3 suggested Resolutions work for you.

To me, the 3rd suggestion seems to be the best course of action. And taking that further, what seems to make the most sense is to add a new database role called "webuser" or something similar, and then add the NT AUTHORITY\NETWORK SERVICE user to that role. This will give you more flexibility if the web app moves to a Windows 2000 machine -- you would just be able to add the ASPNET account as another member of that webuser role.

Terri|||Thank you for your reply. I looked at the article, but I regret to say it does not make much sense to me at this stage. I have bought the MSDE Admin tool to administer MSDE, or could use the osql tool, but am not clear how to:

a. add a new database role (is this adding a "normal" user group)? I dont see any reference to a "database role".

b. add the NTAUTHORITY\NETWORK SERVICE user to that role. I have looked at the list of users and there is no such name. I must be looking in the wrong place.

Excuse my ignorance!

TIA

John B|||You should downloadSQL Server 2000 Books Online. This is a huge download but an essential reference.

I have to admit, I am confused on this issue. I have now come across an article right on this siteRunning ASP.NET 1.1 with IIS 6.0, and part of it covers supporting integrated authentication with SQL Server. The suggestion I gave you was based on something I read elsewhere that seemed to make sense.

Further information on the path I suggested:

The system stored procedure to add a database role is sp_addrole. You'd use it like this:

EXEC sp_addrole 'webuser'

The system stored procedure to add a security account for a Windows user to the current database and enable it to be granted permissions to perform activities in the database is sp_grantdbaccess.

EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK SERVICE', 'Network Service'

The system stored procedure to add a security account as a member of an existing database role in the current database is sp_addrolemember.

EXEC sp_addrolemember 'webuser', 'Network Service'

Terri|||Thank you. The article you suggested in the last post is very helpful. I have now solved the problem, thanks to an article I found www.cgnit.com/resources/ntauthority_networkservice_error.html

which hits it bang on the nose, and may be useful to others.

It seems to me that all the books, and many of the forums suggest that when you run an ASP.NET app and use anonymous access, the system uses the identity mcxxx\aspnet (where mcxxx is the domain or machine no). But what I have found so far is that under Server 2003, the identity assumed is the mysterious user NTAUTHORITY\NETWORKSERVICE which is NOT found in the list of users, but is apparently a member of the IIS_WPG group, so configuring this group to access the database solves the problem and allows an anonymous user to access records according to the permissions set within MSDE or SQL Server.

Can anyone confirm this is true? Is the ASPNET user in fact NEVER used in Server 2003, but only in W2000 or XP?|||Yes, I can confirm that. I ran into this today, setting up ibuyspy on a Windows2003 server. Here's the quote I found in the machine.config file:
When ASP.NET is running under IIS 6 in native mode, the IIS 6 process model is
used and settings in this section are ignored. Please use the IIS administrative
UI to configure things like process identity and cycling for the IIS
worker process for the desired application

I went ahead and added the IIS_WPG to access the DB I cared about, but you could also setup your own IIS6 AppPool with seperate identity information.

/Brad|||

I cannot but say, its a great thread !!

regards

Connecting to MSDE Thru VB Without Machine Name

In order to avoid having to know the machine name, I am thinking about
using the following VB code to connect to an instance of MSDE.
It enumerates all possible SQL Servers and if it finds one with
my instance name string, it uses the string to connect.
I believe it was Andrea who showed me the SQLDMO stuff ...
The code does work on my machine - I am just wondering if it is a
good strategy when deploying the app. to a wide audience.
The installation of MSDE will always install an instance of "SQLINSTEQU".
Public Sub Init_App()
'
' First check that database is running.
'
Dim i As Integer
Dim oNames As SQLDMO.NameList
Dim oSQLApp As SQLDMO.Application
Dim Sqlserver_Running As String
Dim msgtext As String
Set oSQLApp = New SQLDMO.Application
Dim ws_Server_Str As String
Dim str_Pos As Integer
Dim ws_EquServer_Str As String
Set oNames = oSQLApp.ListAvailableSQLServers()
Sqlserver_Running = "NO"
'
' Search all available SQL Servers for a \\ServerName\InstanceName
' that has SQLINSTEQU as the instance name. If found, use the whole
' \\ServerName\InstanceName string to connect to the database.
' Hopefully this will work and then do not have to worry about machine
name.
'
For i = 1 To oNames.Count
ws_Server_Str = oNames(i)
strPos = InStr(ws_Server_Str, "SQLINSTEQU")
If strPos > 0 Then
ws_EquServer_Str = ws_Server_Str
Sqlserver_Running = "YES"
Exit For
End If
Next i
If Sqlserver_Running = "NO" Then
msgtext = "The database is not running. Please start your" & _
vbCr & "database and then re-start the application."
MsgBox msgtext
Set oSQLApp = Nothing
Set oNames = Nothing
End
End If
Set oSQLApp = Nothing
Set oNames = Nothing
'
' Establish a connection with the database using the OLE DB provider
' for SQL Server (SQLOLEDB). This provider does not need a data source
' or an existing ODBC driver. It is a native driver for MS SqlServer.
'
cn.ConnectionString = "PROVIDER=SQLOLEDB" & _
";SERVER=" & ws_EquServer_Str & _
";UID=sa" & _
";PWD=abcdefg" & _
";DATABASE=Equ"
cn.Open
End Sub
Paul,
Unfortunately, in practice, the enumeration of SQL Servers is not reliable. I believe that Gert has some
technical elaborations about this on www.sqldev.net, please check that out before decoding on this strategy.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message news:OC7DHeZIEHA.3820@.tk2msftngp13.phx.gbl...
> In order to avoid having to know the machine name, I am thinking about
> using the following VB code to connect to an instance of MSDE.
> It enumerates all possible SQL Servers and if it finds one with
> my instance name string, it uses the string to connect.
> I believe it was Andrea who showed me the SQLDMO stuff ...
> The code does work on my machine - I am just wondering if it is a
> good strategy when deploying the app. to a wide audience.
> The installation of MSDE will always install an instance of "SQLINSTEQU".
>
> Public Sub Init_App()
> '
> ' First check that database is running.
> '
> Dim i As Integer
> Dim oNames As SQLDMO.NameList
> Dim oSQLApp As SQLDMO.Application
> Dim Sqlserver_Running As String
> Dim msgtext As String
> Set oSQLApp = New SQLDMO.Application
> Dim ws_Server_Str As String
> Dim str_Pos As Integer
> Dim ws_EquServer_Str As String
>
> Set oNames = oSQLApp.ListAvailableSQLServers()
> Sqlserver_Running = "NO"
> '
> ' Search all available SQL Servers for a \\ServerName\InstanceName
> ' that has SQLINSTEQU as the instance name. If found, use the whole
> ' \\ServerName\InstanceName string to connect to the database.
> ' Hopefully this will work and then do not have to worry about machine
> name.
> '
> For i = 1 To oNames.Count
> ws_Server_Str = oNames(i)
> strPos = InStr(ws_Server_Str, "SQLINSTEQU")
> If strPos > 0 Then
> ws_EquServer_Str = ws_Server_Str
> Sqlserver_Running = "YES"
> Exit For
> End If
> Next i
>
> If Sqlserver_Running = "NO" Then
> msgtext = "The database is not running. Please start your" & _
> vbCr & "database and then re-start the application."
> MsgBox msgtext
> Set oSQLApp = Nothing
> Set oNames = Nothing
> End
> End If
> Set oSQLApp = Nothing
> Set oNames = Nothing
> '
> ' Establish a connection with the database using the OLE DB provider
> ' for SQL Server (SQLOLEDB). This provider does not need a data source
> ' or an existing ODBC driver. It is a native driver for MS SqlServer.
> '
>
> cn.ConnectionString = "PROVIDER=SQLOLEDB" & _
> ";SERVER=" & ws_EquServer_Str & _
> ";UID=sa" & _
> ";PWD=abcdefg" & _
> ";DATABASE=Equ"
>
> cn.Open
> End Sub
>
|||I searched that site you mentioned and could find nothing that said this
method was unreliable. On the contrary, I found an example that did just
that which can be found here:
http://www.sqldev.net/sqldmo/SamplesVB6.htm
I would appreciate it if you could back up your response with a link.
Thanks anyways ...
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uB1$x7ZIEHA.720@.TK2MSFTNGP10.phx.gbl...
> Paul,
> Unfortunately, in practice, the enumeration of SQL Servers is not
reliable. I believe that Gert has some
> technical elaborations about this on www.sqldev.net, please check that out
before decoding on this strategy.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message
news:OC7DHeZIEHA.3820@.tk2msftngp13.phx.gbl...[color=darkblue]
"SQLINSTEQU".
>
|||I phrased it "in practice", but perhaps should have quoted the word "reliable" as well. Anyhow, check out
below:
http://www.sqldev.net/misc/OleDbEnum.htm
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message news:OXBvaHaIEHA.3144@.TK2MSFTNGP10.phx.gbl...
> I searched that site you mentioned and could find nothing that said this
> method was unreliable. On the contrary, I found an example that did just
> that which can be found here:
> http://www.sqldev.net/sqldmo/SamplesVB6.htm
> I would appreciate it if you could back up your response with a link.
> Thanks anyways ...
> Paul
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:uB1$x7ZIEHA.720@.TK2MSFTNGP10.phx.gbl...
> reliable. I believe that Gert has some
> before decoding on this strategy.
> news:OC7DHeZIEHA.3820@.tk2msftngp13.phx.gbl...
> "SQLINSTEQU".
>
|||Tibor:
That is NOT the method I proposed.
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23zGcXSaIEHA.828@.TK2MSFTNGP12.phx.gbl...
> I phrased it "in practice", but perhaps should have quoted the word
"reliable" as well. Anyhow, check out
> below:
> http://www.sqldev.net/misc/OleDbEnum.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message
news:OXBvaHaIEHA.3144@.TK2MSFTNGP10.phx.gbl...[color=darkblue]
in[color=darkblue]
out[color=darkblue]
about[color=darkblue]
whole[color=darkblue]
machine[color=darkblue]
source[color=darkblue]
SqlServer.
>
|||If you read the DMO documentation, you will see that the DMO ListAvailableSevers method uses the ODBC
SQLBrowseConnect function, which means that the weaknesses that this function has is also in the DMO method.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message news:uBvSUyaIEHA.3508@.TK2MSFTNGP09.phx.gbl...
> Tibor:
> That is NOT the method I proposed.
> Paul
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23zGcXSaIEHA.828@.TK2MSFTNGP12.phx.gbl...
> "reliable" as well. Anyhow, check out
> news:OXBvaHaIEHA.3144@.TK2MSFTNGP10.phx.gbl...
> in
> out
> about
> whole
> machine
> source
> SqlServer.
>
|||Hi Paul,
Believe Tibor on this one. He's dead right.
Even with the new enumeration options shown in the PDC release of Whidbey,
I've seen similar problems. Under the covers, most of these functions rely
on collecting browser packets.
Many of these "browse" type functions take ages to work on the network. Even
common browsing functions can take up to 24 minutes to settle to a stable
state. So, sometimes, they'll work, sometimes they won't.
Even searching for instances on the local system currently involves
searching the registry and making allowances for the different registry
structures created by different versions.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message
news:OXBvaHaIEHA.3144@.TK2MSFTNGP10.phx.gbl...
> I searched that site you mentioned and could find nothing that said this
> method was unreliable. On the contrary, I found an example that did just
> that which can be found here:
> http://www.sqldev.net/sqldmo/SamplesVB6.htm
> I would appreciate it if you could back up your response with a link.
> Thanks anyways ...
> Paul
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in[vbcol=seagreen]
> message news:uB1$x7ZIEHA.720@.TK2MSFTNGP10.phx.gbl...
> reliable. I believe that Gert has some
out[vbcol=seagreen]
> before decoding on this strategy.
> news:OC7DHeZIEHA.3820@.tk2msftngp13.phx.gbl...
> "SQLINSTEQU".
machine
>
|||hi Paul,
"Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
news:uBvSUyaIEHA.3508@.TK2MSFTNGP09.phx.gbl...
> Tibor:
>...
yep... Tibor is right... you always have to believe him =;-D
ListAvailableServer uses ODBC function SQLBrowseConnect() provided by ODBC
libraries installed by Mdac;
this is a mechanism working in broadcast calls, which result never are
conclusive and consistent, becouse results are influenced of various
servers's answer states, answer time, etc.
Until Mdac 2.5, SQLBrowseConnect function works based on a NetBIOS
broadcast, on which SQL Servers respond (Default protocol for SQL Server
7.0), while in SQL Server 2000 the rules changed, because the default client
protocol changed to TCP/IP and now a UDP broadcast is used, beside a NetBIOS
broadcast, listening on port 1434: which is using a UDP broadcast on port
1434, if instance do not listen or not respond on time they will not be part
of the enumeration.
Some basic rules for 7.0 are:
- SQL Servers have to be running on Windows NT or Windows 2000 and have to
listen on Named Pipes, that is why in 7.0 Windows 9x SQL Servers will never
show up, because they do not listen on Named Pipes.
- The SQL Server has to be running in order to respond on the broadcast.
There is a gray window of 15 minutes after shutdown, where a browse master
in the domain may respond on the broadcast and answer.
- If you have routers in your network, that do not pass on NetBIOS
broadcasts, this might limit your scope of the broadcast.
- Only servers within the same NT domain (or trust) will get enumerated.
In SQL Server 2000 using MDAC 2.6 this changes a little, because now the
default protocol has been changed to be TCP/IP sockets and instead of a
NetBIOS broadcast, they use a TCP UDP to detect the servers. The same logic
still applies roughly.
- SQL Server that are running
- SQL Server that listening on TCP/IP
- Running on Windows NT or Windows 2000 or Windows 9x
- If you use routers and these are configured not to pass UDP broadcasts,
only machines within the same subnet show up.
Upgrading to Service Pack 2 of SQL Server 2000 is required in order to have
..ListAvailableServer method to work properly, becouse preceding release of
Sql-DMO Components of Sql Server 2000 present a bug in this area.
Courtesy of Mr. Gert E.R. Drapers
further Information at
http://sqldev.net/misc.htm
The Service Pack 3a introduced some new amenity in order to prevent MSDE
2000 to be hit by Internet worms like Slammer and Saphire virus and to
increase security, so that Microsoft decided to default for disabling
SuperSockets Network Protocols on new MSDE 2000 installation.
Instances of SQL Server 2000 SP3a or MSDE 2000 SP3a will stop listening on
UDP port 1434 when they are configured to not listen on any network
protocols. This will stop enlisting these servers.
the next generation troubles will depend on WinXP service pack 2, which will
default to close all ports on the internal firewall...
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Paul,
"Paul McTeigue" <paul_mcteigue@.msn.com> ha scritto nel messaggio
news:%23PePoymIEHA.2480@.tk2msftngp13.phx.gbl...
> Okay - I give - I will not use that method. The whole point was to avoid
> having to know
> the machine name - how do you guys solve this problem?
if you have to, you can resort on SQLBrowseConnect() provided by ODBC if you
do not need max precision, or give a try to the other methods like
NetServerEnum as described in http://sqldev.net/misc.htm
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||
> if you have to, you can resort on SQLBrowseConnect() provided by ODBC if
you
> do not need max precision, or give a try to the other methods like
> NetServerEnum as described in http://sqldev.net/misc.htm
> hth
Hi all
Interesting conversation, I have been reading about this lately and from
what I have read the NetServerEnum API function also has the same problem.
You must try to connect using NetQueryDisplayInformation to ensure you get
around the latency issue with the network browser.
Maybe there is no totally reliable / robust method to do this...
Regards
Daryl

connecting to MSDE on Windows 2003 SBS Server

I have an application (Point of Sale System) that utilizes a MSDE
database. The server came loaded with MSDE instances already and I
installed one for the POS System. The client PCs can see the other 3
MSDE instances, but cannot see the one I installed. Any ideas on how
the new instance can appear on the network. The new instance was not
named. The other three were named instances of MSDE.
hi,
auschnet@.gmail.com wrote:
> I have an application (Point of Sale System) that utilizes a MSDE
> database. The server came loaded with MSDE instances already and I
> installed one for the POS System. The client PCs can see the other 3
> MSDE instances, but cannot see the one I installed. Any ideas on how
> the new instance can appear on the network. The new instance was not
> named. The other three were named instances of MSDE.
please verify the required/desired network protocols are enabled... MSDE
installs by default disabling them and you can override this behavior
providing the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe boostrap installer, or later, at run time, using
the Server Network Utility (svrnetcn.exe) and enabling the preferred network
protocol..
additionally, WinXP sp2 ships with a built-in Firewall that's enabled by
default, preventing network connections to... if this is a case, you have to
specify an exception for the service or for the MSDE used port, usually
specifying a subnet or individual remot IP addreses to restrict
connections...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Connecting to MSDE named instance

If we install MSDE 2000 SP3a with out a named instance we can connect to
through OSQL from a different computer on the network.
We used SVRNETCN.EXE to add TCP/IP to the protocol list.
We changed the port from 1059 or something like that to 1433.
We changed "LoginMode" to 2, but we also tried it with 0
But when we try to connect via OSQL
osql -S ROBXP\RR -U sa -P 11111
we get the following error.
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
the same OSQL command works OK from the local computer.
If we re-install with out a named instance we can connect fine with OSQL
Any ideas?
-Rob
PS. it was installed with the following:
setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
Check your MDAC version on the client you're trying to connect from. Upgrade
to the latest version and try it again.
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"rob" wrote:

> If we install MSDE 2000 SP3a with out a named instance we can connect to
> through OSQL from a different computer on the network.
> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
> We changed "LoginMode" to 2, but we also tried it with 0
> But when we try to connect via OSQL
> osql -S ROBXP\RR -U sa -P 11111
> we get the following error.
>
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
> the same OSQL command works OK from the local computer.
>
> If we re-install with out a named instance we can connect fine with OSQL
> Any ideas?
> -Rob
> PS. it was installed with the following:
> setup SAPWD=11111 DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RR
>
>
|||I ran Componet Checker 2.0 and it indidcates I have MDAC 2.8 SP1 which looks
to be the latest version.
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:86C87062-5A4C-4962-8FB3-99BA9CA2F375@.microsoft.com...
> Check your MDAC version on the client you're trying to connect from.
> Upgrade
> to the latest version and try it again.
|||hi,
rob wrote:

> We used SVRNETCN.EXE to add TCP/IP to the protocol list.
> We changed the port from 1059 or something like that to 1433.
usually 1433 is for default instances, where other port numbers indicates
named instances...
specifying a fixed port and not using the dynamic assigned port (wiche
requires on the server the UDP 1434 port to be available out of eventual
firewall) you have to specify an alias via Client Network Utility
(cliconfg.exe) on each remote client...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||THANKS it works.
For anyone else reading this thread in the future.
You give it an alias name (RR for example) and and the servername is the
servername\instance
you can test the connection by using the alias name:
osql -S RR -U sa -Pxxxxx
thanks again.
.....
I have done some more testing. The only thing I am concerned about is:
After my program and MSDE is installed on someones computer, if they want to
access it from a different computer they will need to know how to create
exceptions in the WindowsXP firewall.
They will need to open up UPD 1434 and TCP port XXXX where XXXX is whatever
random port is used during installation of MSDE. I can find that port in
the registry and tell them at install time. But my users are not always
very proficient at using computers, and could have a hard time opening up
ports in the firewall.
If anyone has any suggestions about making this easier I would love to hear
about it.
-Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qfs6cFe280bU1@.individual.net...
> hi,
> rob wrote:
>
> usually 1433 is for default instances, where other port numbers indicates
> named instances...
> specifying a fixed port and not using the dynamic assigned port (wiche
> requires on the server the UDP 1434 port to be available out of eventual
> firewall) you have to specify an alias via Client Network Utility
> (cliconfg.exe) on each remote client...
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Rob,
rob wrote:
> ....
> I have done some more testing. The only thing I am concerned about
> is: After my program and MSDE is installed on someones computer, if
> they want to access it from a different computer they will need to
> know how to create exceptions in the WindowsXP firewall.
> They will need to open up UPD 1434 and TCP port XXXX where XXXX is
> whatever random port is used during installation of MSDE. I can find
> that port in the registry and tell them at install time. But my
> users are not always very proficient at using computers, and could
> have a hard time opening up ports in the firewall.
> If anyone has any suggestions about making this easier I would love
> to hear about it.
>
actually you can provide the script available at
http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
ports" :D
try having a look at it if can helps..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Wow, that will make it easier. I was dreading having to give instructions to
open the firewall. ; )
I don't want to bother you, but I have one more question.
Your advice did work, and I can connect to the newly installed instance, -
IF I set up an alias.
BUT,
I have one computer that I installed with an instance that I do NOT have to
set up an alias for to connect remotely. I can not see what is different
for this computer. I even printed out the MSSQL registry settings for the
two computers and could not see a difference (besides uptime, etc.)
Even though your suggestion works, it would be much easier if I did not have
to set up an alias on the clients. Do you have any ideas what I did
differently with the one that works with out an alias?
Thanks,
Rob
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qhp0hFem400U1@.individual.net...
> hi Rob,
> actually you can provide the script available at
> http://support.microsoft.com/kb/839980/en-us to provide an "automatic open
> ports" :D
> try having a look at it if can helps..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||I downloaded your program DBMgr2 and was able to connect to my DB without
using an alias. The difference was (from your help file) to use servername =
ROBXP\RR,1433
explicitly name the port number. This works via osql also.
The difference remains that I have one computer that I do not need to know
what the port number is, or set up an alias.
"rob" <ryost@..no.spam.rentright.com> wrote in message
news:OqGjGPbyFHA.2924@.TK2MSFTNGP15.phx.gbl...
> Wow, that will make it easier. I was dreading having to give instructions
> to open the firewall. ; )
> I don't want to bother you, but I have one more question.
> Your advice did work, and I can connect to the newly installed instance, -
> IF I set up an alias.
> BUT,
> I have one computer that I installed with an instance that I do NOT have
> to set up an alias for to connect remotely. I can not see what is
> different for this computer. I even printed out the MSSQL registry
> settings for the two computers and could not see a difference (besides
> uptime, etc.)
> Even though your suggestion works, it would be much easier if I did not
> have to set up an alias on the clients. Do you have any ideas what I did
> differently with the one that works with out an alias?
> Thanks,
> Rob
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:3qhp0hFem400U1@.individual.net...
>
|||hi Rob,
rob wrote:
> I downloaded your program DBMgr2 and was able to connect to my DB
> without using an alias. The difference was (from your help file) to
> use servername = ROBXP\RR,1433
> explicitly name the port number. This works via osql also.
> The difference remains that I have one computer that I do not need to
> know what the port number is, or set up an alias.
probably it's not a named instance but a default one, that's to say ROBXP
and not ROBXP\RR..
default instances automatically listen on TCP 1433 as this port is the one
Microsoft reserved on IANA for SQL Server...
try having a look at it..
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I am pretty sure it is a named instance. I connected to it through your
Dbamgr2k by specifing
MICHELLEP\MICHELLE
I did not have to give it port 1433 (which is its port)
I did set this server up several months ago, and do not remember exactly how
I did it.
Also, when I go to add remove programs it is listed as:
Microsoft SQL Server Desktop Engine (MICHELLE)
and I think the instance name is listed in the paren's
From SQLPing:
C:\>sqlping 192.168.0.88
SQL-Pinging 192.168.0.88
Listening...
ServerName:MICHELLEP
InstanceName:MICHELLE
IsClustered:No
Version:8.00.194
tcp:1433
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3qieavFf286oU1@.individual.net...
> probably it's not a named instance but a default one, that's to say ROBXP
> and not ROBXP\RR..
> default instances automatically listen on TCP 1433 as this port is the one
> Microsoft reserved on IANA for SQL Server...
> try having a look at it..
> --
> Andrea Montanari
> http://www.asql.biz/DbaMgr.shtm
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Connecting to MSDE from client

We are using MSDE as a cheap datastore in our client/server app. MSDE is installed only on the server and both the server and the clients connect to it from their machines.

When we deploy on Windows XP, we see that our code running on the server can access MSDE, but our code running on a client machine cannot connect to MSDE.

The clients are able to connect on Windows 2000 ... can anyone help me understand this ?

Thanks in advance,

ethan

MSDE only allow local access.

Connecting to MSDE 2000 over a home network

Hi,

I'm trying to connect to an instance of MSDE 2000 from Visual Studio 2005 over a home network. Although I know how to connect to a database from Visual Studio, I'm pretty clueless about configuring Sql Server to allow the connection (I can connect with no problem when I do so from the same computer). Also, with experimenting I've created a bunch of instances of Sql Server that I don't really need and am not sure how to get rid of them. Thanks in advance for any help.

-Dave

I don't know if this will help, but I've already tried enabling all of the network protocols in the instance. Also, I can easily connect to an Access database over the network.

You may want to start here:

http://msdn2.microsoft.com/en-us/library/ms190944.aspx

Buck Woody

Connecting to MSDE 2000 over a home network

Hi,

I'm trying to connect to an instance of MSDE 2000 from Visual Studio 2005 over a home network. Although I know how to connect to a database from Visual Studio, I'm pretty clueless about configuring Sql Server to allow the connection (I can connect with no problem when I do so from the same computer). Also, with experimenting I've created a bunch of instances of Sql Server that I don't really need and am not sure how to get rid of them. Thanks in advance for any help.

-Dave

I don't know if this will help, but I've already tried enabling all of the network protocols in the instance. Also, I can easily connect to an Access database over the network.

You may want to start here:

http://msdn2.microsoft.com/en-us/library/ms190944.aspx

Buck Woody

connecting to MSDE

I installed MSDE 200 on my machine running XP home
edition.
I cant connect to the db using the SQL mode, but i can
connect using the in windows modes. It returns and odbc
error stae 28000 , i dont know how to correct this.
If set up and odbc connection and try to test this, it
returns the following errore
Attempting connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection.It looks like your MSDE instance is configured for Windows
Authentication only. The following article explains how to
change the authentication mode for MSDE during installation
as well as after installation:
INF: How to Change the Default Login Authentication Mode to
SQL While Installing SQL Server 2000 Desktop Engine by Using
Windows Installer
http://support.microsoft.com/?id=285097
-Sue
On Wed, 25 Feb 2004 19:31:09 -0800, "Lanre"
<lanre_makinde@.yahoo.com_remove.this> wrote:

>I installed MSDE 200 on my machine running XP home
>edition.
>I cant connect to the db using the SQL mode, but i can
>connect using the in windows modes. It returns and odbc
>error stae 28000 , i dont know how to correct this.
>If set up and odbc connection and try to test this, it
>returns the following errore
>Attempting connection
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>failed for user 'sa'. Reason: Not associated with a
>trusted SQL Server connection.

Connecting to MSDE

I am trying to connect to a MSDE database on server from my desktop using query analyzer. I keep getting the generic "SQL Server does not exist or access denied'

I have verified the following:
- the login/password is valid because when I access osql from server I can gain access
- the registry for Loginmode appears OK - set to 2 - mixed mode

What else do I need to check...

Thanks, kgaskeDid MSDE install as a named instance? Check the service, and see if it is listed as MSSQL$foo. If it is, you connect as servername\foo.|||No MSDE is not a named instance. Checked the service..|||Can you connect to the server from the server? Maybe no network protocols were enabled.|||Can you connect to the server from the server? Maybe no network protocols were enabled.

I'll second this; what version of MSDE is it? What's the operating system. By default, MSDE 2000 installed on WXP or Win2003 will not enable IP connections. You have to install SP3 (minimum) or SP4. I also recall (from some dim memory) that by default, MSDE does not enable anything but shared memory (ie, localhost) connections.

Regards,

hmscott

Connecting to MSDE

Being new to the SQL server world I have a beginner question.

How do I grant access to database from a networked computer?
I have tried:
sp_grantlogin '\\computername\username'
and I get the error:
Windows NT or user <above> not found. Please check name.

Any help would be appreciated.
Thanks
EricEric Borden (borden_eric@.invalid.com) writes:
> Being new to the SQL server world I have a beginner question.
> How do I grant access to database from a networked computer?
> I have tried:
> sp_grantlogin '\\computername\username'
> and I get the error:
> Windows NT or user <above> not found. Please check name.

This not really my area, but I believe that SQL Server needs to be
able to verify that the user exists. If the user is in the same domain
as SQL Server this is trivial. But if all you have a workgroup, and
not a domain, things are getting difficult. In this case, SQL authentication
may be required.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp