Can't connect to a SQL engine running on WS2003 from external webserver

[Bjarke Hvejsel]

I have an ASP application, hosted externally, which
connects to a SQL engine on my Windows Server 2003.
Until a few weeks ago I ran the SQL engine on a Windows
2000 Server, and could connect from the external
webserver without any problems. But after I installed
WS2003, the external server can't connect to my SQL
engine. I have disabled the builtin firewall, and have
installed BlackIce firewall instead. The external
webserver is fully trusted on my firewall. And it used to
work under windows 2000 server...

What do I do wrong?

[Ken Schaefer]

Can you connect if you disable the BlackIce Firewall? If so, then that is
the culprit.

If not, then something else is up.

What are you using (eg what application), on the external webserver, to test
connectivity to the SQL Server? What is the error message you are getting?

Cheers
Ken

"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
: I have an ASP application, hosted externally, which
: connects to a SQL engine on my Windows Server 2003.
: Until a few weeks ago I ran the SQL engine on a Windows
: 2000 Server, and could connect from the external
: webserver without any problems. But after I installed
: WS2003, the external server can't connect to my SQL
: engine. I have disabled the builtin firewall, and have
: installed BlackIce firewall instead. The external
: webserver is fully trusted on my firewall. And it used to
: work under windows 2000 server...
:
: What do I do wrong?
:

[Bjarke Hvejsel]

No - it doesn't work when I disable ALL firewall
functionality. Both the builtin WS2003 firewall and the
Blackice. It's like there's still some kind of block on
my system...

I'm using the ASP application that runs on the external
webserver to test. I used to work, and it works if I run
the application from the internal webserver - unmodified!

The error is the "HTTP 500 - Internal server error " -
but that's due to the fact that the application can't
connect to the SQL server.

Before I trusted the external webserver, I got hits in my
firewall-logs from the calls the external server tried to
make. I set those calls to "allowed" in my firewall, and
furthermore I made a complete trust on the IP of the
external server.

As I said... This has been running without any problem
before under Windows 2000 server. The difference is that
I now run the SQL server on a Windows Server 2003...

>-----Original Message-----
>Can you connect if you disable the BlackIce Firewall? If

so, then that is

>the culprit.
>
>If not, then something else is up.
>
>What are you using (eg what application), on the

external webserver, to test

>connectivity to the SQL Server? What is the error

message you are getting?

>
>Cheers
>Ken
>
>"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
>news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
>: I have an ASP application, hosted externally, which
>: connects to a SQL engine on my Windows Server 2003.
>: Until a few weeks ago I ran the SQL engine on a Windows
>: 2000 Server, and could connect from the external
>: webserver without any problems. But after I installed
>: WS2003, the external server can't connect to my SQL
>: engine. I have disabled the builtin firewall, and have
>: installed BlackIce firewall instead. The external
>: webserver is fully trusted on my firewall. And it used

to

>: work under windows 2000 server...
>:
>: What do I do wrong?
>:
>
>
>.
>

[Sergio Orrego]

It might help if you can get the proper error message in IE.

To do that open IE & go to tools/internet options. In the advanced tab check
the 'show friendly HTTP error messages' box.

You may get a more meaningful error.


"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
news:0ba001c350fb$8745ae50$a101280a@phx.gbl...

> No - it doesn't work when I disable ALL firewall
> functionality. Both the builtin WS2003 firewall and the
> Blackice. It's like there's still some kind of block on
> my system...
>
> I'm using the ASP application that runs on the external
> webserver to test. I used to work, and it works if I run
> the application from the internal webserver - unmodified!
>
> The error is the "HTTP 500 - Internal server error " -
> but that's due to the fact that the application can't
> connect to the SQL server.
>
> Before I trusted the external webserver, I got hits in my
> firewall-logs from the calls the external server tried to
> make. I set those calls to "allowed" in my firewall, and
> furthermore I made a complete trust on the IP of the
> external server.
>
> As I said... This has been running without any problem
> before under Windows 2000 server. The difference is that
> I now run the SQL server on a Windows Server 2003...
>
>

