Hello Steve,
I'll guess that the SQL Server need to use a static port?
1. From SQL Server Network Utility I'll see that port 1433 is default.
2. In the registry the settings looks like dynamic port allocation
3. The log displays:
2007-04-19 07:49:42.21 server SQL server listening on 192.168.0.6: 1433.
2007-04-19 07:49:42.34 server SQL server listening on 127.0.0.1: 1433.
2007-04-19 07:49:42.34 server SuperSocket Info: Bind failed on TCP port
1433.
2007-04-19 07:49:42.60 server SuperSocket Info: Bind failed on TCP port
1433.
I have tested to change the port to 1500, but I get the same bind error,
"Bind failed on TCP port 1500".
I have both SQL Server 9, and SQL Server Express on this machine. Is that
the problem?
Thanks!
"Steve Thompson" <stevethompson@nomail.please> skrev i meddelandet
news:eOtYGIfgHHA.4916@TK2MSFTNGP06.phx.gbl...
[quoted text, click to view] > "Nutshell" <nospam@nospam.com> wrote in message
> news:%239FNk8bgHHA.596@TK2MSFTNGP05.phx.gbl...
>
>> I'm trying to figure out if it's possible to reach the database on my
>> development machine from the outside (internet). To test this I'm trying
>> to connect to the database from the development machine by using my
>> public IP address. I also opned port 1433 in my firewall.
>>
>> Is there any other ports I need to open?
>
> You'll want to give this a read (and some of the related links):
>
http://support.microsoft.com/kb/823938/en-us >
>> How can I verify that the sqlserver on my development is accessible from
>> internet?
>
> You should be able to use Query Analyzer or OSQL as a basic test
> mechanism...
>
> Steve
>