Re: How can I verify that the sqlserver on my development is accessable from internet

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@xxxxxxxxxxxxx> skrev i meddelandet
news:eOtYGIfgHHA.4916@xxxxxxxxxxxxxxxxxxxxxxx
"Nutshell" <nospam@xxxxxxxxxx> wrote in message
news:%239FNk8bgHHA.596@xxxxxxxxxxxxxxxxxxxxxxx

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



.

Relevant Pages

  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL 200 Dev edition on workgroup will not connect
    ... I have been using sql server for about 8 years but mainly working with sql 2000. ... know your experience level with SQL Server and yes, sometimes things being messy but letting a SQL Server instance to accept remote connections and uninstalling it are generally straightforward tasks to perform. ... I suggest you to check for the dynamic port number that your SQL Server graps. ... Write down the port number in the "TCP Dynamic Ports" property and then run a Command Prompt and see if this port is bening listened. ...
    (microsoft.public.sqlserver.connect)