dbTalk Databases Forums  

HTTP access to Analysis Services failing

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss HTTP access to Analysis Services failing in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Codecommando
 
Posts: n/a

Default HTTP access to Analysis Services failing - 07-26-2005 , 10:32 AM






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

Reply With Quote
  #2  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: HTTP access to Analysis Services failing - 07-26-2005 , 11:39 AM






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

Quote:
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



Reply With Quote
  #3  
Old   
Codecommando
 
Posts: n/a

Default Re: HTTP access to Analysis Services failing - 07-26-2005 , 01:38 PM



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:

Quote:
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




Reply With Quote
  #4  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: HTTP access to Analysis Services failing - 07-27-2005 , 11:15 AM



A quick search of KB articles
http://search.microsoft.com for:
"ports used for windows authentication"

Hit #6 is:
http://support.microsoft.com/default...b;en-us;832017
Look at net logon in particular, but there may be others.
The best way is to enable packet logging on your firewall and see what
actual traffic moves between them if you enable everything.
--
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

Quote:
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






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.