![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We are using MSDTC to perform distributed transactions between our application server (A) and a database server (B). Application server is running windows 2000 with IIS 5 while database server is running winnt 4 SP6 with SQL 7.0 SP3. These severs are separated by a firewall, but no NAT. To test the functionality of the application we opened all ports on the firewall (from the application server to the database server and viceversa). The problem is with MSDTC. Infact the application works fine, except when a transaction is performed to update records on the db. We tested for connectivity with Dtcping.exe with no errors and a full connectivity trace between the two servers. The application works fine if we put the db on a database server in the same LAN of the application server. Any hints appreciated, regards, pacho baratta |
#3
| |||
| |||
|
|
-----Original Message----- I believe you need NetBIOS name resolution for DTS to work correctly, so you try either WINS or LMHOSTS that cover both sides of the FW. -- Darren Green http://www.sqldts.com "Pacho Baratta" <p.baratta (AT) datasiel (DOT) net> wrote in message news:01ed01c3d9ae$3c43d080$a001280a (AT) phx (DOT) gbl... We are using MSDTC to perform distributed transactions between our application server (A) and a database server (B). Application server is running windows 2000 with IIS 5 while database server is running winnt 4 SP6 with SQL 7.0 SP3. These severs are separated by a firewall, but no NAT. To test the functionality of the application we opened all ports on the firewall (from the application server to the database server and viceversa). The problem is with MSDTC. Infact the application works fine, except when a transaction is performed to update records on the db. We tested for connectivity with Dtcping.exe with no errors and a full connectivity trace between the two servers. The application works fine if we put the db on a database server in the same LAN of the application server. Any hints appreciated, regards, pacho baratta . |
#4
| |||
| |||
|
|
lmhosts is already correctly compiled. -----Original Message----- I believe you need NetBIOS name resolution for DTS to work correctly, so you try either WINS or LMHOSTS that cover both sides of the FW. -- Darren Green http://www.sqldts.com "Pacho Baratta" <p.baratta (AT) datasiel (DOT) net> wrote in message news:01ed01c3d9ae$3c43d080$a001280a (AT) phx (DOT) gbl... We are using MSDTC to perform distributed transactions between our application server (A) and a database server (B). Application server is running windows 2000 with IIS 5 while database server is running winnt 4 SP6 with SQL 7.0 SP3. These severs are separated by a firewall, but no NAT. To test the functionality of the application we opened all ports on the firewall (from the application server to the database server and viceversa). The problem is with MSDTC. Infact the application works fine, except when a transaction is performed to update records on the db. We tested for connectivity with Dtcping.exe with no errors and a full connectivity trace between the two servers. The application works fine if we put the db on a database server in the same LAN of the application server. Any hints appreciated, regards, pacho baratta . |
#5
| |||
| |||
|
|
lmhosts is already correctly compiled. |
![]() |
| Thread Tools | |
| Display Modes | |
| |