• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TDP for Exchange and Firewall Routing Problems

BDMcGrew

ADSM.ORG Member
#1
Good morning... I'm using TSM 6.3 and TDP for Exchange 6.3.

I'm trying to backup Exchange 2010 over a VPN to a remote TSM server. The problem I have is this particular server in question is natted though the firewall an TDP wants to resolve it's address as being the public IP and won't connect to itself for the backups.

So, this brings me to two questions:

1) Is is possible, within the TSM Client/TDP Client to force the connections to a specific network interface? I can add another NIC to the machine that isn't natted and my problem would go away. I've searched high and low for this answer and have seen some vague queries on the subject about making Windows do the routing but nothing conclusive. I'm looking for a way to tell the TSM Client/TDP Client to use connection X in the server and just be done with it.

2) If the above is not possible, then is it possible to install the TSM/TDP client on a remote machine without Exchange installed (or a minimal install) and have it backup that way? Or, must the TSM/TDP client be installed on the same machine where all the mailboxes live?

I have proven this is a firewall routing issue because when the TSM Server is local on-site and everything is using addresses from the private network, everything works just fine!

Thanks for any help, TDP for Exchange isn't my strong point :)

-brian
 

moon-buddy

ADSM.ORG Moderator
#2
1) Is is possible, within the TSM Client/TDP Client to force the connections to a specific network interface? I can add another NIC to the machine that isn't natted and my problem would go away. I've searched high and low for this answer and have seen some vague queries on the subject about making Windows do the routing but nothing conclusive. I'm looking for a way to tell the TSM Client/TDP Client to use connection X in the server and just be done with it.
Yes, you can.

Bring up the second NIC and update the node settings on the TSM server:

As an example:

tcpclientport 1760 (or whatever you want)
tcpclientaddress 192.168.64.66

The tcpclientport is the LLA and the tcpclientaddress is the HLA (see 'help update node')

Caveat: the node should ALWAYS have the same IP address over the VPN link for this to work. I wonder if you can assign a static IP over a VPN link.
 

smajl

ADSM.ORG Senior Member
#3
As far as I noticed tcpclientport and tcpclientaddress are used only for informing TSM server that TSM Client scheduler is accessible on that ip:port. As moon-buddy wrote, add 2nd Nic and set up static network route on win server for TSM server IP via this new interface.
 

pmello

Active Newcomer
#4
I believe this is an DNS issue... Try to put the tsm address on hosts file (C:\Windows\System32\drivers\etc\hosts). Like this example:

192.168.0.15 tsm.pmello.local
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 7 23.3%
  • Keep using TSM for Spectrum Protect.

    Votes: 16 53.3%
  • Let's be formal and just say Spectrum Protect

    Votes: 4 13.3%
  • Other (please comement)

    Votes: 3 10.0%

Forum statistics

Threads
30,889
Messages
131,420
Members
21,194
Latest member
jamesmacd40