> >-----Original Message-----
> >Can you connect if you disable the BlackIce Firewall? If

> so, then that is

> >the culprit.
> >
> >If not, then something else is up.
> >
> >What are you using (eg what application), on the

> external webserver, to test

> >connectivity to the SQL Server? What is the error

> message you are getting?

> >
> >Cheers
> >Ken
> >
> >"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
> >news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
> >: I have an ASP application, hosted externally, which
> >: connects to a SQL engine on my Windows Server 2003.
> >: Until a few weeks ago I ran the SQL engine on a Windows
> >: 2000 Server, and could connect from the external
> >: webserver without any problems. But after I installed
> >: WS2003, the external server can't connect to my SQL
> >: engine. I have disabled the builtin firewall, and have
> >: installed BlackIce firewall instead. The external
> >: webserver is fully trusted on my firewall. And it used

> to

> >: work under windows 2000 server...
> >:
> >: What do I do wrong?
> >:
> >
> >
> >.
> >

[Sergio Orrego]

It might help if you can get the proper error message in IE.

To do that open IE & go to tools/internet options. In the advanced tab check
the 'show friendly HTTP error messages' box.

You may get a more meaningful error.

"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
news:0ba001c350fb$8745ae50$a101280a@phx.gbl...

> No - it doesn't work when I disable ALL firewall
> functionality. Both the builtin WS2003 firewall and the
> Blackice. It's like there's still some kind of block on
> my system...
>
> I'm using the ASP application that runs on the external
> webserver to test. I used to work, and it works if I run
> the application from the internal webserver - unmodified!
>
> The error is the "HTTP 500 - Internal server error " -
> but that's due to the fact that the application can't
> connect to the SQL server.
>
> Before I trusted the external webserver, I got hits in my
> firewall-logs from the calls the external server tried to
> make. I set those calls to "allowed" in my firewall, and
> furthermore I made a complete trust on the IP of the
> external server.
>
> As I said... This has been running without any problem
> before under Windows 2000 server. The difference is that
> I now run the SQL server on a Windows Server 2003...
>
>

> >-----Original Message-----
> >Can you connect if you disable the BlackIce Firewall? If

> so, then that is

> >the culprit.
> >
> >If not, then something else is up.
> >
> >What are you using (eg what application), on the

> external webserver, to test

> >connectivity to the SQL Server? What is the error

> message you are getting?

> >
> >Cheers
> >Ken
> >
> >"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
> >news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
> >: I have an ASP application, hosted externally, which
> >: connects to a SQL engine on my Windows Server 2003.
> >: Until a few weeks ago I ran the SQL engine on a Windows
> >: 2000 Server, and could connect from the external
> >: webserver without any problems. But after I installed
> >: WS2003, the external server can't connect to my SQL
> >: engine. I have disabled the builtin firewall, and have
> >: installed BlackIce firewall instead. The external
> >: webserver is fully trusted on my firewall. And it used

> to

> >: work under windows 2000 server...
> >:
> >: What do I do wrong?
> >:
> >
> >
> >.
> >

[Ken Schaefer]

If you are using Internet Explorer, then goto Tools -> Options -> Advanced
and uncheck "Show Friendly HTTP Errors", and reload the page so that you can
see the real error message.

Also, try testing connectivity using some other tool (eg Query Analyser, or
Enteprise Manager)

Cheers
Ken

