Posts: 2
Joined: 23.Nov.2004
From: Haarlem, The Netherlands
Status: offline
Hi all,
I'm having the following problem. From our LAN I need to contact a OWA 2003 (HTTP) server of another company. When I type in the URL it asks me for a username and password. It authenticates me, loads a couple of frames and than it ask for authentication again and again...
I have Cisco PIX as a permiter firewall. And I've installed a ISA 2004 server in Single NIC mode, for caching and HTTP filtering, as a proxy server.
The problem doesn't occur when I set up a session directly through the PIX firewall (skipping the ISA as a proxy).
Please Help. If you need additional information? Just ask.
Why only one NIC in the ISA firewall? The PIX doesn't have one NIC, and neither should the ISA firewall! Get that fixed and we should be able to solve this problem quick.
RE: Problem with contacting OWA 2003 through ISA 2004 s... - 4.Feb.2005 10:41:00 PM
Guest
I have the same problem with SBS from several different locations. That is, the problem is generic to ISA server and not just your installation. Still looking for the solution.
bump this subject back up. I have the exact same problem. the number of Nic's doesn't matter for this problem. Mine happens to have 2 and i have ironed out most of problems i have ran into except for this last one. I need to connect to OWA of another company and going strait to the PIX, no problem. Try and use the isa server (rule doesn't matter either, if i am authenticated, using sNAT or firewall client, if i am going through a rule that allows all users or only a group, if i filter outbound traffic or leave it wide open, or if the network rule is a NAT or route none of that matters) and you can't get more than the frame outline of OWA and maybe a "loading" screen but that is it and it will prompt you over and over for username/password until you finally get access is denied. all i can think of is that the isa server is automatically populating domain info into the logon request to the remote domain which of coarse the remote domain doesn't know. oh also authentication type doesn't matter.
Has someone tried username@remotedomain.com then password in the bellow form? Or remotedomain\username then password. I know it looks naive, but it might work.