|
Home > Archive > MS SQL Server > October 2006 > SQL Server 2005, SBS 2003 Premium
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server 2005, SBS 2003 Premium
|
|
| Timothy Peer 2006-10-28, 7:14 pm |
| Yesterday I upgraded an SQL Server 2000 to 2005 (rolling upgrade). When 2005
was installed, I selected the Windows Integrated Securityand subsequently
changed security to Mixed Mode from the Management Tool.
Problem: .NET ASPX pages which reference a 2005 database are not
authenticating. The pages are coded to use the SA account and password
inherited from the 2000 environment (I know it isn't the right way to do it)
which under 2000 worked fine.
I found various discussions related to the ASPNet and the IIS_WAP? user (I
don't have an IIS_WAP user or group in AD).
What I need: ASPX pages which are accessed via unauthenticated accounts via
the internet (which are hard-coded to use the SA password.)
ISA 2003 is installed and configured.
Exchange is configured on this system, OWA and Sharepoint.
Questions: What is my configuration missing to no permit unauthenticated
users to access the SQL Server database (1433 is open and enabled)? Should I
uninstall and reinstall IIS 6.0 or run the ICW?
Please advise and thanks!
Tim Peer
| |
| Arnie Rowland 2006-10-28, 7:14 pm |
| The default installation of SQL Server 2005 is closed to net traffic.
You will need to use the SQL Server Configuration Manager to enable the
TCP/IP protocol.
Then using SSMS, Server Properties, Connections, check 'Allow Remote
Connections'.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Timothy Peer" < TimothyPeer@discussi
ons.microsoft.com> wrote in message
news:8CE471BB-1AA5-4A05-A98A- 4E2B27760FA1@microso
ft.com...
> Yesterday I upgraded an SQL Server 2000 to 2005 (rolling upgrade). When
> 2005
> was installed, I selected the Windows Integrated Securityand subsequently
> changed security to Mixed Mode from the Management Tool.
>
> Problem: .NET ASPX pages which reference a 2005 database are not
> authenticating. The pages are coded to use the SA account and password
> inherited from the 2000 environment (I know it isn't the right way to do
> it)
> which under 2000 worked fine.
>
> I found various discussions related to the ASPNet and the IIS_WAP? user (I
> don't have an IIS_WAP user or group in AD).
>
> What I need: ASPX pages which are accessed via unauthenticated accounts
> via
> the internet (which are hard-coded to use the SA password.)
>
> ISA 2003 is installed and configured.
> Exchange is configured on this system, OWA and Sharepoint.
>
> Questions: What is my configuration missing to no permit unauthenticated
> users to access the SQL Server database (1433 is open and enabled)? Should
> I
> uninstall and reinstall IIS 6.0 or run the ICW?
>
> Please advise and thanks!
>
> Tim Peer
| |
| Timothy Peer 2006-10-28, 7:14 pm |
| Arnie,
Thanks for the quick response. TCPIP protocol is enabled and have since
disabled Local and Remote access via the Surface Configuration Utility. I
will restart the services and start again and toggle TCPIP back to Local and
Remote to see if this helps.
Also, I am changing the SA user/pass to an authenticated AD username and am
receiving a new message.
Exception Details: System.Data.SqlClient.SqlException: An error has
occurred while establishing a connection to the server. When connecting to
SQL Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Thanks again for your continued assistance with this matter.
Regards,
TP
"Timothy Peer" wrote:
> Yesterday I upgraded an SQL Server 2000 to 2005 (rolling upgrade). When 2005
> was installed, I selected the Windows Integrated Securityand subsequently
> changed security to Mixed Mode from the Management Tool.
>
> Problem: .NET ASPX pages which reference a 2005 database are not
> authenticating. The pages are coded to use the SA account and password
> inherited from the 2000 environment (I know it isn't the right way to do it)
> which under 2000 worked fine.
>
> I found various discussions related to the ASPNet and the IIS_WAP? user (I
> don't have an IIS_WAP user or group in AD).
>
> What I need: ASPX pages which are accessed via unauthenticated accounts via
> the internet (which are hard-coded to use the SA password.)
>
> ISA 2003 is installed and configured.
> Exchange is configured on this system, OWA and Sharepoint.
>
> Questions: What is my configuration missing to no permit unauthenticated
> users to access the SQL Server database (1433 is open and enabled)? Should I
> uninstall and reinstall IIS 6.0 or run the ICW?
>
> Please advise and thanks!
>
> Tim Peer
| |
| Arnie Rowland 2006-10-28, 7:14 pm |
| You want to ENABLE Local and Remote access via the Surface Configuration
Utility.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Timothy Peer" < TimothyPeer@discussi
ons.microsoft.com> wrote in message
news:645F896B-67BD-4482-B95F- D0C2FF6A1165@microso
ft.com...[color=darkred]
> Arnie,
>
> Thanks for the quick response. TCPIP protocol is enabled and have since
> disabled Local and Remote access via the Surface Configuration Utility. I
> will restart the services and start again and toggle TCPIP back to Local
> and
> Remote to see if this helps.
>
> Also, I am changing the SA user/pass to an authenticated AD username and
> am
> receiving a new message.
>
> Exception Details: System.Data.SqlClient.SqlException: An error has
> occurred while establishing a connection to the server. When connecting
> to
> SQL Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections. (provider:
> Named Pipes Provider, error: 40 - Could not open a connection to SQL
> Server)
>
> Thanks again for your continued assistance with this matter.
>
> Regards,
>
> TP
> "Timothy Peer" wrote:
>
| |
| Arnie Rowland 2006-10-28, 7:14 pm |
| You want to ENABLE Local and Remote access via the Surface Configuration
Utility.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Timothy Peer" < TimothyPeer@discussi
ons.microsoft.com> wrote in message
news:645F896B-67BD-4482-B95F- D0C2FF6A1165@microso
ft.com...[color=darkred]
> Arnie,
>
> Thanks for the quick response. TCPIP protocol is enabled and have since
> disabled Local and Remote access via the Surface Configuration Utility. I
> will restart the services and start again and toggle TCPIP back to Local
> and
> Remote to see if this helps.
>
> Also, I am changing the SA user/pass to an authenticated AD username and
> am
> receiving a new message.
>
> Exception Details: System.Data.SqlClient.SqlException: An error has
> occurred while establishing a connection to the server. When connecting
> to
> SQL Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections. (provider:
> Named Pipes Provider, error: 40 - Could not open a connection to SQL
> Server)
>
> Thanks again for your continued assistance with this matter.
>
> Regards,
>
> TP
> "Timothy Peer" wrote:
>
| |
| Arnie Rowland 2006-10-28, 7:14 pm |
| You want to ENABLE Local and Remote access via the Surface Configuration
Utility.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Timothy Peer" < TimothyPeer@discussi
ons.microsoft.com> wrote in message
news:645F896B-67BD-4482-B95F- D0C2FF6A1165@microso
ft.com...[color=darkred]
> Arnie,
>
> Thanks for the quick response. TCPIP protocol is enabled and have since
> disabled Local and Remote access via the Surface Configuration Utility. I
> will restart the services and start again and toggle TCPIP back to Local
> and
> Remote to see if this helps.
>
> Also, I am changing the SA user/pass to an authenticated AD username and
> am
> receiving a new message.
>
> Exception Details: System.Data.SqlClient.SqlException: An error has
> occurred while establishing a connection to the server. When connecting
> to
> SQL Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections. (provider:
> Named Pipes Provider, error: 40 - Could not open a connection to SQL
> Server)
>
> Thanks again for your continued assistance with this matter.
>
> Regards,
>
> TP
> "Timothy Peer" wrote:
>
|
|
|
|
|