DTS across domains

[markSaunders]

Any advice on this one:

I have opened up the firewall on the destination server for a specific IP address of the source server on port 1433 in order to allow a DTS package to update a destination table with the contents of the source table.

To test the connection is permitted I then created a DTS package on the source machine and have attempted to create a connection that uses the
Data Source: MS OLE DB provider for SQL Server
Server: contains the destination IP address
Uses SQL server login: a login/user that can select/update/delete etc. on one table in the database (i've actually tried the same with the sa password).

after entering the correct password and attempting to refresh i get the

Login failed for user 'testUsr'

if i try an incorrect destination IP address i get a message indicating that the server cannot be contacted as would expected so this leads me to think that the connection is getting through the firewall, but not into SQL.

i can connect when i'm in the same domain using the user as above but not when i've come through the firewall -

have i missed something obvious?

any ideas?

any help appreciated!

cheers
m
Mark Saunders

 

[markSaunders]

oops...

using SQL2000, Win2k Mark Saunders

 

[wilk]

AS a inital response I would first of all set up a new user on the machine you want to connect to as the same user you are logging in as, giving the user admin rights on the machine. Then you can use winnt authentication. A big test to see if you have the right rights on the machine you wish to connect to is if you can go to the start menu and run the cmd \\ip address\c$ if you can connect like this you have a greater chance of being able to connect to it.

I have used this approach with win2k machines before using RAS to dial and connect to remote computers and on a seperate domain and even connecting to msde machine.

Not sure this helps.

 

[markSaunders]

thanks for the advice but the problem was that the firewall had been opened to the correct ip, but some firewall setting that then directed ip address locally (back into the DMZ) was incorrect - consequently the connection was being made to SQL, but unfotunately to the wrong SQL box!!

now sorted but thanks.
Mark Saunders