I have a client that has some data that I need to process. This data is in a closed server that can only be accessed by a Windows Server 2008 server instance, via a specific port on the closed server.
My idea is to create a tunnel that forwards whatever comes from that port to me, although I have no idea of the feasibility of my plan.
Windows Server 2008 instance connects to closed server via socket.
Windows Server 2008 exposes a port that forwards the received data.
I connect to this newly exposed port.
Constraints: I cannot install anything on the Windows Server 2008 instance, so I am left with configuration tweaks and PowerShell scripts.
Is it possible to do this?
I have a lot of experience with Linux servers but none with Windows, I am researching ways to do this, but maybe someone can light the path on what I should look into.
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.
I just start with MongoDB.
I have installed it on Win Server 2008 R2 and hosted it in a win Service, worked.
I tried to connect from a Client using an app, but can't connect.
I checked the Connection string twice, correct (isn't that hard) and I stopped the Firewalls on both machines, nothing helped. The machines were part of a private Network, no Routers in between.
I also used mongo Shell (mongo.exe) on the Server, and I was able to connect.
So, it must be some issue with the Client machine or the Network.
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 remote access enabled in SQL Server at my work network, which is on my "server". In the office, I have my desktop machine which I can use SQL Server Management Studio to access - no problems. I can use telnet [LOCAL_IP] 1433 with no problems.
When I am at home, I want to access the SQL Server too. I can PING [EXTERNAL_IP] address to the office fine (which is a router), but can't telnet [EXTERNAL_IP] 1433. So my machine can't access it when using SQL Server Management Studio.
I thought it was a router firewall issue, I have modified the router firewall to let my IP address through on TCP and UDP on ports 1433 and 1434 both source and destination. I've also tried letting my home IP through on all ports too, and still nothing. I've also tried to disable the firewall on the windows server at work.
I can set up RDP fine though....so I am thinking something I don't know about in SQL Server is the problem.
Does anyone have any suggestions to try please?
Thx
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.