June 22, 2005 at 12:36 pm
Okay I am going crazy...I have a small network, my server is running windows SBS 2003 SP 2, and I have MSDE 2000 running on my server. I cannot access MSDE remotely or privately by IP address. I have enabled TCP/IP protocol in MSDE, and restarted the services, and opened up port 1433 and mapped it to my server on my linksys router, I am not running windows firewall on my server because of the ipnat.sys thing. Can anyone help me...I can hit the MSDE from my workstation my using the server/instance name, but I can't hit it using the IP address of my server.
June 23, 2005 at 3:51 am
If during installation you have named your server using server-name\instance-name you can also access it by using server-ip-address\instance-name. You cannot access it by the ip address of the server alone.
If this installation is the only instance of sqlserver on this machine, then you can reinstall it using the only the server name. Then you will be able to access it using the ip address.
June 23, 2005 at 6:06 am
you should also be able to connect to the instance by connecting to IPaddress,port;
ie 65.34.234.179,1207
you use that format whether it is in QA, a connection string in ASP or .NET; it's not ip-colon-port like a web page, it's ip-comma-port.
see this post for a similar issue; there's is a script to run in QA to find which port the instance is listening too; it may not be 1433 as you are expecting.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=184041#bm185404
Lowell
June 23, 2005 at 9:18 am
Okay...very cool, I can connect via QA perfectly.
BUT...my web programmer is remote and he cannot connect via the ASP web pages written in VB script. Below is the connect string I gave him.
cConnectString = "DRIVER=SQL Server;SERVER=69.154.0.22,1433;UID=webuser;PWD=*********;DATABASE=idealweb"
June 23, 2005 at 10:01 am
ok and on your linksys router, you've mapped some port forwarding so it looks something like this?
if you don't have port forwarding to the sql server, of course your developer cannot get to it; but it's just a firewall setup issue. here's an example setup from my linksys.
others will chime in that it is evil to expose your sql server over the web, but that's another thread:
Port Range | |||||
Application | Start | End | Protocol | IP Address | Enable |
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. | |||
to | TCP UDP Both | 192.168.1. |
Lowell
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply