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
Related
I'm using Xampp server (Apache server ) for my website however it has some connectivity issues with the internet and I can't access it online. So I was advised that I must use Windows server 2008. Let me know if this is a good idea or not. The Xampp has issue with port forward through Dynamic IP. Let me know the best option that I have.
To connect your Apache webserver to the internet you don't need to do any local port-forwarding, you should try port-forwarding with your router. If you're runing linux, you should type ifconfig and look for your default gateway, that's the ip your router is using.
Some ISP's force you to use their own website to port-forward though. Standard, apache always runs on port 80, which you should allow in your firewall using the TCP protocol.
Perhaps you could explain your situation more, Windows Server won't make the hosting easier though. You will most likely encounter the same problems.
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 have configured jetty-maven-plugin in my eclipse Mars and I can run the server using jetty start and stop goals. I can able to access the website using http://localhost:8080/myapp but not using local IP address(i.e., http://192.168.0.5:8080/myapp) from my own computer or other computers connected in the same network via LAN and Wi-Fi.
As mentioned as a solution in these posts,
how to make jetty server accessible from LAN?
Configuring Jetty to accept connections from all hosts
I configured the server host to 0.0.0.0 from localhost to listen on all hosts. With this setting I can see on server start log,
INFO:oejs.AbstractConnector:Started SelectChannelConnector#0.0.0.0:8080
and it works only on http://localhost:8080 but it's not accessible from http://192.168.0.5:8080.
I also tried running that if the interface is accessible using the Networks Interface Listing as mentioned in this comment. and I got,
Display name: NETGEAR WNA1000M N150 Wireless USB Micro Adapter
Name: wlan4
InetAddress: /192.168.0.5
I also tried turning off my Windows Firewall/antivirus but din't help. My jetty version is <jetty.version>9.3.0.M1</jetty.version> and JDK 1.7. What could be the problem? Any help is appreciated.
McAfee Endpoint Security was the culprit here. It was blocking the requests with IP addresses from my very own computer. Turned off the firewall inside the Antivirus and I was able to access the site with http://192.168.0.5:8080/mysite from the browser and other devices connected through the network.
Sometimes some other program opens your port on external address before you do that with Jetty. It will receive all traffic instead. On Windows you will not know it if you reuse port (that is Jetty's default behavior). Check with netstat -ano what is the IP of the process that is indeed listening on 0.0.0.0:8080. Verify if it is your Jetty process only.
Then try connecting with telnet or netcat and see if you can open the connection and what is the response.
Am using Netgear dgn1000 router and just planning to execute a server-client program over internet.
I switched off windows firewall. Allowed DMZ in router. Also Disabled antivirus in both the system. I don't know what else i got to do.?Please do help
Have you enabled port forwarding to the PC that the server is running on?
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.