Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ISA 2000 web publishing

Status
Not open for further replies.

LindsayeCroft

Technical User
Jun 10, 2003
32
GB
I am using isa 2000 on a windows 2000 server machine and i am trying to publish a website located on the internal network. I have had it working before but it has suddenly stopped working, i think it was because i re-did dns but i have done that much messing about now i am not sure

I have followed steps from microsoft site and isaserver.org but i just get a gateway timeout error.

I have:

1. set up a destination set with as the destination which is the address i want people on the internet to type in to reach our internal website.
2. created a web publishing rule which applies to the destination set i have created, reditrects requests to the ip address of the internal web server and applies to all traffic.
3. set isa to listen on its external nic on port 80.

I have tried changing allsorts of bits such as changing the ports that iis listen on and so much more my head hurts.

PLEASE can anybody help me?

Thankyou

Lindsay
 
Hi me again,

i think i have got a little further, on the external nic i have removed the dns entries so it simply has a static ip address, subnet mask and default gateway set.

now when i try to access i get the error
Bad Request
your browser sent a request that this server could not understand
Apache/2.0.48 (unix) PHP/4.3.4RC1 Server at Port 82

where that is the address of my internal webserver so something must be getting through?
 
check if you enabled send http header to server
and check if the http server in the default gateway got the isa server ip adress

hope its helps
coco10
 
thanks, i have ticked and unticked the send http header to server and it makes no difference. and the web server has the isa servers internal network address as it's default gateway and it still doesn't work.

i really think it is a dns problem but i can't work it out, don't understand as it was working - honest!
 
why port 82? do you try to access from internal?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top