I have been trying for SSRS 2008R2 reports access from my one of the server which are delpoyed on it (O.S windows 2008 R2 server) to my web
application which is hosted on another server ..
I tried by using reportviewer and by passing the server credentails.
I am getting an error :
Unable to connect to the remote server
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond IPAddess:80
plzz can any one help me..
Looks more a firewall port blocking problem to me.
Can you open the report server via http://yourserver/reports on the machine itself?
If so then check your firewall settings on the server. On default they block all incoming port in "domain", "public" and "private".
EDIT:
Checkout the screenshot for firewall settings (german, but english gui is the same location)
Related
How can I connect my SSMS client to a remote SQL Server 2008 R2 instance using SQL browser AND with Windows firewall enabled?
I find that that with the firewall turned off, I can connect fine (without specifying the instance name). Now when I turn the firewall (domain profile) back on, my connection attempts time out. So, to begin my troubleshooting, I created an 'AnyAny' firewall rule however it still failed with a timeout error.
Naturally I can connect fine either way (firewall turned on/off) when I specify the instance name and port. SQL browser is running and listening on UDP 1433. SQL Server is running Windows 2008 R2.
What is getting blocked? And why won't a custom 'AnyAny' rule bypass it?
The information on this SQLCAT blog might be helpful to you. By default, the SQL Browser service runs on UDP port 1434. If you have a firewall configured on your SQL server, you should open up port 1434 for inbound connections from SSMS.
If you need help setting remote connections to your SQL Server, this guide is spot on.
We have Tableau Desktop & Redshift as datasource. When we are publishing the report to Tableau server (hosted) we are getting following error :
An unexpected error occurred on the server. If you continue to receive this error please contact your Tableau Server Administrator.
TableauException: Could not connect to the server; A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [58.89.281.166:5439] Unable to connect to the server "abc.redshift.amazonaws.com". Check that the server is running and that you have access privile...
2014-06-17 13:56:20.974 (U6BI2gq#AWoAAB0gowQAAAGi,0,1)
This is likely caused by the Tableau Server not being able to access the Redshift Server you listed. It looks like a time out occurred which indicates that a connection attempt failed.
Since it's hosted, you might not be able to verify the connection directly. If you can log onto the Tableau Server and access Windows, you can attempt to establish a connection to the RedShift server at the command line using a tool like Telnet. You need to make sure that the Tableau Server in question can access the Redshift server (verify firewall and security settings for both the Tableau Server and Redshift instance).
I have installed a SQL Express 2008 Server on my Desktop for some local work. This has mixed authentication. I have enabled TCP/IP connection so that one colleague can connect to this server. However, this exposes the server to everyone in the network. How do i keep track of which PC in the network connected to this server and when ? This would just help me audit the usage of the server.
Well you can get information about current users, sessions, and processes in an instance by using
sp_who;
MSDN Documentation
I have a WinForms application installed on multiple PCs in an office, and a SQL Server 2012 Express database on the server to which the client application connects.
Each machine fails to connect on the first two attempts giving an error -
Timeout Expired: The timeout period elapsed prior to the completion of the operation or the server is not responding.
However, it always works on the 3rd attempt on all machines!
The server is SBS 2008, the machines are running Windows 7.
The issue was I had used a Named Instanced on SQL Server which by default uses dynamic ports. Hence each connection attempt used a different Port, and each time I was asking the server administrator to allow additional ports. The successful log ins where simply because the dynamic port chosen just so happened to be one previously allowed.
The answer was to use SQL Server Configuration Manager to remove the dynamic port setting and specify a single port to use for all connection attempts, and ensure firewalls etc had an exception for that particular port.
I have an instance of SQL Server 2008 and SSRS 2008 running on a desktop PC for to be used for development. This PC is registered under my user id and I can remote desktop into it and connect to SSRS just fine from my laptop (also registered under my user id). Also, I can access the website from my laptop when I am NOT logged into the PC (i.e. after a reboot and before logging in).
When another team member tries to connect to SSRS via the web (SSRS is running on port 8080) he cannot connect. I have tried different options like adding his as a user on the PC and granting permissions for him on the Home folder in Report Manager. Nothing seems to work. He CAN connect to the PC over remote desktop so I know that the connectivity is there and since I can access port 8080 from my laptop he should be able to access port 8080 as well.
Anyone have any thoughts on how to grant access to this team member? I am open to all ideas that do not involve writing custom code (which i really should not have to do to fix this issue). This used to work with SSRS 2005 but I know that it used IIS then and now it uses http.sys directly.
Thanks!
Your colleague needs permissions at the file system level to the SSRS folders:
C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportManager
and
C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
in addition to access granted to the website in IIS.
Are these computers in a domain?
What operating system?
Without more information about your network it seems difficult to diagnose this issue. He cannot connect to port 8080 at all, as though the port was blocked? Or is SSRS replying with an error page?
If he can't connect to port 8080 at all it is almost certainly a packet filtering or firewall issue. What happens if you use a telnet application to send an HTTP GET request from his computer to the server on port 8080?
If there are error messages describing them would be quite helpful in finding a resolution.