• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 588
  • Last Modified:

Port 1433 on SQL Server 2008 on Windows Server 2008

Hi,

I want to connect to SQL Server 2008 with SQL Management Studio.  The server is using 64 bit Windows Server 2008.  I have the Firewalls turned off on the server and the remote machine.  From a local machine on the network, I can connect fine (192.168.x.x).  However, from a remote machine, I cannot connect to the SQL database.  Remote connections are turned on (and connections work from the same network).

I suspect there is a problem with connecting to port 1433.  I have tried to telnet to port 1433 and it does not connect.  Once again, telneting on the internal network from a desktop to the server works.  I have disabled wirefalls, put in port 1433 exceptions...etc.

Any ideas?

thanks,
-Rocket
0
rocketmonkey
Asked:
rocketmonkey
  • 7
  • 5
  • 2
  • +3
3 Solutions
 
NJComputerNetworksCommented:
maybe you have to enable remote connections... something similar to this:  http://www.linglom.com/2009/03/28/enable-remote-connection-on-sql-server-2008-express/
0
 
rocketmonkeyAuthor Commented:
Thanks, but I have already done all that.  Local computers on the same network can connect fine.  It is computers outside the network from a public IP that cannot connect.
0
 
rocketmonkeyAuthor Commented:
Why wouldn't I be able to tenlet to port 1433 with the firewalls turned off??
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
TleeyahooCommented:
Be sure the SQL Browser service is running
0
 
dbidbaCommented:
Verify the port on which SQL is listening. Either through the GUI or in the registry. On 2005 it is in one of these two locations. It may be the same in 2008.

SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib\Tcp
SOFTWARE\Microsoft\Microsoft SQL Server\<<instance>>\MSSQLServer\SuperSocketNetLib\Tcp

I suspect that it is not 1433 if it will not accept a telnet connection and the path to the box is clear.
0
 
David ToddSenior DBACommented:
Hi,

Are you running a named instance?

Its likely that you have dynamic SQL ports. In that case, dollars to donuts you will not have the correct port open.

I suggest that you copy this number from the TCP dynamic Ports box to the TCP Ports box, clear the dynamic ports value and restart the server. Leaving it in the dynamic ports means the port is likely to change when the server restarts.

If you have older install media, look for SQLPing.exe. Copy this to the computer you are trying to connect from.

Don't forget that if trying to connect by name, the remote computer will need to resolve that name to an IP address.

Cheers
  David
SQL-TCP-Port.jpg
0
 
ralmadaCommented:
@dtodd, I guess you didn't read the link i've posted before. It's explaining the same thing.
Here it goes again:

http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_24072150.html 
0
 
David ToddSenior DBACommented:
@ralmada, point taken, although I was suggesting NOT changing to port 1433.

The SQL browser service sits behind that.

For named instances, there is a two stage connection - try port 1433, then the SQL Browser service replies with the correct port for the named instance, and hte client retries the connect on the supplied port.

This works around the LAN as there is no firewall in the path, but external client fail on the firewall.

HTH
  David
0
 
rocketmonkeyAuthor Commented:
I found out that my hosting provider is blocking port 1433.  I have tried to change the port to something else, but it still does not work.  I can atleast telnet to the new port now, but cannot connect via SQL Management Studio.  I wonder if it is a SQL 2008 thing?
0
 
ralmadaCommented:
Make sure you're using SQL authentication and not Windows authentication to connect.
 
0
 
rocketmonkeyAuthor Commented:
Thanks Ralmada.  I already have it set as SQL Authentication.
Also, in SQL Server Configuration Manager, I have the following:
IP1
TCP Dynamic Ports 0
TCP Port 60xx

IP2
TCP Dynmic Ports 0
TCP Port 60xx

IPALL
TCP Dynamic Ports 6060
TCP Port: blank
0
 
ralmadaCommented:
use the same port in all IP1, IP2 and IPALL
0
 
ralmadaCommented:
So I mean:
IP1 
TCP Dynamic Ports 0
TCP Port 6060

IP2
TCP Dynmic Ports 0
TCP Port 6060

IPALL
TCP Dynamic Ports 0
TCP Port: 6060

Open in new window

0
 
rocketmonkeyAuthor Commented:
Thanks ralmada, but it still does not work.  I restarted the MSSQL service.  I have set everything to 6060, but still cannot connect.  Windows Firewall is off.  I can telnet to port 6060 fine....
0
 
rocketmonkeyAuthor Commented:
Ok, so it looks like the way to connect from SQL Management Studio to a different port is with a comma after the IP and NOT a colon.  So, it would be:
x.x.x.x, 6060
NOT
x.x.x.x:6060

Ahhh!!  I don't think I have any hair left after this!! ;-)   Thanks for the help from everybody!!!!
0
 
rocketmonkeyAuthor Commented:
Thanks!!  Also, to add:
1. Make sure your hosting provider isn't blocking the port
2. Connect with a comma after the IP from SQL Management Studio
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 5
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now