Microsoft Transporter Suite

[jebenson]

Hello all,

I am migrating from Lotus Domino 6.5.x to Exchange 2007. I am trying to use the Microsoft Transporter Suite (MTS) for Lotus Domino, but I am having trouble. I have installed MTS on the machine that runs CAS, Mailbox and Hub Transport. I also have the Lotus Notes client installed on that machine, and the client can connect to the Lotus Domino server with no problem. When I run MTS it automatically creates a directory connector between the Exchange server and the IP address of the Lotus server. I don't have to put in the IP address, MTS finds it automatically. When I try to get a list of users from the Lotus server, it fails with this message: "Server 'server.domain' is not found. Please check the server name." The error message has the correct server name and domain, so it is obviously resolving the IP address correctly.

I cannot find any resources to help get this thing running properly. Do I need to open some ports on my firewall, between the LAN and DMZ? The Lotus server on the DMZ also hosts a website, so the firewall is set to allow connections to ports 80 and 443, from LAN to DMZ and from DMZ to LAN. I read somewhere that MTS uses port 443 to connect to the Domino server, but this doesn't seem to be the case as I have this port open but still no connection. I also enabled port 1352 both ways, which is what Lotus Notes uses. Still no luck.

Any ideas? Let me know if you need any further information to help with this.

Thanks,
jebenson

I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

Arrrr, mateys! Ye needs ta be preparin' yerselves fer Talk Like a Pirate Day!

 

[joepc]

i would first confiure your lan - dmz / dmz - lan rules allow just the lan server and the dmz server to communicate on all ports before i spent a whole lot of time troubleshooting. if security is a concern i would block wan traffic to the dmz server first.

if that resolves the issue you could use a packet capture utility to see what ports are actually being used. as far as i know microsoft has very detailed documentation on what ports all of there programs use.