MSDTC cross domain fails

Question

Post reply

MSDTC cross domain fails

Johan Bijnens

SSC Guru

Points: 135376
More actions
June 23, 2005 at 12:20 am

#89626

I cannot find the reason why I cannot run this distributed transacion cross domain.
I've enabled the w2k3 registry key, disabled my xp-sp2 firewall for this test, ...
still "unable to enlist...)
Johan

Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 1

I'm no expert here but have the proper 'trust' relationships and permissions been set up ?

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

K. Brian Kelley SSC Guru Points: 114642 More actions · Answer 2

Can you run it in the same domain?

K. Brian Kelley
@kbriankelley

Yelena Varshal SSC-Dedicated Points: 34286 More actions · Answer 3

Hi,

we had a discussion here some time ago on this topic, I am getting this very error a lot between Windows 2000 and Windows 2003 servers, everything is in the same domain. Other people too. See

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=183398#bm185242

The script running for example from Windows 2003 server SQL 2000 has no problems connecting to Windows 2000 servers, can connect (run distributed transaction) to one Windows 2003 server, can not do disributed transaction to itself (2003 server) and can not connect to another Windows 2003 server.

Someone said that if he is running only Windows 2003 servers with SQL Server 2000 and installed SP1 for Windows 2003 then the error go away.

In my particular case in the environment with different OS versions I tested that if I run my script from Windows XP workstation with SQL Server CTP 2005 towards Windows 2000 and Windows 2003 servers with SQL Server 2000 it works.

So it may be not a domain problem but different OS of the servers

Yelena

Regards,Yelena Varsha

HSM_DBA Right there with Babe Points: 771 More actions · Answer 4

Had similar problems before. If you haven't tried the following, I would try these things first:

1 - Ping both the servers from the other (domain or name resolution problem).

2 - Make sure MSDTC is started and all the other related services are started (e.g. Network DDE or something, I can't remember off-hand).

3 - Use the DTCPing utility. Gives you a little detail on where the failure is.

4 - Check the firewall and if certain ports (I think it is 135, I could be wrong) is enabled.

5 - If the servers are not on the same domain, then check to see if the default gateway is correct.

My 2 cents.

Johan Bijnens SSC Guru Points: 135376 More actions · Answer 5

thank you all for your replies.

MSDTC is working fine when in the same domain.

Now I'm focussing on the VLANs to check if there are port issues. (I'm not a network expert, but our network guy is very helpfull &nbsp

If that VLAN does not come up with something, SP1 on the W2k will be tested.

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

HSM_DBA Right there with Babe Points: 771 More actions · Answer 6

Resolved a similar issue of "across domains" just a couple days ago. The default gateway on one of the servers was incorrect.

Johan Bijnens SSC Guru Points: 135376 More actions · Answer 7

The issue occurs when I plug one of the servers to another vlan. I'll check on the impact of the gateways.