Setting Up SQL Server For Remote Clients

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.