Re: IIS6 connecting ports

Thanx for your answer Kristofer, I will try to clarify further if
possible..

> What exactly is crashing? IIS? The application pool? Something else?
All websites become inaccessable [404].

> When does it crash? Immediately when you enabled NIC2? When you (try to)
> connect to the database?
Yes I think it is when the asp page attempts db connection

> What is the definition of a crash in this context (i have a feeling that you
> mean that the websites are just inaccessible)?
Correct

> Nothing explained in your message should cause IIS to crash. Connecting to
> two different databases from the same web server, from different
> applications should not be a problem.

I fully agree and cannot understand how this can occur.

> Can this be a routing issue? When you enable NIC2 the server doesn't really
> know which NIC to use for outgoing traffic?

I have the primary SQL server listening on 1433 as usual, and the
secondary listening on 1533 so have routed NIC2 - 10.0.10.11 &
10.0.10.12 out of the DMZ on 1533 only to the secondary SQL server,
likewise NIC1 - 10.0.10.10 out of the DMZ on 1433 only to the primary
SQL server so there should be no crossover. However when I try to
connect to the website on 10.0.10.11 the firewall tells me that a
connection is being made from 10.0.10.10 to secondary SQL server on
port 1434!!

Bizarre!

Re: IIS6 connecting ports

Please see inline below

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


"gstar" skrev i meddelandet
news:1cac52b4-406c-446e-9a7f-173ff04b4dad@c4g2000hsg.googleg roups.com...
> Thanx for your answer Kristofer, I will try to clarify further if
> possible..
>
>> What exactly is crashing? IIS? The application pool? Something else?
> All websites become inaccessable [404].

That does not make sense. Nothing described here would cause IIS to respond
with 404 (file not found). I could except something in the 500 range, but
not 404. Maybe the web browser is not telling the truth (internet explorer
is not very friendly about this)?

Can you please use a tool such as WFetch to access the website, so we can
see what is actually happening and what IIS responds with (or not responds).

Do you run all websites in the same application pool? Is anything logged in
the event log?

>
>> When does it crash? Immediately when you enabled NIC2? When you (try to)
>> connect to the database?
> Yes I think it is when the asp page attempts db connection

We need to know for sure. I have a feeling that it happens either when you
enable NIC2, or when the first request gets to IIS.

>
>> What is the definition of a crash in this context (i have a feeling that
>> you
>> mean that the websites are just inaccessible)?
> Correct

Okay, so nothing actually crashes? Does it perhaps work locally? Have you
tried to access a regular html page locally when this occurs? I suspect that
this will work. Is anything logged in the httperr log?

>
>> Nothing explained in your message should cause IIS to crash. Connecting
>> to
>> two different databases from the same web server, from different
>> applications should not be a problem.
>
> I fully agree and cannot understand how this can occur.
>
>> Can this be a routing issue? When you enable NIC2 the server doesn't
>> really
>> know which NIC to use for outgoing traffic?
>
> I have the primary SQL server listening on 1433 as usual, and the
> secondary listening on 1533 so have routed NIC2 - 10.0.10.11 &
> 10.0.10.12 out of the DMZ on 1533 only to the secondary SQL server,
> likewise NIC1 - 10.0.10.10 out of the DMZ on 1433 only to the primary
> SQL server so there should be no crossover. However when I try to
> connect to the website on 10.0.10.11 the firewall tells me that a
> connection is being made from 10.0.10.10 to secondary SQL server on
> port 1434!!

How do you tell IIS to use a specific NIC to access the database server? I
think this is your problem. Your application misbehaves when it cannot get
the expected result from the SQL Server due to a networking issue, which
seems to be the problem.

Are these NICs on the same subnet? Something tells me they are. As far as i
know you cannot tell Windows to use NIC1 when the incoming request to IIS
comes on 10.0.10.10. Traffic are not bound to a specific NIC. Windows will
use whatever NIC it can use to reach the destination, and has the lowest
cost.

I think the problem is here. Windows does not use the NIC you expect it to
use when connecting to the database server.

I am not a networking expert, so i would recommend you to ask about this in
the networking newsgroup. Because i think that you have not properly
configured this. And i don't think anything is wrong with IIS (the logs
would say something, and also try to download a static file locally).

>
> Bizarre!
>
>
>