Instance Name Not Visible.

I have laptops that require the loopback adapter when they are not
connected. However when they connect back to the network the networked
servers display just the computer name not the / instancename. Any
ideas? It only happens on network instances. The local instances are
correct. This happens in Enterprise Manager, Access connection tool
and using SQL-DMO.
Gary Shane Lim
hi Gary,
Shane Lim wrote:
> I have laptops that require the loopback adapter when they are not
> connected. However when they connect back to the network the networked
> servers display just the computer name not the / instancename. Any
> ideas? It only happens on network instances. The local instances are
> correct. This happens in Enterprise Manager, Access connection tool
> and using SQL-DMO.
> Gary Shane Lim
are the laptops instances "named instances" or "default instances"?
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
|||They are all names instances.
On Fri, 18 Mar 2005 11:57:13 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

>hi Gary,
>Shane Lim wrote:
>are the laptops instances "named instances" or "default instances"?

Installing Sql Server and Visual Basic .NET

Browsing the Sql server installation cd I found that I need to create a
domain name. What will be the difference with WORKGROUP network? Do I need to
change from workgroup to domain name?> Browsing the Sql server installation cd I found that I need to create a
> domain name.
? Could you be more specific? Where did you "find" this?|||Urraca wrote:
> Browsing the Sql server installation cd I found that I need to create
> a domain name. What will be the difference with WORKGROUP network? Do
> I need to change from workgroup to domain name?
No. A workgroup is fine for SQL Server installation.
--
David Gugick
Imceda Software
www.imceda.com|||You may want to search for "Authentication Modes" in BOL for a
discussion of how authentication can be configured in SQL Server.
Joe Webb
SQL Server MVP
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)
On Wed, 4 May 2005 09:10:10 -0700, Urraca
<chiriqui9844(removethis)@.msn.com> wrote:
>Browsing the Sql server installation cd I found that I need to create a
>domain name. What will be the difference with WORKGROUP network? Do I need to
>change from workgroup to domain name?

Installing Sql Server and Visual Basic .NET

Browsing the Sql server installation cd I found that I need to create a
domain name. What will be the difference with WORKGROUP network? Do I need to
change from workgroup to domain name?
> Browsing the Sql server installation cd I found that I need to create a
> domain name.
? Could you be more specific? Where did you "find" this?
|||Urraca wrote:
> Browsing the Sql server installation cd I found that I need to create
> a domain name. What will be the difference with WORKGROUP network? Do
> I need to change from workgroup to domain name?
No. A workgroup is fine for SQL Server installation.
David Gugick
Imceda Software
www.imceda.com
|||You may want to search for "Authentication Modes" in BOL for a
discussion of how authentication can be configured in SQL Server.
Joe Webb
SQL Server MVP
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg...l/-/0972688811
I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)
On Wed, 4 May 2005 09:10:10 -0700, Urraca
<chiriqui9844(removethis)@.msn.com> wrote:

>Browsing the Sql server installation cd I found that I need to create a
>domain name. What will be the difference with WORKGROUP network? Do I need to
>change from workgroup to domain name?

Installing Sql Server and Visual Basic .NET

Browsing the Sql server installation cd I found that I need to create a
domain name. What will be the difference with WORKGROUP network? Do I need t
o
change from workgroup to domain name?> Browsing the Sql server installation cd I found that I need to create a
> domain name.
? Could you be more specific? Where did you "find" this?|||Urraca wrote:
> Browsing the Sql server installation cd I found that I need to create
> a domain name. What will be the difference with WORKGROUP network? Do
> I need to change from workgroup to domain name?
No. A workgroup is fine for SQL Server installation.
David Gugick
Imceda Software
www.imceda.com|||You may want to search for "Authentication Modes" in BOL for a
discussion of how authentication can be configured in SQL Server.
Joe Webb
SQL Server MVP
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/t...il/-/0972688811
I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)
On Wed, 4 May 2005 09:10:10 -0700, Urraca
<chiriqui9844(removethis)@.msn.com> wrote:

>Browsing the Sql server installation cd I found that I need to create a
>domain name. What will be the difference with WORKGROUP network? Do I need
to
>change from workgroup to domain name?sql

Integrated Security

We have SS 2000 and SSRS 2000. SSRS is connecting as a Windows account of "NT
Authority\Network Service". That account is in both RSEXEC roles in
ReportServer and ReportServerTempDB. When we log into the Report Server
website as a domain name (which on the server has admin rights), it works
fine. When we log into ReportServer using SQL Authentication using a testname
that is on the server, we get the home page with no access to our folder. We
added that id to SQL, we have added that user to RS with full access, we have
tried even adding that to the RSEXEC. No change. We also checked IIS for the
Report folder and it is using Windows Integrated Security. One more thing,
the dataset is using the aspnet login. When we make the person an
administrator on the server - it works fine. Of course that options is not
feasible. Any ideas of what we missed?You are confusing two different things. First, who the user is and what the
credentials to retrieve the data for the report are.
This is completely two different things (although they can be the same).
When you go to the website it is using the integrated windows security that
identifies who the user is that is on the computer which is accessing
Reporting Services. This has nothing whatsoever to do with SQL
Authentication. That is strictly for credentials of the data source.
My suggestion is this. First read up on roles. Roles are used to give access
to the folders, reports, reporting functionality like deploying reports and
subscriptions. Plan how you want to organize and give access. What I do
because it is easiest for me, I create a local group that I add individual
domain users and domain groups to. Then I give this group role membership in
Reporting Services.
Next I run SQL Server in mixed mode security (which I think you are already
doing). I setup a login that is a read only login. I use that for the
credentials of the data source. This buys you performance as well. It allows
connection pooling to work its magic.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mgcap" <mgcap@.discussions.microsoft.com> wrote in message
news:93178514-7883-493F-8A18-83614CD56EF5@.microsoft.com...
> We have SS 2000 and SSRS 2000. SSRS is connecting as a Windows account of
> "NT
> Authority\Network Service". That account is in both RSEXEC roles in
> ReportServer and ReportServerTempDB. When we log into the Report Server
> website as a domain name (which on the server has admin rights), it works
> fine. When we log into ReportServer using SQL Authentication using a
> testname
> that is on the server, we get the home page with no access to our folder.
> We
> added that id to SQL, we have added that user to RS with full access, we
> have
> tried even adding that to the RSEXEC. No change. We also checked IIS for
> the
> Report folder and it is using Windows Integrated Security. One more thing,
> the dataset is using the aspnet login. When we make the person an
> administrator on the server - it works fine. Of course that options is not
> feasible. Any ideas of what we missed?|||Bruce, Thanks. That did clear up what we were stumbling with. We did get it
fixed this morning - we had not given security to the home folder. But I
still have one more question for you. We do understand a bit about the roles
(but are still learning) but when you talk about the groups are you talking
about a Windows group on the server or something else?
"Bruce L-C [MVP]" wrote:
> You are confusing two different things. First, who the user is and what the
> credentials to retrieve the data for the report are.
> This is completely two different things (although they can be the same).
> When you go to the website it is using the integrated windows security that
> identifies who the user is that is on the computer which is accessing
> Reporting Services. This has nothing whatsoever to do with SQL
> Authentication. That is strictly for credentials of the data source.
> My suggestion is this. First read up on roles. Roles are used to give access
> to the folders, reports, reporting functionality like deploying reports and
> subscriptions. Plan how you want to organize and give access. What I do
> because it is easiest for me, I create a local group that I add individual
> domain users and domain groups to. Then I give this group role membership in
> Reporting Services.
> Next I run SQL Server in mixed mode security (which I think you are already
> doing). I setup a login that is a read only login. I use that for the
> credentials of the data source. This buys you performance as well. It allows
> connection pooling to work its magic.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "mgcap" <mgcap@.discussions.microsoft.com> wrote in message
> news:93178514-7883-493F-8A18-83614CD56EF5@.microsoft.com...
> > We have SS 2000 and SSRS 2000. SSRS is connecting as a Windows account of
> > "NT
> > Authority\Network Service". That account is in both RSEXEC roles in
> > ReportServer and ReportServerTempDB. When we log into the Report Server
> > website as a domain name (which on the server has admin rights), it works
> > fine. When we log into ReportServer using SQL Authentication using a
> > testname
> > that is on the server, we get the home page with no access to our folder.
> > We
> > added that id to SQL, we have added that user to RS with full access, we
> > have
> > tried even adding that to the RSEXEC. No change. We also checked IIS for
> > the
> > Report folder and it is using Windows Integrated Security. One more thing,
> > the dataset is using the aspnet login. When we make the person an
> > administrator on the server - it works fine. Of course that options is not
> > feasible. Any ideas of what we missed?
>
>|||I am talking about a local Windows group. In my case I found it easier to
assign all the different domain groups to a local windows group and then use
that when I was assigning rights in Reporting Services.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mgcap" <mgcap@.discussions.microsoft.com> wrote in message
news:D1544B76-99F8-43CD-85F8-9156FBCC6C39@.microsoft.com...
> Bruce, Thanks. That did clear up what we were stumbling with. We did get
> it
> fixed this morning - we had not given security to the home folder. But I
> still have one more question for you. We do understand a bit about the
> roles
> (but are still learning) but when you talk about the groups are you
> talking
> about a Windows group on the server or something else?
> "Bruce L-C [MVP]" wrote:
>> You are confusing two different things. First, who the user is and what
>> the
>> credentials to retrieve the data for the report are.
>> This is completely two different things (although they can be the same).
>> When you go to the website it is using the integrated windows security
>> that
>> identifies who the user is that is on the computer which is accessing
>> Reporting Services. This has nothing whatsoever to do with SQL
>> Authentication. That is strictly for credentials of the data source.
>> My suggestion is this. First read up on roles. Roles are used to give
>> access
>> to the folders, reports, reporting functionality like deploying reports
>> and
>> subscriptions. Plan how you want to organize and give access. What I do
>> because it is easiest for me, I create a local group that I add
>> individual
>> domain users and domain groups to. Then I give this group role membership
>> in
>> Reporting Services.
>> Next I run SQL Server in mixed mode security (which I think you are
>> already
>> doing). I setup a login that is a read only login. I use that for the
>> credentials of the data source. This buys you performance as well. It
>> allows
>> connection pooling to work its magic.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "mgcap" <mgcap@.discussions.microsoft.com> wrote in message
>> news:93178514-7883-493F-8A18-83614CD56EF5@.microsoft.com...
>> > We have SS 2000 and SSRS 2000. SSRS is connecting as a Windows account
>> > of
>> > "NT
>> > Authority\Network Service". That account is in both RSEXEC roles in
>> > ReportServer and ReportServerTempDB. When we log into the Report Server
>> > website as a domain name (which on the server has admin rights), it
>> > works
>> > fine. When we log into ReportServer using SQL Authentication using a
>> > testname
>> > that is on the server, we get the home page with no access to our
>> > folder.
>> > We
>> > added that id to SQL, we have added that user to RS with full access,
>> > we
>> > have
>> > tried even adding that to the RSEXEC. No change. We also checked IIS
>> > for
>> > the
>> > Report folder and it is using Windows Integrated Security. One more
>> > thing,
>> > the dataset is using the aspnet login. When we make the person an
>> > administrator on the server - it works fine. Of course that options is
>> > not
>> > feasible. Any ideas of what we missed?
>>

