W
WT
Hello,
My configuration is isa 2006 server connected to internet in front of a
windows domain, providing internet access, vpn, exchange 2007 publishing
and a web server in DMZ.
Exchange and web server are published to internet using classical
isa listerners.
The web server is a domain member.
Domain network is 192.168.1.0-255, web server is 10.0.0.2.
Each are connected to a different network card on isa (through a Giga switch
with
VLANs on ports),
Domain is on the internal isa network.
Web server is on annother isa network treated as a DMZwith routing enabled
between internal
and it and Web server piblished to the internet (external isa network)
In the isa rules, we have added full access between our domain controllers
and the web server to have domain authentication working, selecting
necessary protocols.
Our web server needs to access a domain server on the internal isa network
using
web services on port 80.
So we have added a rule allowing full HTTP access from Web server to the Web
Services server on port 80.
It works but is extremely slow, in such a way that some requests which were
working without problems, receive a timeout.
This is not a bandwith problem, especially because today, we have no traffic
on this isa server: 2 clients vpns using RDP , exchange with few mails, few
web access. But we want to open internet traffic on it.
I have suppressed the HTTP filter on the HTTP:80 rule with no change.
Solution is not Ok for a real usage of this architecture with dozen of
access/ hour.
Isa is working perfectly for web and exchange but is so slow for 'firewall
through' web service access !!!
How to improve seriously isa performance ?
1) Is it related to the fact that HTTP connection for web service is
using secureNat ?
The process in web server IIS calling the web service is running under
network services and we are calling web service with a valid network
credentials based on a domain admin account (for test).
2) I tried to add another network card on the Web server and to run it with
an internal domain address 192.168.1.x and connect it directly to domain
switch, but this seems to be fooling isa and I have been loosing server
access so I had to rollback this solution.
Any help welcome.
CS
My configuration is isa 2006 server connected to internet in front of a
windows domain, providing internet access, vpn, exchange 2007 publishing
and a web server in DMZ.
Exchange and web server are published to internet using classical
isa listerners.
The web server is a domain member.
Domain network is 192.168.1.0-255, web server is 10.0.0.2.
Each are connected to a different network card on isa (through a Giga switch
with
VLANs on ports),
Domain is on the internal isa network.
Web server is on annother isa network treated as a DMZwith routing enabled
between internal
and it and Web server piblished to the internet (external isa network)
In the isa rules, we have added full access between our domain controllers
and the web server to have domain authentication working, selecting
necessary protocols.
Our web server needs to access a domain server on the internal isa network
using
web services on port 80.
So we have added a rule allowing full HTTP access from Web server to the Web
Services server on port 80.
It works but is extremely slow, in such a way that some requests which were
working without problems, receive a timeout.
This is not a bandwith problem, especially because today, we have no traffic
on this isa server: 2 clients vpns using RDP , exchange with few mails, few
web access. But we want to open internet traffic on it.
I have suppressed the HTTP filter on the HTTP:80 rule with no change.
Solution is not Ok for a real usage of this architecture with dozen of
access/ hour.
Isa is working perfectly for web and exchange but is so slow for 'firewall
through' web service access !!!
How to improve seriously isa performance ?
1) Is it related to the fact that HTTP connection for web service is
using secureNat ?
The process in web server IIS calling the web service is running under
network services and we are calling web service with a valid network
credentials based on a domain admin account (for test).
2) I tried to add another network card on the Web server and to run it with
an internal domain address 192.168.1.x and connect it directly to domain
switch, but this seems to be fooling isa and I have been loosing server
access so I had to rollback this solution.
Any help welcome.
CS