1. When will your book be available in Singapore?

2. Problem with OWA.

I have the same problem as Scott McCarthy. I have recently installed ISA SERVER and followed your article on how to publish outlook web access. It asks you to login and validates your login. Then, it starts to display the frames for web access and eventually shows "page cannot be displayed" in both frames.

For the inbound, I have integrated on the listerner. On the OWA site, I have basic and integrated turned on the Exchange virtual directory (web site). The Exchange Server is on the SecureNAT portion.

Can you help?

3. Internal DNS Servers.

I follow your suggestions on forwarding my internal DNS to my ISP. I configure my hosts with public internet addresses in the DNS, though their interfaces actually are bind to private IP addresses. However, dynamic DNS updates my hosts with those private IP addresses. Hence each of my hosts has a private and a public IP address. Will it affect those from outside to reach my hosts?

Thank you for your assistance.

Tan Aik Seng
tanaikseng@executiveworkplace.com

------------------

1. Hmmm. That's a good question

2. Try is out the way I have it configured in the article. Do not force authentication on the external interface, and configure the Exchange 2000 server to use basic authentication within the domain.

Make sure your destination sets are configured correctly. When configuring the publishing rule, remember to send the orignal host header and also use an IP address right than an internal FQDN (this gets around problems you might have with internal domain name resolution)

3. Sounds like you have some major DNS issues. Check out my article over at www.brainbuzz.com later next week regarding issues you have to handle if you are going to use the same domain for internal and external network resources. There is also a good MS Whitepaper on DNS that is worth reading too.

HTH,

Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

Get it Here!

2. However, my clients are not able to access the web now. I checked, and discover that my Web Proxy Services of ISA is not working now. I tried to restart it, but I receive an error message that tells me the service could not be started.

The event viewer stated "The Microsoft Web Proxy service terminated with service-specific error 2147942402." What does it mean?

Your assistance will be greatly appreciated. How can I get the service to start again?

Tan

quote:

---

Originally posted by tshinder:
Hi Tan,

1. Hmmm. That's a good question

2. Try is out the way I have it configured in the article. Do not force authentication on the external interface, and configure the Exchange 2000 server to use basic authentication within the domain.

Make sure your destination sets are configured correctly. When configuring the publishing rule, remember to send the orignal host header and also use an IP address right than an internal FQDN (this gets around problems you might have with internal domain name resolution)

3. Sounds like you have some major DNS issues. Check out my article over at www.brainbuzz.com later next week regarding issues you have to handle if you are going to use the same domain for internal and external network resources. There is also a good MS Whitepaper on DNS that is worth reading too.

HTH,

Tom

---

It might be a couple of things:

1. The cache is corrupt. Delete the .cdat file for the cache and then go back and recreate it in the ISA Management console.

2. You might have deleted a Protocol Defintion that is being used in a rule. However, none of the services would start then, so its probably not that.

HTH,
Tom

------------------
Tom Shinder
http://www.isaserver.org/shinder/

Get it Here!