I have a SQLServer 2000 under Windows 2003.  I access that server?s
databases from another computer (laptop) with Enterprise Manager
through my LAN  (I use Windows Authentication option in the
registration entry).

I would like to do the same from home (access database through TCP-IP).

How ?

Note:  My SQLServer has a static IP address, no firewall.

(I know it is easy, but don?t have time to look up tutorials)

---

Clarification of Question by edullega-ga on 07 Apr 2004 11:49 PDT

navjotsingh-ga

That?s the first I tried? It saids ?SQL Server does not exist?  
I?m sure about the user and password.

dine-ga

I?ve been doing that before, but that is not optimal for security
reasons.  That is way I need to do it using the SQLServer resources.

creation-ga

MySQL Server is connected to internet using a DSL connection.  The
router is a Netopia Cayman 3346.  His DHCP server is disabled cause
I?m using several static Ips.

So, my SQLServer have a fixed static IP.  The IP of my server is
different of my router IP.  I can ping my SQLServer IP anywhere over
the Internet.

I have not any pinhole in my router and I suppose it is no need. My
SQLServer PC is also a webserver, and I can browse my site anywhere
even without any pinhole for 80 port in the router.  Do I need a
pinhole for 1433 port ?

I tried creating a entry from ?SQL Server Client Network Utility? Then
I selected it at Enterprise Manager when I create a new entry? but I
get the message ?SQL Server does not exist?.

Thank you all for your answers.

1. Install SQL Enterprise Manager at laptop.
2. After Installation, from the Program Menu, open the Enterprise
Manager interface.
3. In left hand side pane, right click on the "SQL Server xxx" link.
4. Choose SQL Server Registrtion..
5. follow the wizard.. surely, it will ask you for the Server IP and
the username/password to that server.

it's that simple

Easiest thing to do would be to use Remote Desktop, this will bring
your whole server desktop to the machine your at! - This is extremely
useful for server management if you have many things to keep an eye on
like IIS, SQL, Exchange etc.

Hope this helps.

I

I need more information to answer this correctly. It's not hard, and
I'm happy to step you through it.

Firstly, you need to make sure you have all of the necessary TCP ports
routed to your SQL Server. These ports will vary depending on exactly
what you want to do. HOw to do this will also depend on the
firewall/router that you're using.

If you just want to access the database with SQL Enterprise manager,
you can enter the DNS name or IP address in the management tool when
you add the new server.

Using Remote Desktop is also a valid option.. once again, it depends
on what you want to do.

Let me know..

navjotsingh-ga

That?s the first I tried? It saids ?SQL Server does not exist?  
I?m sure about the user and password.

dine-ga

I?ve been doing that before, but that is not optimal for security
reasons.  That is way I need to do it using the SQLServer resources.

creation-ga

MySQL Server is connected to internet using a DSL connection.  The
router is a Netopia Cayman 3346.  His DHCP server is disables cause
I?m using several static Ips.

So, my SQLServer have a fixed static IP.  The IP of my server is
different of my router IP.  I can ping my SQLServer IP anywhere over
the Internet.

I have not any pinhole in my router and I suppose it is no need. My
SQLServer PC is also a webserver, and I can browse my site anywhere
even without any pinhole for 80 port in the router.  Do I need a
pinhole for 1433 port ?

I tried creating a entry from ?SQL Server Client Network Utility? Then
I selected it at Enterprise Manager when I create a new entry? but I
get the message ?SQL Server does not exist?.

Firstly you will need to determine if you have access on port 1433.

I use telnet. Just telnet to port 1433 and see if it connects, it wont
do much but will indicate if there is a connection or not. If not, you
may want to check your router.

Now, with SQL Server 2000 it can automatically determine a different
port to use, that is other than 1433. This can sometimes cause
problems if you are behind a firewall, as it uses a different port
(1434) to resolve the port the subsequent connections are going to
use.

Anyway, I avoid using the dynamic port allocation by forcing the
connection to 1433. The is done when setting up an alias in the Client
Network Utility. And selecting the option underneath the servername.

Now when you go and connect to SQL server, remember that you will need
to use SQL Server authentication rather than Windows Authentication.

I hope it helps.

Ok, we are in the way.

I'm forcing the use of 1433 with the Client Network Utility as you suggest.

Again, there is no firewall.

I telnet the port 1433 in the IP of my server and I got the message
?Connection can?t be established?.

Who do I open/close the 1433 port in a Windows 2003 server?

Note: My Cayman Router has almost his default configuration.

Sorry about the delay in providing an answer
As you have said,

"I telnet the port 1433 in the IP of my server and I got the message
?Connection can?t be established?."

What this indicates to me is that something between you and your
server is stopping you accessing port 1433, either your router, or
something else.

But first I would check, and this should work, telnetting to the same
server on port 1433 from your LAN.

Now a couple of other things to check.
On the server, open the Server Network Utility, check that tcp/ip is
in the enabled column, it should be fairly easy to see.  If not,
enable it.

Next click on TCP/IP in the enabled column and click properties.  That
allows you to set the default port.  So check that its 1433 and make
sure the server isn't hidden (a checkbox next to the port number).

On windows 2000, and presumably 2003, there is a Routing and Remote
Access feature(found in Administrative Tools). You might also want to
check if its running, and/or forcing any restrictions.

Both of the above suggestions will stop you from connecting via tcp/ip
to the server.

Another test:
On a computer on the LAN, using the Client Network Utility setup an
Alias for the server only using TCP/IP, call it something unique, or
at least different from the server name.

Then try and connect to the server using that unique name. This will
force a TCP/IP connection and you will know if it is a setting on the
server or else where that is causing the problem.

By default, LAN connections to SQL Server are done using Named Pipes,
this is why I suggest setting up a new Alias under the Client Network
Utility on the LAN to test TCP/IP connectivity to the Server.

Good luck.