March 27, 2013 at 9:09 pm
I am making a VB.Net app that accesses my SQL Server, but when I try to run the app from a remote computer, I get an error that it can't find the server.
It works fine if I access it from the local network using the local IP, but outside, using the public IP, it doesn't work!
I checked the Allow Remote Connection options, but that didn't work either
Also, I tried to put my server as DMZ host on my router, didn't work.
Additionally, I tried to disable windows firewall, no results.
Environment: Windows Server 2012, SQL Server 2012
Maxwell.
April 11, 2013 at 10:02 pm
Just a try..
connect using : instancename,XXXX (1433, port number)
Cheers,
- Win
"Dont Judge a Book by its Cover"
April 12, 2013 at 1:37 am
Are you trying to access SQL from the internet in which case are you using the correct IP address? Try http://www.whatismyip.com/ or similar from the box in question. Can you ping the server?
If it is over the WAN then ask your network admins to check if there are firewalls between sites that are blocking ypur TCP/IP address and port 1433. A telnet to the box from the remote site may help. Also get them to check to see if there any routers with access control lists which are blocking, and yes some network admins will see firewalls and routers+acl as completely different beasts!!
Worse case can you install a Network Monitor tool on the box to see if any traffic is reaching it. Best check with your Security admin to see if this is legit for your company.
As an aside: Why? Why do you want to connect to a sql server over a distance with a vb app. Unless you have a completely locked down sql server, and even then, it is generally not considered to be wise to allow a sql server to be accessed directly from the internet.
Are you using the correct IP Address.
April 12, 2013 at 5:47 am
i'l repeat what has already been said: it's a badk idea to expose your SQL se3rver directly to the internet.
that said, un doubtedly, you'll need to modify the router between the server and the internet; it typically blocks all inbound traffic unless you specifically set up some routing.
remember the rounter usually uses one ip address for all the machines inside the LAN, so a request for port 1433, that you think would go to your SLq server, gets ignored unless you take special steps.
you can also set up port forwarding as well, sot hat , for example, every request asking for port 1433 goes to a specific machine.
here's a screenshot from a home router as an example: it's sending certain ports to a specific machine.
Lowell
April 12, 2013 at 11:18 am
Everything is actually fine!
I was just my ISP doesn't allow you to access local computers using a remote IP.
Maxwell.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply