Hi,
I would like to ask what is the difference between "Login" and "User" entity.
I know that a Login is a principal and I can use it for accessing db
resource, and I can to limit its rights. Why there is a "User" entity also?
Thanks,
Lubomir
At a very basic level, a login is at the server level and
allows connecting to the server.
A user is at the database level and allows access to the
database.
-Sue
On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
<Lubomir@.discussions.microsoft.com> wrote:
>Hi,
>I would like to ask what is the difference between "Login" and "User" entity.
>I know that a Login is a principal and I can use it for accessing db
>resource, and I can to limit its rights. Why there is a "User" entity also?
>Thanks,
>Lubomir
|||Thanks.
"Sue Hoegemeier" wrote:
> At a very basic level, a login is at the server level and
> allows connecting to the server.
> A user is at the database level and allows access to the
> database.
> -Sue
> On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
> <Lubomir@.discussions.microsoft.com> wrote:
>
>
Showing posts with label accessing. Show all posts
Showing posts with label accessing. Show all posts
Monday, March 12, 2012
Logins and users
Hi,
I would like to ask what is the difference between "Login" and "User" entity
.
I know that a Login is a principal and I can use it for accessing db
resource, and I can to limit its rights. Why there is a "User" entity also?
Thanks,
LubomirHi Lubomir,
Login is a principal that gains access to the server (to SQL Server
instance). It is generally used for granting permissions on server level
(configuration, database creation and so forth).
User is a principal created in specific database by mapping some single
login to it and is generally used for granting permissions in the database.
Read more in Books Online (SQL Server documentation, also available online).
You should also read about roles (server roles and database roles). Roles
are used for managing permissions in more effective way.
Regards
Pawel Potasinski
[http://www.potasinski.pl]
Uytkownik "Lubomir" <Lubomir@.discussions.microsoft.com> napisa w
wiadomoci news:29BC9649-D34E-4FAE-9855-E8E793AE84E0@.microsoft.com...
> Hi,
> I would like to ask what is the difference between "Login" and "User"
> entity.
> I know that a Login is a principal and I can use it for accessing db
> resource, and I can to limit its rights. Why there is a "User" entity
> also?
> Thanks,
> Lubomir|||At a very basic level, a login is at the server level and
allows connecting to the server.
A user is at the database level and allows access to the
database.
-Sue
On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
<Lubomir@.discussions.microsoft.com> wrote:
>Hi,
>I would like to ask what is the difference between "Login" and "User" entit
y.
>I know that a Login is a principal and I can use it for accessing db
>resource, and I can to limit its rights. Why there is a "User" entity also
?
>Thanks,
>Lubomir|||Thanks.
"Sue Hoegemeier" wrote:
> At a very basic level, a login is at the server level and
> allows connecting to the server.
> A user is at the database level and allows access to the
> database.
> -Sue
> On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
> <Lubomir@.discussions.microsoft.com> wrote:
>
>
I would like to ask what is the difference between "Login" and "User" entity
.
I know that a Login is a principal and I can use it for accessing db
resource, and I can to limit its rights. Why there is a "User" entity also?
Thanks,
LubomirHi Lubomir,
Login is a principal that gains access to the server (to SQL Server
instance). It is generally used for granting permissions on server level
(configuration, database creation and so forth).
User is a principal created in specific database by mapping some single
login to it and is generally used for granting permissions in the database.
Read more in Books Online (SQL Server documentation, also available online).
You should also read about roles (server roles and database roles). Roles
are used for managing permissions in more effective way.
Regards
Pawel Potasinski
[http://www.potasinski.pl]
Uytkownik "Lubomir" <Lubomir@.discussions.microsoft.com> napisa w
wiadomoci news:29BC9649-D34E-4FAE-9855-E8E793AE84E0@.microsoft.com...
> Hi,
> I would like to ask what is the difference between "Login" and "User"
> entity.
> I know that a Login is a principal and I can use it for accessing db
> resource, and I can to limit its rights. Why there is a "User" entity
> also?
> Thanks,
> Lubomir|||At a very basic level, a login is at the server level and
allows connecting to the server.
A user is at the database level and allows access to the
database.
-Sue
On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
<Lubomir@.discussions.microsoft.com> wrote:
>Hi,
>I would like to ask what is the difference between "Login" and "User" entit
y.
>I know that a Login is a principal and I can use it for accessing db
>resource, and I can to limit its rights. Why there is a "User" entity also
?
>Thanks,
>Lubomir|||Thanks.
"Sue Hoegemeier" wrote:
> At a very basic level, a login is at the server level and
> allows connecting to the server.
> A user is at the database level and allows access to the
> database.
> -Sue
> On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
> <Lubomir@.discussions.microsoft.com> wrote:
>
>
Logins and users
Hi,
I would like to ask what is the difference between "Login" and "User" entity.
I know that a Login is a principal and I can use it for accessing db
resource, and I can to limit its rights. Why there is a "User" entity also?
Thanks,
LubomirHi Lubomir,
Login is a principal that gains access to the server (to SQL Server
instance). It is generally used for granting permissions on server level
(configuration, database creation and so forth).
User is a principal created in specific database by mapping some single
login to it and is generally used for granting permissions in the database.
Read more in Books Online (SQL Server documentation, also available online).
You should also read about roles (server roles and database roles). Roles
are used for managing permissions in more effective way.
--
Regards
Pawel Potasinski
[http://www.potasinski.pl]
U¿ytkownik "Lubomir" <Lubomir@.discussions.microsoft.com> napisa³ w
wiadomo¶ci news:29BC9649-D34E-4FAE-9855-E8E793AE84E0@.microsoft.com...
> Hi,
> I would like to ask what is the difference between "Login" and "User"
> entity.
> I know that a Login is a principal and I can use it for accessing db
> resource, and I can to limit its rights. Why there is a "User" entity
> also?
> Thanks,
> Lubomir|||At a very basic level, a login is at the server level and
allows connecting to the server.
A user is at the database level and allows access to the
database.
-Sue
On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
<Lubomir@.discussions.microsoft.com> wrote:
>Hi,
>I would like to ask what is the difference between "Login" and "User" entity.
>I know that a Login is a principal and I can use it for accessing db
>resource, and I can to limit its rights. Why there is a "User" entity also?
>Thanks,
>Lubomir|||Thanks.
"Sue Hoegemeier" wrote:
> At a very basic level, a login is at the server level and
> allows connecting to the server.
> A user is at the database level and allows access to the
> database.
> -Sue
> On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
> <Lubomir@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I would like to ask what is the difference between "Login" and "User" entity.
> >
> >I know that a Login is a principal and I can use it for accessing db
> >resource, and I can to limit its rights. Why there is a "User" entity also?
> >
> >Thanks,
> >
> >Lubomir
>
I would like to ask what is the difference between "Login" and "User" entity.
I know that a Login is a principal and I can use it for accessing db
resource, and I can to limit its rights. Why there is a "User" entity also?
Thanks,
LubomirHi Lubomir,
Login is a principal that gains access to the server (to SQL Server
instance). It is generally used for granting permissions on server level
(configuration, database creation and so forth).
User is a principal created in specific database by mapping some single
login to it and is generally used for granting permissions in the database.
Read more in Books Online (SQL Server documentation, also available online).
You should also read about roles (server roles and database roles). Roles
are used for managing permissions in more effective way.
--
Regards
Pawel Potasinski
[http://www.potasinski.pl]
U¿ytkownik "Lubomir" <Lubomir@.discussions.microsoft.com> napisa³ w
wiadomo¶ci news:29BC9649-D34E-4FAE-9855-E8E793AE84E0@.microsoft.com...
> Hi,
> I would like to ask what is the difference between "Login" and "User"
> entity.
> I know that a Login is a principal and I can use it for accessing db
> resource, and I can to limit its rights. Why there is a "User" entity
> also?
> Thanks,
> Lubomir|||At a very basic level, a login is at the server level and
allows connecting to the server.
A user is at the database level and allows access to the
database.
-Sue
On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
<Lubomir@.discussions.microsoft.com> wrote:
>Hi,
>I would like to ask what is the difference between "Login" and "User" entity.
>I know that a Login is a principal and I can use it for accessing db
>resource, and I can to limit its rights. Why there is a "User" entity also?
>Thanks,
>Lubomir|||Thanks.
"Sue Hoegemeier" wrote:
> At a very basic level, a login is at the server level and
> allows connecting to the server.
> A user is at the database level and allows access to the
> database.
> -Sue
> On Tue, 7 Aug 2007 11:40:01 -0700, Lubomir
> <Lubomir@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I would like to ask what is the difference between "Login" and "User" entity.
> >
> >I know that a Login is a principal and I can use it for accessing db
> >resource, and I can to limit its rights. Why there is a "User" entity also?
> >
> >Thanks,
> >
> >Lubomir
>
Wednesday, March 7, 2012
Login vs. User (basic questions)
In the Books Online, it is stated that '...a single login is mapped to one u
ser account created in each database the login is accessing'. As long as on
ly one login can be used in a db and a user is associated with a login, what
is the purpose of having a
distinction between a User and a Login? Why can't you just add a Login to a
database and skip the User? Also, what is the purpose of allowing the user
name to be different than the login name (I realize it defaults to the login
name)? Since connection
strings use the login name, what purpose is there to have the username poten
tially different?
I'm assuming this has something to do with database (as opposed to server) r
oles, in which case multiple users can be added to a role. However, why are
n't Logins added directly to roles instead of Users?Sorry, but you should try and keep this as simple as possible.
A login is a security mechanism to control access to SQL server.
A user account is a security mechanism to control access to databases once a
connection has been established to SQL Server with a login. That is why
logins are mapped to user accounts.
Logins can be added to server roles to give that login rights to perform
server level operations -- adding logins/users, adding databases, etc.
Users are added to database roles since you need a user account to connect
to the database. DBO is an important one -- database owner.
Don't forget to read up on groups -- especially public.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:55BC9EF1-E300-46D3-8EC8-D69BADF4843B@.microsoft.com...
user account created in each database the login is accessing'. As long as
only one login can be used in a db and a user is associated with a login,
what is the purpose of having a distinction between a User and a Login? Why
can't you just add a Login to a database and skip the User? Also, what is
the purpose of allowing the user name to be different than the login name (I
realize it defaults to the login name)? Since connection strings use the
login name, what purpose is there to have the username potentially
different?
roles, in which case multiple users can be added to a role. However, why
aren't Logins added directly to roles instead of Users?|||"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:55BC9EF1-E300-46D3-8EC8-D69BADF4843B@.microsoft.com...
user account created in each database the login is accessing'. As long as
only one login can be used in a db and a user is associated with a login,
what is the purpose of having a distinction between a User and a Login? Why
can't you just add a Login to a database and skip the User? Also, what is
the purpose of allowing the user name to be different than the login name (I
realize it defaults to the login name)? Since connection strings use the
login name, what purpose is there to have the username potentially
different?<
Thing of accessing SQL Server as a two-tier process. You need a login to
connect to SQL Server, then you need to grant a login access to a specific
database or databases. Where possible it's recommended to use Windows
Authentication, grant login authentication to NT groups, and assign specific
database access to those groups. Once this mechanism is in place, it's
simple a matter of adding a user or users to the particular group and you're
done!
Please read this paper for a more in-depth discussion:
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/default.asp
roles, in which case multiple users can be added to a role. However, why
aren't Logins added directly to roles instead of Users?<
Roles were designed to be used by applications that could connect via a
given account/password (hidden in the application) that have specific rights
on a database.|||> "mt" <anonymous@.discussions.microsoft.com> wrote in message
Why
(I
Thing of accessing SQL Server as a two-tier process. You need a login to
connect to SQL Server, then you need to grant a login access to a specific
database or databases. Where possible it's recommended to use Windows
Authentication, grant login authentication to NT groups, and assign specific
database access to those groups. Once this mechanism is in place, it's
simple a matter of adding a user or users to the particular group and you're
done!
Please read this paper for a more in-depth discussion (watch line wrap):
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/default.asp
Roles were designed to be used by applications that could connect via a
given account/password (hidden in the application) that have specific rights
on a database.
Steve|||MT,
As a newbie on SQL server ( I'm an Oracle DBA ) I found out that the online
docs where prety clear on how to log into the server / database(s) Please re
ad the "Permissions Validation" part in the "Administring SQLserver/Managing
security /Security levels"
ser account created in each database the login is accessing'. As long as on
ly one login can be used in a db and a user is associated with a login, what
is the purpose of having a
distinction between a User and a Login? Why can't you just add a Login to a
database and skip the User? Also, what is the purpose of allowing the user
name to be different than the login name (I realize it defaults to the login
name)? Since connection
strings use the login name, what purpose is there to have the username poten
tially different?
I'm assuming this has something to do with database (as opposed to server) r
oles, in which case multiple users can be added to a role. However, why are
n't Logins added directly to roles instead of Users?Sorry, but you should try and keep this as simple as possible.
A login is a security mechanism to control access to SQL server.
A user account is a security mechanism to control access to databases once a
connection has been established to SQL Server with a login. That is why
logins are mapped to user accounts.
Logins can be added to server roles to give that login rights to perform
server level operations -- adding logins/users, adding databases, etc.
Users are added to database roles since you need a user account to connect
to the database. DBO is an important one -- database owner.
Don't forget to read up on groups -- especially public.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:55BC9EF1-E300-46D3-8EC8-D69BADF4843B@.microsoft.com...
quote:
> In the Books Online, it is stated that '...a single login is mapped to one
user account created in each database the login is accessing'. As long as
only one login can be used in a db and a user is associated with a login,
what is the purpose of having a distinction between a User and a Login? Why
can't you just add a Login to a database and skip the User? Also, what is
the purpose of allowing the user name to be different than the login name (I
realize it defaults to the login name)? Since connection strings use the
login name, what purpose is there to have the username potentially
different?
quote:
> I'm assuming this has something to do with database (as opposed to server)
roles, in which case multiple users can be added to a role. However, why
aren't Logins added directly to roles instead of Users?|||"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:55BC9EF1-E300-46D3-8EC8-D69BADF4843B@.microsoft.com...
quote:
> In the Books Online, it is stated that '...a single login is mapped to one
user account created in each database the login is accessing'. As long as
only one login can be used in a db and a user is associated with a login,
what is the purpose of having a distinction between a User and a Login? Why
can't you just add a Login to a database and skip the User? Also, what is
the purpose of allowing the user name to be different than the login name (I
realize it defaults to the login name)? Since connection strings use the
login name, what purpose is there to have the username potentially
different?<
Thing of accessing SQL Server as a two-tier process. You need a login to
connect to SQL Server, then you need to grant a login access to a specific
database or databases. Where possible it's recommended to use Windows
Authentication, grant login authentication to NT groups, and assign specific
database access to those groups. Once this mechanism is in place, it's
simple a matter of adding a user or users to the particular group and you're
done!
Please read this paper for a more in-depth discussion:
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/default.asp
quote:
> I'm assuming this has something to do with database (as opposed to server)
roles, in which case multiple users can be added to a role. However, why
aren't Logins added directly to roles instead of Users?<
Roles were designed to be used by applications that could connect via a
given account/password (hidden in the application) that have specific rights
on a database.|||> "mt" <anonymous@.discussions.microsoft.com> wrote in message
quote:
> news:55BC9EF1-E300-46D3-8EC8-D69BADF4843B@.microsoft.com...
one[QUOTE]
> user account created in each database the login is accessing'. As long as
> only one login can be used in a db and a user is associated with a login,
> what is the purpose of having a distinction between a User and a Login?
Why
quote:
> can't you just add a Login to a database and skip the User? Also, what is
> the purpose of allowing the user name to be different than the login name
(I
quote:
> realize it defaults to the login name)? Since connection strings use the
> login name, what purpose is there to have the username potentially
> different?<
>
Thing of accessing SQL Server as a two-tier process. You need a login to
connect to SQL Server, then you need to grant a login access to a specific
database or databases. Where possible it's recommended to use Windows
Authentication, grant login authentication to NT groups, and assign specific
database access to those groups. Once this mechanism is in place, it's
simple a matter of adding a user or users to the particular group and you're
done!
Please read this paper for a more in-depth discussion (watch line wrap):
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/default.asp
quote:
>
server)[QUOTE]
> roles, in which case multiple users can be added to a role. However, why
> aren't Logins added directly to roles instead of Users?<
>
Roles were designed to be used by applications that could connect via a
given account/password (hidden in the application) that have specific rights
on a database.
quote:
>
Steve|||MT,
As a newbie on SQL server ( I'm an Oracle DBA ) I found out that the online
docs where prety clear on how to log into the server / database(s) Please re
ad the "Permissions Validation" part in the "Administring SQLserver/Managing
security /Security levels"
Login to SQL with non domain account
I have a problem accessing a SQL instance from a VB script that uses a SQL
user, and is executed with a local computer user.
When I use the same VB script while logged on with any domain user it
executes successfully.
All SQL tools like query analyzer and enterprise admin have not problems.
What can cause this problem?
Any help would be appreciated.
Thanks in advance,
Ido Friedman
Hi,
Looks liks your SQL Server is setup for Windows Authentication only. In that
case to communicate to
SQL Server you may need to login to client with an domain user which has
access to SQL Server. Incase
if you can not do that then change the authetication mode to Windows and SQL
Server authentication.
In this you could connect to SQL Server using SQL Server Authentication.
Thanks
Hari
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:85A4A648-23E0-4AF6-870D-BE7380734DBC@.microsoft.com...
>I have a problem accessing a SQL instance from a VB script that uses a SQL
> user, and is executed with a local computer user.
> When I use the same VB script while logged on with any domain user it
> executes successfully.
> All SQL tools like query analyzer and enterprise admin have not problems.
> What can cause this problem?
> Any help would be appreciated.
>
> Thanks in advance,
> Ido Friedman
user, and is executed with a local computer user.
When I use the same VB script while logged on with any domain user it
executes successfully.
All SQL tools like query analyzer and enterprise admin have not problems.
What can cause this problem?
Any help would be appreciated.
Thanks in advance,
Ido Friedman
Hi,
Looks liks your SQL Server is setup for Windows Authentication only. In that
case to communicate to
SQL Server you may need to login to client with an domain user which has
access to SQL Server. Incase
if you can not do that then change the authetication mode to Windows and SQL
Server authentication.
In this you could connect to SQL Server using SQL Server Authentication.
Thanks
Hari
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:85A4A648-23E0-4AF6-870D-BE7380734DBC@.microsoft.com...
>I have a problem accessing a SQL instance from a VB script that uses a SQL
> user, and is executed with a local computer user.
> When I use the same VB script while logged on with any domain user it
> executes successfully.
> All SQL tools like query analyzer and enterprise admin have not problems.
> What can cause this problem?
> Any help would be appreciated.
>
> Thanks in advance,
> Ido Friedman
Friday, February 24, 2012
Login Security issues
RS installed on machine outside the firewall using SQL installed locally,
accessing data on SQL server inside the firewall using a shared data source.
Have given group browser rights on the top-level folder in RS.
When user initially accesses the reports home page, they are prompted for a
login and then the home page folders are displayed. Clicking on the folder
displays all the reports. Accessing a report prompts for login again. Same
user & password will display the report - and the login is not requested
again for the duration of the session.
How to avoid prompting for login twice?
Thanks
MarkI have more information on this issue...
WHen accessing from outside, the first login grants access to the home page
and the reports folders. However, when selecting a report - at the point
where we get a second login request in side the firewall - instead we get an
error:
The page cannot be displayed
Cannot find server or DNS Error|||More details...
Inside the firewall all works fine..
Outside the firewall I get these results...
This is the home page:
http://<server>/reports/Pages/Folder.aspx
This page works fine
Click on the folder for Remedy Reports and it goes here
http://<server>/Reports/Pages/Folder.aspx?ItemPath=%2fRemedy+Reports&IsDetailsView=False
This page works fine
Click on a report to view it and..
http://<server>/Reports/Pages/Report.aspx?ItemPath=%2fRemedy+Reports%2f72+Hour+Report
Outside the firewall, this page gets an error:
Cannot find server or DNS error|||Hopefully someone else can jump in with the particulars but I remember
seeing in another post
where there was a place in a config file that you need to make a change so
the server is in the form of servername.blah.blah rather than just
servername.
Just a guess since I have not had this situation occur before.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mark Nicks" <MarkNicks@.discussions.microsoft.com> wrote in message
news:864759C8-39B0-4D23-9F7A-914464D13D3C@.microsoft.com...
> More details...
> Inside the firewall all works fine..
> Outside the firewall I get these results...
> This is the home page:
> http://<server>/reports/Pages/Folder.aspx
> This page works fine
> Click on the folder for Remedy Reports and it goes here:
>
http://<server>/Reports/Pages/Folder.aspx?ItemPath=%2fRemedy+Reports&IsDetailsView=False
> This page works fine
> Click on a report to view it and...
>
http://<server>/Reports/Pages/Report.aspx?ItemPath=%2fRemedy+Reports%2f72+Hour+Report
> Outside the firewall, this page gets an error:
> Cannot find server or DNS error|||Bruce I did find the answer posted in the forum. I'm reposting Dmitry
Vasilevsy's response here for anyone who runs across it...
Try accessing /ReportServer virtual folder (not /Report) from outside the
intranet, if it works, you just need to configure Report Manager application
properly.
The simplest way to do this is when you are running Report Server and Report
Manager application on the same machine (this is the only option available
when you run setup). Go look at the Report Manager configuration file,
RSWebApplication.config. There is a UI section
<UI>
<ReportServerUrl>http://intranet-computer-name/ReportServer</ReportServerUrl
>
</UI>
Change it to
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
You should be able to access Report Manager from both intranet and internet.
accessing data on SQL server inside the firewall using a shared data source.
Have given group browser rights on the top-level folder in RS.
When user initially accesses the reports home page, they are prompted for a
login and then the home page folders are displayed. Clicking on the folder
displays all the reports. Accessing a report prompts for login again. Same
user & password will display the report - and the login is not requested
again for the duration of the session.
How to avoid prompting for login twice?
Thanks
MarkI have more information on this issue...
WHen accessing from outside, the first login grants access to the home page
and the reports folders. However, when selecting a report - at the point
where we get a second login request in side the firewall - instead we get an
error:
The page cannot be displayed
Cannot find server or DNS Error|||More details...
Inside the firewall all works fine..
Outside the firewall I get these results...
This is the home page:
http://<server>/reports/Pages/Folder.aspx
This page works fine
Click on the folder for Remedy Reports and it goes here
http://<server>/Reports/Pages/Folder.aspx?ItemPath=%2fRemedy+Reports&IsDetailsView=False
This page works fine
Click on a report to view it and..
http://<server>/Reports/Pages/Report.aspx?ItemPath=%2fRemedy+Reports%2f72+Hour+Report
Outside the firewall, this page gets an error:
Cannot find server or DNS error|||Hopefully someone else can jump in with the particulars but I remember
seeing in another post
where there was a place in a config file that you need to make a change so
the server is in the form of servername.blah.blah rather than just
servername.
Just a guess since I have not had this situation occur before.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mark Nicks" <MarkNicks@.discussions.microsoft.com> wrote in message
news:864759C8-39B0-4D23-9F7A-914464D13D3C@.microsoft.com...
> More details...
> Inside the firewall all works fine..
> Outside the firewall I get these results...
> This is the home page:
> http://<server>/reports/Pages/Folder.aspx
> This page works fine
> Click on the folder for Remedy Reports and it goes here:
>
http://<server>/Reports/Pages/Folder.aspx?ItemPath=%2fRemedy+Reports&IsDetailsView=False
> This page works fine
> Click on a report to view it and...
>
http://<server>/Reports/Pages/Report.aspx?ItemPath=%2fRemedy+Reports%2f72+Hour+Report
> Outside the firewall, this page gets an error:
> Cannot find server or DNS error|||Bruce I did find the answer posted in the forum. I'm reposting Dmitry
Vasilevsy's response here for anyone who runs across it...
Try accessing /ReportServer virtual folder (not /Report) from outside the
intranet, if it works, you just need to configure Report Manager application
properly.
The simplest way to do this is when you are running Report Server and Report
Manager application on the same machine (this is the only option available
when you run setup). Go look at the Report Manager configuration file,
RSWebApplication.config. There is a UI section
<UI>
<ReportServerUrl>http://intranet-computer-name/ReportServer</ReportServerUrl
>
</UI>
Change it to
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
You should be able to access Report Manager from both intranet and internet.
Subscribe to:
Posts (Atom)