Solved

SSRS reachable by FQDN on local computer, but not from a different computer

Posted on 2013-10-29
1
632 Views
Last Modified: 2013-10-29
Hello,

I am having trouble getting my SSRS server to successfully cohabitate with IIS, after having to move the server to a different subnet. I have 2 static IPs for that server: .242 is defined explicitly in IIS bindings, and .161 is for SSRS. I have my SSRS Web Service URL set to "All Assigned", and the Report Manager URL set to http://appreports.domain.com:80/reports & https://+:443/reports. DNS is pointing to .161. Also, SSRS points to an external database server.

What I am seeing is strange to me. I can browse to http://appreports.domain.com:80/reports on that server, and it looks great - I am at the SSRS Report Manager page, and all is well. When I call http://appreports.domain.com:80/reports from a different computer, I get an IIS error:

HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)

I am not sure why IIS intercepts the call when accessed remotely. In the System log, I see this:

A Kerberos Error Message was received:
 on logon session
 Client Time:
 Server Time: 17:10:4.0000 10/29/2013 Z
 Error Code: 0x7  KDC_ERR_S_PRINCIPAL_UNKNOWN
 Extended Error: 0xc0000035 KLIN(0)
 Client Realm:
 Client Name:
 Server Realm: DOMAIN.LOCAL
 Server Name: MSSQLSvc/VM-db.domain.local:1433
 Target Name: MSSQLSvc/VM-db.domain.local:1433@Domain.LOCAL
 Error Text:
 File: 9
 Line: f09

In the ReportServerService log, there are no errors - it is the picture of health. I should also say that we are just trying to access http://appreports.domain.com:80/reports from within the local network.

I suspect there is an SPN issue, but I don't understand it well enough to comment. Thoughts most welcome! Naturally, max points on this one.
0
Comment
Question by:Ash_embers
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
Ash_embers earned 0 total points
ID: 39610105
Never mind on this - turns out networking was messed up. Adding a new NIC and putting the IP there fixed everything.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A phishing scam that claims a recipient’s credit card details have been “suspended” is the latest trend in spoof emails.
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

690 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question