All very good news!

I got it.... there are multiple IP address settings on the 'IP ADDRESS' tab of the TCP/IP properties in Server Manager. I had to change all of them (except the loopback) including 'IPAll' to not use dynamic (clear the zero) and use 1433, not just the IP that NAT's from my public IP.



WOOT! I connected to my SQL Server with a strataframe app over the web, life is good. That was the last piece to make sure worked. Thanks! Hopefully someone else may find this useful someday, thanks for the help.



Now I just have to encrypt the stream like Ben said.



Also, I was able to connect to just the public IP address once I made this change.






Keith Chisarik

I was just sitting here thinking though...if you are exposing this server publically you may have an issue with a named instance.  Don't hold me to that, but it could cause you more heart-ache than being the default instance on the server which would be just an IP and a port externally versus including the name.  This would be straight TCP/IP and should be a little more smooth to implement.  Having the named instance could pose a problem.

No, it isn't odd.  You just have a named instance on the server which is fine.  You can install SQL Server to be the default instance which doesn't require a name at the end, but this will work just fine

I have to use IP\SERVERNAME even in Management Studio internally.



I dont know if that is odd, I assume it is since you said I should have to.

Keith Chisarik

I'm on it.........




Keith Chisarik

That's more than likely the issue.  If you can get a telnet to work, then you should be good.

I cannot. I guess that means I need to recheck my firewall settings?




Keith Chisarik

Can you telnet to the server?

telnet PUBLICIPADDRESS 1433

Still no dice



I already made sure my server is listening on a static port (1433) instead of the default dynamic according to this article.



http://msdn2.microsoft.com/en-us/library/ms177440.aspx

Keith Chisarik