"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
news:0ba001c350fb$8745ae50$a101280a@phx.gbl...
: No - it doesn't work when I disable ALL firewall
: functionality. Both the builtin WS2003 firewall and the
: Blackice. It's like there's still some kind of block on
: my system...
:
: I'm using the ASP application that runs on the external
: webserver to test. I used to work, and it works if I run
: the application from the internal webserver - unmodified!
:
: The error is the "HTTP 500 - Internal server error " -
: but that's due to the fact that the application can't
: connect to the SQL server.
:
: Before I trusted the external webserver, I got hits in my
: firewall-logs from the calls the external server tried to
: make. I set those calls to "allowed" in my firewall, and
: furthermore I made a complete trust on the IP of the
: external server.
:
: As I said... This has been running without any problem
: before under Windows 2000 server. The difference is that
: I now run the SQL server on a Windows Server 2003...
:
:
: >-----Original Message-----
: >Can you connect if you disable the BlackIce Firewall? If
: so, then that is
: >the culprit.
: >
: >If not, then something else is up.
: >
: >What are you using (eg what application), on the
: external webserver, to test
: >connectivity to the SQL Server? What is the error
: message you are getting?
: >
: >Cheers
: >Ken
: >
: >"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
: >news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
: >: I have an ASP application, hosted externally, which
: >: connects to a SQL engine on my Windows Server 2003.
: >: Until a few weeks ago I ran the SQL engine on a Windows
: >: 2000 Server, and could connect from the external
: >: webserver without any problems. But after I installed
: >: WS2003, the external server can't connect to my SQL
: >: engine. I have disabled the builtin firewall, and have
: >: installed BlackIce firewall instead. The external
: >: webserver is fully trusted on my firewall. And it used
: to
: >: work under windows 2000 server...
: >:
: >: What do I do wrong?
: >:
: >
: >
: >.
: >

[John Beschler]

This may be obvious, but have you made sure that the
application is pointing to the new server? Did you change
server name and/or IP address when you installed 2K3?

>-----Original Message-----
>No - it doesn't work when I disable ALL firewall
>functionality. Both the builtin WS2003 firewall and the
>Blackice. It's like there's still some kind of block on
>my system...
>
>I'm using the ASP application that runs on the external
>webserver to test. I used to work, and it works if I run
>the application from the internal webserver - unmodified!
>
>The error is the "HTTP 500 - Internal server error " -
>but that's due to the fact that the application can't
>connect to the SQL server.
>
>Before I trusted the external webserver, I got hits in my
>firewall-logs from the calls the external server tried to
>make. I set those calls to "allowed" in my firewall, and
>furthermore I made a complete trust on the IP of the
>external server.
>
>As I said... This has been running without any problem
>before under Windows 2000 server. The difference is that
>I now run the SQL server on a Windows Server 2003...
>
>

>>-----Original Message-----
>>Can you connect if you disable the BlackIce Firewall? If

>so, then that is

>>the culprit.
>>
>>If not, then something else is up.
>>
>>What are you using (eg what application), on the

>external webserver, to test

>>connectivity to the SQL Server? What is the error

>message you are getting?

>>
>>Cheers
>>Ken
>>
>>"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
>>news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
>>: I have an ASP application, hosted externally, which
>>: connects to a SQL engine on my Windows Server 2003.
>>: Until a few weeks ago I ran the SQL engine on a Windows
>>: 2000 Server, and could connect from the external
>>: webserver without any problems. But after I installed
>>: WS2003, the external server can't connect to my SQL
>>: engine. I have disabled the builtin firewall, and have
>>: installed BlackIce firewall instead. The external
>>: webserver is fully trusted on my firewall. And it used

>to

>>: work under windows 2000 server...
>>:
>>: What do I do wrong?
>>:
>>
>>
>>.
>>

>.
>

[Bjarke Hvejsel]

I allready did that - but you won't get a more detailed
error-message, when it's a HTTP 500 - Internal Server
error"... Besides I know what cause the error.
It's the missing connection.

And I have tried all other means of testing the
connection. But no luck.

I've been working with SQL servers, internet and Windows
for 6-7 years now, so I'm now novice. But I just can't
crack this nut.

/MrWeb

>-----Original Message-----
>It might help if you can get the proper error message in

IE.

>
>To do that open IE & go to tools/internet options. In

the advanced tab check

>the 'show friendly HTTP error messages' box.
>
>You may get a more meaningful error.
>
>
>"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
>news:0ba001c350fb$8745ae50$a101280a@phx.gbl...

>> No - it doesn't work when I disable ALL firewall
>> functionality. Both the builtin WS2003 firewall and the
>> Blackice. It's like there's still some kind of block on
>> my system...
>>
>> I'm using the ASP application that runs on the external
>> webserver to test. I used to work, and it works if I

run

>> the application from the internal webserver -

unmodified!

>>
>> The error is the "HTTP 500 - Internal server error " -
>> but that's due to the fact that the application can't
>> connect to the SQL server.
>>
>> Before I trusted the external webserver, I got hits in

my

>> firewall-logs from the calls the external server tried

to

>> make. I set those calls to "allowed" in my firewall,

and

>> furthermore I made a complete trust on the IP of the
>> external server.
>>
>> As I said... This has been running without any problem
>> before under Windows 2000 server. The difference is

that

>> I now run the SQL server on a Windows Server 2003...
>>
>>

>> >-----Original Message-----
>> >Can you connect if you disable the BlackIce Firewall?

If

>> so, then that is

>> >the culprit.
>> >
>> >If not, then something else is up.
>> >
>> >What are you using (eg what application), on the

>> external webserver, to test

>> >connectivity to the SQL Server? What is the error

>> message you are getting?

>> >
>> >Cheers
>> >Ken
>> >
>> >"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
>> >news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
>> >: I have an ASP application, hosted externally, which
>> >: connects to a SQL engine on my Windows Server 2003.
>> >: Until a few weeks ago I ran the SQL engine on a

Windows

>> >: 2000 Server, and could connect from the external
>> >: webserver without any problems. But after I

installed

>> >: WS2003, the external server can't connect to my SQL
>> >: engine. I have disabled the builtin firewall, and

have

>> >: installed BlackIce firewall instead. The external
>> >: webserver is fully trusted on my firewall. And it

used

>> to

>> >: work under windows 2000 server...
>> >:
>> >: What do I do wrong?
>> >:
>> >
>> >
>> >.
>> >

>
>
>.
>

[Bjarke Hvejsel]

I allready tried all that. I know what cause the error.
It's the missing connection.

I have tried all other means of testing the connection.
But no luck.

I've been working with SQL servers, internet and Windows
for 6-7 years now, so I'm no novice. But I just can't
crack this nut.

/MrWeb

>-----Original Message-----
>This may be obvious, but have you made sure that the
>application is pointing to the new server? Did you

change

>server name and/or IP address when you installed 2K3?
>
>
>

>>-----Original Message-----
>>No - it doesn't work when I disable ALL firewall
>>functionality. Both the builtin WS2003 firewall and the
>>Blackice. It's like there's still some kind of block on
>>my system...
>>
>>I'm using the ASP application that runs on the external
>>webserver to test. I used to work, and it works if I

run

>>the application from the internal webserver -

unmodified!

>>
>>The error is the "HTTP 500 - Internal server error " -
>>but that's due to the fact that the application can't
>>connect to the SQL server.
>>
>>Before I trusted the external webserver, I got hits in

my

>>firewall-logs from the calls the external server tried

to

>>make. I set those calls to "allowed" in my firewall,

and

>>furthermore I made a complete trust on the IP of the
>>external server.
>>
>>As I said... This has been running without any problem
>>before under Windows 2000 server. The difference is

that

>>I now run the SQL server on a Windows Server 2003...
>>
>>

>>>-----Original Message-----
>>>Can you connect if you disable the BlackIce Firewall?

If

>>so, then that is

>>>the culprit.
>>>
>>>If not, then something else is up.
>>>
>>>What are you using (eg what application), on the

>>external webserver, to test

>>>connectivity to the SQL Server? What is the error

>>message you are getting?

>>>
>>>Cheers
>>>Ken
>>>
>>>"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
>>>news:0a3201c350f6$51f9d410$a301280a@phx.gbl.. .
>>>: I have an ASP application, hosted externally, which
>>>: connects to a SQL engine on my Windows Server 2003.
>>>: Until a few weeks ago I ran the SQL engine on a

Windows

>>>: 2000 Server, and could connect from the external
>>>: webserver without any problems. But after I installed
>>>: WS2003, the external server can't connect to my SQL
>>>: engine. I have disabled the builtin firewall, and

have

>>>: installed BlackIce firewall instead. The external
>>>: webserver is fully trusted on my firewall. And it

used

>>to

>>>: work under windows 2000 server...
>>>:
>>>: What do I do wrong?
>>>:
>>>
>>>
>>>.
>>>

>>.
>>

>.
>

[Bjarke Hvejsel]

Please read my reply to Sergio Orrego.

/MrWeb

>-----Original Message-----
>If you are using Internet Explorer, then goto Tools ->

Options -> Advanced

>and uncheck "Show Friendly HTTP Errors", and reload the

page so that you can

>see the real error message.
>
>Also, try testing connectivity using some other tool (eg

Query Analyser, or

>Enteprise Manager)
>
>Cheers
>Ken
>
>"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
>news:0ba001c350fb$8745ae50$a101280a@phx.gbl...
>: No - it doesn't work when I disable ALL firewall
>: functionality. Both the builtin WS2003 firewall and the
>: Blackice. It's like there's still some kind of block on
>: my system...
>:
>: I'm using the ASP application that runs on the external
>: webserver to test. I used to work, and it works if I

run

>: the application from the internal webserver -

unmodified!

>:
>: The error is the "HTTP 500 - Internal server error " -
>: but that's due to the fact that the application can't
>: connect to the SQL server.
>:
>: Before I trusted the external webserver, I got hits in

my

>: firewall-logs from the calls the external server tried

to

>: make. I set those calls to "allowed" in my firewall,

and

>: furthermore I made a complete trust on the IP of the
>: external server.
>:
>: As I said... This has been running without any problem
>: before under Windows 2000 server. The difference is

that

>: I now run the SQL server on a Windows Server 2003...
>:
>:
>: >-----Original Message-----
>: >Can you connect if you disable the BlackIce Firewall?

If

>: so, then that is
>: >the culprit.
>: >
>: >If not, then something else is up.
>: >
>: >What are you using (eg what application), on the
>: external webserver, to test
>: >connectivity to the SQL Server? What is the error
>: message you are getting?
>: >
>: >Cheers
>: >Ken
>: >
>: >"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
>: >news:0a3201c350f6$51f9d410$a301280a@phx.gbl...
>: >: I have an ASP application, hosted externally, which
>: >: connects to a SQL engine on my Windows Server 2003.
>: >: Until a few weeks ago I ran the SQL engine on a

Windows

>: >: 2000 Server, and could connect from the external
>: >: webserver without any problems. But after I

installed

>: >: WS2003, the external server can't connect to my SQL
>: >: engine. I have disabled the builtin firewall, and

have

>: >: installed BlackIce firewall instead. The external
>: >: webserver is fully trusted on my firewall. And it

used

>: to
>: >: work under windows 2000 server...
>: >:
>: >: What do I do wrong?
>: >:
>: >
>: >
>: >.
>: >
>
>
>.
>

[Chris Hohmann]

"Bjarke Hvejsel" <mrweb@twivia.net> wrote in message
news:0a3201c350f6$51f9d410$a301280a@phx.gbl...

> I have an ASP application, hosted externally, which
> connects to a SQL engine on my Windows Server 2003.
> Until a few weeks ago I ran the SQL engine on a Windows
> 2000 Server, and could connect from the external
> webserver without any problems. But after I installed
> WS2003, the external server can't connect to my SQL
> engine. I have disabled the builtin firewall, and have
> installed BlackIce firewall instead. The external
> webserver is fully trusted on my firewall. And it used to
> work under windows 2000 server...
>
> What do I do wrong?
>

Could you provide some more detail about your model? Specifically, you
mentioned that the external server is fully trusted. Have you also added
the external trusted group to a local group on your db server with
rights to the database? When you say you installed 2003, do you mean you
upgrade an existing installation of 2000 (with SQLServer) to 2003 or did
you install 2003 to a new machine and migrate the db(s)? Are you able to
access the db via SQL authentication? Who are SQLServer and Agent
running as?

This article may be of help:

[url]http://www.microsoft.com/technet/prodtechnol/sql/maintain/security/sp3sec/SP3SEC01.ASP[/url]