Integrated AND Basic authentication?!

Trying to set up a site with both integrated and basic authentication
enabled (anonymous disabled of course).
When working on local network I want integrated auth. to act, and it does,
no problem.
Accessing site from outside of local network Basic auth. should kick in, and
it does, no problem. But Basic auth. does not listen to default domain. It
takes the local machinename as auth. domain.
Am I doing something wrong or is this the behaviour to expect?
Any help would be very appreciated!
Kjellsorry wrong group, posting this to the right group...
Sorry!!
Kjell
"Kjell Brandes" <kjell@.brandes.tv> wrote in message
news:%232VKlMAlEHA.3520@.TK2MSFTNGP11.phx.gbl...
> Trying to set up a site with both integrated and basic authentication
> enabled (anonymous disabled of course).
> When working on local network I want integrated auth. to act, and it does,
> no problem.
> Accessing site from outside of local network Basic auth. should kick in,
and
> it does, no problem. But Basic auth. does not listen to default domain. It
> takes the local machinename as auth. domain.
> Am I doing something wrong or is this the behaviour to expect?
> Any help would be very appreciated!
> Kjell
>|||Are you typing domain\username for the user name in the security dialog? If
not specified, it will default to the local machine account.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kjell Brandes" <kjell@.brandes.tv> wrote in message
news:eafkcXAlEHA.2764@.TK2MSFTNGP11.phx.gbl...
> sorry wrong group, posting this to the right group...
> Sorry!!
> Kjell
>
> "Kjell Brandes" <kjell@.brandes.tv> wrote in message
> news:%232VKlMAlEHA.3520@.TK2MSFTNGP11.phx.gbl...
>> Trying to set up a site with both integrated and basic authentication
>> enabled (anonymous disabled of course).
>> When working on local network I want integrated auth. to act, and it
>> does,
>> no problem.
>> Accessing site from outside of local network Basic auth. should kick in,
> and
>> it does, no problem. But Basic auth. does not listen to default domain.
>> It
>> takes the local machinename as auth. domain.
>> Am I doing something wrong or is this the behaviour to expect?
>> Any help would be very appreciated!
>> Kjell
>>
>|||the default domain used for basic authenication is controlled by an IIS
property. Use the IIS snap in. Open Properties for the WWW server. Select
the Directory Security Tab. (on IIS 5)
you will see next to the Basic authentication check box the Phrase:
SELECT A DOMAIN and a button labeled EDIT
Click the EDIT button and type in the domain name you want to use for the
default.
the alternative, of course, as Brian pointed out, is to explicitly type the
domain in the username dialog box during basic authentication.
Hope this helps.
dlr
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:eUXUJSFlEHA.3520@.TK2MSFTNGP11.phx.gbl...
> Are you typing domain\username for the user name in the security dialog?
If
> not specified, it will default to the local machine account.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Kjell Brandes" <kjell@.brandes.tv> wrote in message
> news:eafkcXAlEHA.2764@.TK2MSFTNGP11.phx.gbl...
> > sorry wrong group, posting this to the right group...
> >
> > Sorry!!
> >
> > Kjell
> >
> >
> > "Kjell Brandes" <kjell@.brandes.tv> wrote in message
> > news:%232VKlMAlEHA.3520@.TK2MSFTNGP11.phx.gbl...
> >> Trying to set up a site with both integrated and basic authentication
> >> enabled (anonymous disabled of course).
> >> When working on local network I want integrated auth. to act, and it
> >> does,
> >> no problem.
> >> Accessing site from outside of local network Basic auth. should kick
in,
> > and
> >> it does, no problem. But Basic auth. does not listen to default domain.
> >> It
> >> takes the local machinename as auth. domain.
> >> Am I doing something wrong or is this the behaviour to expect?
> >>
> >> Any help would be very appreciated!
> >>
> >> Kjell
> >>
> >>
> >
> >
>

