Hi all,
We're having a strange problem getting the T-Stats connection to Tessitura (in regards to creating and using Tessitura lists) to work from a remote site. The site is remote in regards to being a couple blocks away from the Opera House, although they're connected by an Opt-E-Man circuit (essentially a point-to-point, private fiber connection) and are therefore just a different IP segment on our internal network. For some reason, T-Stats can't connect to the named SQL instance on our Live Tessitura server. (But Tessitura works fine at this site.)
Here's the kicker: when I run the Microsoft Port Query tool from the remote site, it shows that UDP port 1434 is 'filtered' on our Live Tessitura server (as well as to one other SQL server we have on our network). However, that port is 'listening' on all the other SQL servers we have here at the Opera House (and we have a bunch!). So that rules out firewalls and the circuit itself (since they're on the internal network, the firewall is configured for unrestricted access anyhow). As far as I can tell, there is no IPSEC policy active.
Any ideas? For the life of me, I can't figure out why the Live server isn't allowing T-Stats access. Oh, and note also that T-Stats connects fine to Tessitura from within the Opera House.
Thanks in advance for your thoughts!
Best,
Paul
There are a ton of variables here and I don't know what your whole network layout is here but I assume the private fiber still comes in to a separate port on your firewall. If so you might want to check the MTU on it (on both ends). It may be that the MTU is set too small and the packets are getting fragmented. I have seen this happen over a VPN connection before with some DB apps. Hope this is helpful.
-Rich
From: Paul Goetz <bounce-paulgoetz3560@tessituranetwork.com>Sent: 4/12/2010 5:49:02 PM