![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all, SQL Server 2000 Enterprise SP3a, Win 2K3 I'm having a problem in my production environment that is not happening in QA. I am using HTTP access to connect to the server. In QA this is working fine. Windows Auth is on, the user logs in, and OWC connects to AS using the users credentials. But in Production, this is failing. It only works under anonymous access. The only difference is that production has a firewall with only ports 80, 443 open. Any ideas ??? TIA, Brian |
#3
| |||
| |||
|
|
And that is in-fact your problem. You are using windows authentication which needs more than port 80 and 443. Look at the IIS docs for what ports you need open. This is a pure IIS issue. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Codecommando" <Codecommando (AT) discussions (DOT) microsoft.com> wrote in message news:80076E18-E800-48EB-B89D-2B56DA6DA338 (AT) microsoft (DOT) com... Hi all, SQL Server 2000 Enterprise SP3a, Win 2K3 I'm having a problem in my production environment that is not happening in QA. I am using HTTP access to connect to the server. In QA this is working fine. Windows Auth is on, the user logs in, and OWC connects to AS using the users credentials. But in Production, this is failing. It only works under anonymous access. The only difference is that production has a firewall with only ports 80, 443 open. Any ideas ??? TIA, Brian |
#4
| |||
| |||
|
|
Thanks Dave, I had a feeling that was the problem. One more thing, I'm looking through the docs for IIS and I can't find anything on the required ports for Windows Auth. Can I ask for your assistance one more time (Probably right in front of my eyes, I've been looking at this for so long!!)? Thanks, Brian "Dave Wickert [MSFT]" wrote: And that is in-fact your problem. You are using windows authentication which needs more than port 80 and 443. Look at the IIS docs for what ports you need open. This is a pure IIS issue. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Codecommando" <Codecommando (AT) discussions (DOT) microsoft.com> wrote in message news:80076E18-E800-48EB-B89D-2B56DA6DA338 (AT) microsoft (DOT) com... Hi all, SQL Server 2000 Enterprise SP3a, Win 2K3 I'm having a problem in my production environment that is not happening in QA. I am using HTTP access to connect to the server. In QA this is working fine. Windows Auth is on, the user logs in, and OWC connects to AS using the users credentials. But in Production, this is failing. It only works under anonymous access. The only difference is that production has a firewall with only ports 80, 443 open. Any ideas ??? TIA, Brian |
![]() |
| Thread Tools | |
| Display Modes | |
| |