MSDE 2000 and enterprise (enterprize) manager remotely

Hey all.
Can you use enterprise manager to connect to an MSDE 2000 version of
SQL Server across the internet? Ignoring firewalls (server was placed
outside firewall to see if thats where the connection problem was)
We get the 'SQL Server does not exist or access denied
ConnectionOpen(Connect())' error when trying to connect to a clients
database on their server over the internet. However, everything looks
ok and I can vpn into their machine and connect to the server using
enterprise manager on a terminal service session on their servers.
This in itself is a pain and we would rather have their server
registered in our enterprise manager.
Does the same answer apply if the server was an installation of SQL
Server standard edition?Licensing questions aside:
Yes. Note that MSDE doesn't by default listen to any netlibs. If you can
connect to the same MSDE after VPN, then this shouldn't be an issue. I
suggest you, on the client, make sure that TCP IP is at the top of the list
in Client Network Utility. Also try connecting using IP address. And as for
port numbers,
The IP netlib uses 1433 for a default instance.
The IP netlib uses 1434 for the port resolution query and whatever the
instance picked at the first startup for the actual data traffic.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Karl Rhodes" <karl.rhodes@.keywave.com> wrote in message
news:7cee27c2.0402110245.64167e99@.posting.google.com...
> Hey all.
> Can you use enterprise manager to connect to an MSDE 2000 version of
> SQL Server across the internet? Ignoring firewalls (server was placed
> outside firewall to see if thats where the connection problem was)
> We get the 'SQL Server does not exist or access denied
> ConnectionOpen(Connect())' error when trying to connect to a clients
> database on their server over the internet. However, everything looks
> ok and I can vpn into their machine and connect to the server using
> enterprise manager on a terminal service session on their servers.
> This in itself is a pain and we would rather have their server
> registered in our enterprise manager.
> Does the same answer apply if the server was an installation of SQL
> Server standard edition?