June 18, 2009 at 8:49 am
HI
I got two XP sp3 machine having IIS 5.1
I install SQL 2008 on it and Configure my Report server by using
Reporting Services Configuration Manager
with following setting
Services account
= Local System
Web URL
= All assigned
TCP port 8080
Reporting mode
= native
So
and I got following URL
when it click http://level2/ReportServer
I can able to access My report and view report
but when i try to enter same URL on Different machine i cant able to open report
I can able to see SQl database for this machice and able to ping the two machine
I dont have any Domain account on my machine..
i will be really helpful pls help me...
June 19, 2009 at 5:37 am
Hi,
First of all you should browse the /Reports folder for viewing reports and executing reports if you want to run reports directly on the reports web application.
And probably the /Reports folder is configured for Windows authentication so you should have configured permissions on the report folders and reports for NT Users.
Eralper
June 19, 2009 at 9:32 am
Yes i can able to access http://level2:8080/Reports locally and i can view the reports
but when i put IP of machince name it is asking me for USER name and Password
USer name format is @Domain\machinename
But i do not have any domain name for this network.
June 22, 2009 at 4:05 pm
Try entering your credentials using the machine name instead of the domain name.
I.e. LEVEL2\UserName
June 30, 2009 at 12:22 pm
I tried it ,
and It is not working...
still having same problem
June 30, 2009 at 1:37 pm
Have you created a SQL Server login for SSRS? You will need to login to your SQL Server's Reporting Engine with Management Studio to create/modify the accounts.
I have very little experience with running SQL Server in workgroup environments, I usually work with either local systems or domains. I know that SQL behaves somewhat differently in a workgroup configuration compared to a domain configuration. This is a result of the inherent security within domains. A domain is managed by a domain administrator through the use of domain controller server(s).
Because workgroups don't have this centrally managed authority, they're treated with a lower level of trust. Anyone can join any Windows computer to a workgroup by simply configuring the network options and rebooting. This poses some obvious security issues.
Additionally, because workgroups don't have a centrally managed authority for membership & permissions (i.e. Active Directory/domain controller), two people can belong to the same workgroup with the same account name. This is why workgroups use MACHINENAME\USERNAME instead of WORKGROUPNAME\USERNAME when managing credentials across a network.
I suspect that your problem is a result of SQL Server not being able to fully authenticate the session from the remote machine. If you need help with creating a login for your reporting services instance let me know. I'll try to help you with that too.
I know this wasn't a very insightful answer to your question, but I hope that you at least have a better understanding of what's going on in the background. :rolleyes:
March 1, 2011 at 8:16 am
Hi. Thanks for explaining domain vs workgroup accounts. I've been googling for this problem for days now and your answer is the best explanation I encountered. So if SQL Server is having problems because of the workgroup account, how are we suppose to create a RS with DB on the same machine? Is this explanation same for all SQL Server Editions (2005, 2008 and 2008 R2) and Windows OS (XP SP3 and Win 7)?
Thank you and more power. 🙂
Alexander MacGregor (6/30/2009)
Have you created a SQL Server login for SSRS? You will need to login to your SQL Server's Reporting Engine with Management Studio to create/modify the accounts.I have very little experience with running SQL Server in workgroup environments, I usually work with either local systems or domains. I know that SQL behaves somewhat differently in a workgroup configuration compared to a domain configuration. This is a result of the inherent security within domains. A domain is managed by a domain administrator through the use of domain controller server(s).
Because workgroups don't have this centrally managed authority, they're treated with a lower level of trust. Anyone can join any Windows computer to a workgroup by simply configuring the network options and rebooting. This poses some obvious security issues.
Additionally, because workgroups don't have a centrally managed authority for membership & permissions (i.e. Active Directory/domain controller), two people can belong to the same workgroup with the same account name. This is why workgroups use MACHINENAME\USERNAME instead of WORKGROUPNAME\USERNAME when managing credentials across a network.
I suspect that your problem is a result of SQL Server not being able to fully authenticate the session from the remote machine. If you need help with creating a login for your reporting services instance let me know. I'll try to help you with that too.
I know this wasn't a very insightful answer to your question, but I hope that you at least have a better understanding of what's going on in the background. :rolleyes:
March 1, 2011 at 9:27 am
Thanks koshikei!
You can install & use Reporting Services on a non-domain computer, but you won't be able to use Windows Authentication to manage access from other computers.
Instead, you can use forms authentication (MSDN: How to Configure Custom or Forms Authentication in Reporting Services), but this is somewhat involved and requires some ASP.NET coding (see MSDN: Implementing a Security Extension for more info).
The authentication concepts should be the same for SQL Server 2005 & later (not sure about SQL 2000) and Windows XP or later. Although, I'm not sure if Reporting Services 2005 provides the same API functionality for developing a custom security extension that 2008 & 2008 R2 provide.
I'm pretty sure that previous versions of Windows (e.g. Windows 2000, Windows ME :crazy:, etc...) should behave similarly too. Thankfully, I haven't had to work with anything that old.:-P
March 1, 2011 at 8:12 pm
Okay. Thanks for your suggestion. I will try that as soon as I install SSRS (for the nth time) in my pc. I still have questions but I'll raise them after I tried some solutions I found. Thanks again for your suggestion and for your speedy reply. 🙂
May 6, 2013 at 11:47 pm
Hi All,
When I am trying to access report server or reports url I am getting below message. Please let me know what should we do to resolve this issue.
"No web site is configured at this address"
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply