Discussion Locked

Exchange Server client through ISA

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Recently we have moved to ISA Server from Proxy Server 2.0. Everything appears to be running great except for one thing, our connection between Outlook and Exchange Server. All our workstations connect to Exchange Server 5.5 located at our ISP. We use the lmhosts file to configure the Exchange client so Outlook can connect. I have configured the packet filter for port 135, 1225 and 1226. I searched TechNet and only found one article, "XADM: Setting TCP/IP ports for Exchange and Outlook Client Connections Through a Firewall". The article has you making registry changes on the client and opening the above ports. However, our workstations do not have the registry key that the article talks about. HELP I NEED MY EMAIL!

9 replies

by dkane

My understanding is that these keys are on the server not the client. Our problem is connecting to the Exchange Server located at the ISP through our ISA firewall. I'm starting to think this is more of the ISPs problem and not mine. Let me know if you think of anything else.

by khahina

You must create this key.
It's the case of lot advanced keys. The key does not exist if you use the initial config. and default value .
nb : Take a look in Ressource kit tools

by dkane

My understanding is that these keys are on the server not the client. Our problem is connecting to the Exchange Server located at the ISP through our ISA firewall. I'm starting to think this is more of the ISPs problem and not mine. Let me know if you think of anything else.

by khahina

You must create this key.
It's the case of lot advanced keys. The key does not exist if you use the initial config. and default value .
nb : Take a look in Ressource kit tools

by dkane

My understanding is that these keys are on the server not the client. Our problem is connecting to the Exchange Server located at the ISP through our ISA firewall. I'm starting to think this is more of the ISPs problem and not mine. Let me know if you think of anything else.

by scottsman

you may have to make a site rule that shows the internal clients the exchange servers IP

for info on how to do this e-mail me or try www.isaserver.org under lessons

it sounds like ISA isnt passing the request.

by dkane

We decided to give up on this quest and switch over to NAT instead of ISA.

This discussion is closed to new replies.