All users who attempt to access the server end up failing because they all end up logging in as the same users.

We spoke to the manufacturer, and their claim was that since the server is being published via NAT, that thier server cannot differentiate one user from another.

I guess I'll ask the question in two ways.

1) Has anyone else got this product working with ISA

2) Is there a way to have external clients reach the internal box (chatspace) with their actual IP addresses vs the IP of the ISA box (NAT).

Our setup has all been done through Server Publishing.

Sounds like you're going to need to configure the machine as a Firewall Client and get up to speed on how to configure a wspcfg.ini file to make this work.

HTH,
Tom

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

Get It Here

Thanks for the suggestion, but I was hoping to not go the old PROXY route.

I was actually able to resolve the issue after a bit of trial and error.

It turns out that CACHE was the problem. I guess I never assumes that Cache would work for both internal and external requests, but it seems that since Cache was turned on, the cleints would get confused.

I'm still continuing to research this, because I still don't understand how Cache fits in, but if anyone has any feedback, please chime in!

Ha! That's what I get for trusting the vendor

You can create a Routing Rule so the requests destination for the internal server are not cached.

HTH,
Tom

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

Get It Here