I am using SQL Server 2000. The local computer is XP the remote one is
W2003.
I am the admin of both machines.
I want to move data from the local server to the remote server over the
internet, using DTS.
Where and in what format should I declare to DTS the remote server.
Thanks,
Dan

In message <OseOdhTiEHA.1776 (AT) tk2msftngp13 (DOT) phx.gbl>, dan <dea (AT) deamon (DOT) com>
writes
Simplest way is to just add a connection for the remote server and
supply the IP address for the "name" and a SQL login username and
password.

You can use an alias created through the client network utility if you
want a nice way of specifying a friendly name, network library and port.
Then just use the alias name instead of the IP in your connection.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Darren,
Thank you very much for your reply.
Unfortunately I am new to SQL and DTS thus I would need more guidance.

I tried to find in Books Online HOW to do what you suggested but it's
hopeless. For instance the only "add a connection" topic is related to
English Query.
I would be very grateful if you could give me more details.
Thank you very much,
Dan



"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

Having never done this personally, I can only tell you what it sounds like
Darren is saying. Basically, go to Enterprise Manager, open the tree under
the Console Root folder, right click on SQL Server Group and select
New SQL Server Registration. Therein can you toy around with what
he's describing, I believe.



"dan" <dea (AT) deamon (DOT) com> wrote

In message <OwL204biEHA.644 (AT) tk2msftngp13 (DOT) phx.gbl>, dan <dea (AT) deamon (DOT) com>
writes
your DTS packages for you. You can enter the remote server IP as good as
anything else.


Once you have done this a few times, try opening and examining the
package that the wizard creates. For info, to add a connection you drag
and drop one of the connection "icons" from the toolbox.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Not quite as I am talking about a DTS connection, but if you haven't
already registered the server as John suggests then I would.

In message <2p1efhFem8btU1 (AT) uni-berlin (DOT) de>, John <jtaylor (AT) kmznet (DOT) com>
writes
--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Many thanks Darren and John.
I have done what John suggested. The registration was successful. However
when trying to connect I got the message: "I connection could not be
established to <IP address> . Reason: SQL Server does not exists or access
denied.
Well, the server exists and is running. I examined the Registration
Properties on the remote server and I see no reason for denial.
Which are the most frequent reasons for denial?
Many thanks again,
Dan


"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

Thanks again Darren.
re-examined the remote server settings. The login I am using is System and
Server Administrator and has all the permissions. What else could be wrong?


Many thanks, Dan


"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

In message <ug3AFahiEHA.1344 (AT) TK2MSFTNGP11 (DOT) phx.gbl>, dan <dea (AT) deamon (DOT) com>
writes
This is going to be the same issue as you had when registering the
server as suggested in the other branch of this thread, so fix one and
the other should fall into place.

That message says to me that you cannot find the server. If using a name
then it can mean the name resolution is not available. for example. If
using an IP address then are you using the correct IP/ Are you using the
publicly exposed IP of the server, for example there could be a routing
device in between that uses NAT for example. Firewalls can also block
the connection, both at a host and also at the port. By default SQL
server users TCP port 1433. Get confirmation of what port the remote SQL
Server is using.

Whilst the error says it may be "access denied", it doesn't really mean
a login failure. if it is one that then you will get an error message
back fairly quickly as opposed to teh 20-30s it takes for the current
message. The login failure error will also say something like "Login
failed for user xxxx...."


Start with the IP address of the remote server and a known username (and
password) for a SQL Server login, such as sa.

Can you get a connection to work?

Things to try-
Check that TCP/IP is your default network library, open the (SQL
Programs group) Client Network Utility on your box, and set the Network
Library order.

Starting talking to the network boys and find out if you have a firewall
locally, and if so are you allowed o make outbound connections on TCP
port 1433. Also check for a similar setup at the remote end.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Thanks again Darren, I appreciate your expertize and effort.
It's good to know it is not a login problem, so I can concentrate on the
network part of the problem.

I know for sure the IP address is OK as I am using it daily for FTP and
Terminal Services from the same computer.

Regarding your other hints, I am going to continue my tests tomorrow.

Perhaps I will have to look if there is not a Win2003 setting that creates
the problem.

Kind regards,
Dan



"Darren Green" <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote