Setting up SQL Server for Remote Clients

[Oliver Klozoff]

Hi,

I am having a hard time setting up an SQL Server 2000 Developer
Edition instance for remote clients. The instance is running well and
I can connect to it on the local computer. When I try connecting from
another computer using Enterprise Manager with the server's IP as the
instance name, I always get the usual "Specified SQL Server not found"
error. I have used Enterprise Manager many times to connect to local
and remote servers (which were set up by someone else obviously).

I used the client network utility on the client to make an alias for
this server and have it use the TCP/IP library for port 1433.

I understand that SQL Server listens on port 1433 for connections. I
have a firewall on the server and setup 1433 forwarding. But when I
use Enterprise Manager to try to register the server, the firewall
doesn't even show a connection attempt on port 1433 (it logs all
connection attempts).

When I use telnet to port 1433, the firewall logs the attempt but
there is still no connection, as if the server isn't actually
listening on 1433 at all. I can't seem to find any help on getting the
server listening, as if it supposed to be easy to set up so I don't
know what I'm missing. I guess I have the following questions:

1) Does anything have to be done on the server side to set it up to
listen for remote client connections?
2) How do I set the port on which the server listens in case I want to
change from 1433?
3) Does anything have to be set up on the client side other than using
the client network utility?
4) Why does Enterprise Manager not seem to even attempt a connection
on port 1433 when I try to register this server?

Any help is appreciated.

[Leythos]

In article <dd**************************@posting.google.com >,
kl*****@hotmail.com says...

Hi,

I am having a hard time setting up an SQL Server 2000 Developer
Edition instance for remote clients. The instance is running well and
I can connect to it on the local computer. When I try connecting from
another computer using Enterprise Manager with the server's IP as the
instance name, I always get the usual "Specified SQL Server not found"
error. I have used Enterprise Manager many times to connect to local
and remote servers (which were set up by someone else obviously).

I used the client network utility on the client to make an alias for
this server and have it use the TCP/IP library for port 1433.

I understand that SQL Server listens on port 1433 for connections. I
have a firewall on the server and setup 1433 forwarding. But when I
use Enterprise Manager to try to register the server, the firewall
doesn't even show a connection attempt on port 1433 (it logs all
connection attempts).

When I use telnet to port 1433, the firewall logs the attempt but
there is still no connection, as if the server isn't actually
listening on 1433 at all. I can't seem to find any help on getting the
server listening, as if it supposed to be easy to set up so I don't
know what I'm missing. I guess I have the following questions:

1) Does anything have to be done on the server side to set it up to
listen for remote client connections?
2) How do I set the port on which the server listens in case I want to
change from 1433?
3) Does anything have to be set up on the client side other than using
the client network utility?
4) Why does Enterprise Manager not seem to even attempt a connection
on port 1433 when I try to register this server?

Any help is appreciated.

1433 is for data, 1434 is for communications. If you open your firewall
to allow 1433 and 1434 you are going to get hacked. At the very least,
you need to only open the ports to fixed IP addresses of your users
(their fixed internet address).

You need to force them to use a VPN to connect, even a simple PPTP
tunnel is better than opening the ports to the entire world.

You should also tell us what firewall - it would be easier to tell you
what rules to create.

--
--
sp*********@rrohio.com
(Remove 999 to reply to me)

[Oliver Klozoff]

Thanks for the reply.

The firewall is a Netgear FVS318. I understand that leaving the server
on the default ports is not a good idea so I would also like to know how
to change that and lock things down more. But for now I can't seem to
connect to it at all even on the default ports so I am not convinced
that it is just a firewall issue, it still doesn't seem to be listening
on 1433/1434 (I have opened 1434 as well).

As for the VPN idea, I have not looked into that at all yet, would it
still be possible to use DB tools like DTS if the clients are forced to
VPN first?

Thanks again.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!