Installing Sql Express on a Peer to Peer Network Log in and Password problems

I am trying to set up Sql Server Express on a peer to peer network. I need to set a log in and password for the service so that I can access the DBs from any machine. (ultimately I will be using VB but for now I am just trying to make the connecton through the Management Component studio). I have sql express installed on both machines. I can not find anywhere it will allow me to change from Windows authentication to Sql Authentication I have tried both in the properties of Sql Express management studio and the local Computer management. Help please!!!

hi,

SQLExpress installs by default diabling standard SQL Server authenticated connections...

you can modify that behaviour at install time, specifying the SECURITYMODE=SQL parameter if you execute the setup wit command line parameters or setup.ini file, or in the installation wizard unchecking the "hide advanced features" check box.. a successive wizard task will enable you to define "Mixed mode" as connection option...

if you like to enable Mixed mode after installation, you can manually "hack" the Windows registry modifying the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.3\MSSQLServer
LoginMode = 2
key, where MSSQL.3 identifies your SQLExpress database engine or, more user friendly, you can use the SQL Server Management Studio Express graphical tool to modify the setting..
log in as a member of system administrator, select the Database Engine node in the Object Browser.. rx click->Properties.. in the "Security" tab select "SQL Server and Windows Authentication mode"..

when you are finished, select the Security->Logins node.. select the "sa" login, rx click->Properties.. set a strong password for this special super account.. in the "Status" tab, set "Login: Enabled" property...

restart the SQLExpress instance..

you can now add your own standard SQL Server logins as desired..

regards

|||Thanks for your help up and running and testing.

Installing Sql Express on a Peer to Peer Network Log in and Password problems

I am trying to set up Sql Server Express on a peer to peer network. I need to set a log in and password for the service so that I can access the DBs from any machine. (ultimately I will be using VB but for now I am just trying to make the connecton through the Management Component studio). I have sql express installed on both machines. I can not find anywhere it will allow me to change from Windows authentication to Sql Authentication I have tried both in the properties of Sql Express management studio and the local Computer management. Help please!!!

hi,

SQLExpress installs by default diabling standard SQL Server authenticated connections...

you can modify that behaviour at install time, specifying the SECURITYMODE=SQL parameter if you execute the setup wit command line parameters or setup.ini file, or in the installation wizard unchecking the "hide advanced features" check box.. a successive wizard task will enable you to define "Mixed mode" as connection option...

if you like to enable Mixed mode after installation, you can manually "hack" the Windows registry modifying the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.3\MSSQLServer
LoginMode = 2
key, where MSSQL.3 identifies your SQLExpress database engine or, more user friendly, you can use the SQL Server Management Studio Express graphical tool to modify the setting..
log in as a member of system administrator, select the Database Engine node in the Object Browser.. rx click->Properties.. in the "Security" tab select "SQL Server and Windows Authentication mode"..

when you are finished, select the Security->Logins node.. select the "sa" login, rx click->Properties.. set a strong password for this special super account.. in the "Status" tab, set "Login: Enabled" property...

restart the SQLExpress instance..

you can now add your own standard SQL Server logins as desired..

regards

|||Thanks for your help up and running and testing.