DTC Through Firewall. Port Limitation Not Working
- From: Ross Mason <RossMason@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Jun 2009 08:06:06 -0700
Hi I am experiencing problems limiting the dynamic ports used by MSDTC. The
problem we are seeing is on a production box that we are trying to deploy to.
I cannot replicate the issue we are seeing on the live boxes in any test
scenario. The production servers live in an environment which has some very
severe change managing policies and the servers are separated by a firewall.
We have been trying to limit the ports required for DTC through the
Component Services Snap-In >> Default Protocols. After a restart we have then
been using Microsoft Network Monitor to monitor traffic when using the DTC
ping tool. It currently appears that whilst one of the servers is correctly
assigning out ports from the pool we setup the the other server does not seem
to see the ports we have setup and is still using ports in the low 1000's
rather than 5000-5100 as per our setup. I cannot explain this as all my tests
on test boxes work first time after a restart.
There is friction with my client at the minute as these are production boxes
and every server restart has to be requested through change management and
takes a day or two to organise. We are also running behind a deadline to get
this application up and running so the pressure is really on.
I cannot really ask my client to restart the servers any more without a good
reason or without making some solid configuration change that we are almost
certain will work.
I am really clutching at straws for ideas now and am at a loss as to why our
setup isn't working on the production boxes. So what I really need to know is
why would the ports setup in the DCOM config be ignored?
.
- Prev by Date: Re: IIS, SQL 2000 & XP's Firewall
- Next by Date: Re: IIS, SQL 2000 & XP's Firewall
- Previous by thread: Using SQL2000 JDBC driver with SQL2005, Database in SQL2000 mode
- Next by thread: MDB on shared drive via UNC
- Index(es):
Relevant Pages
|
Loading