Ok all you gurus, I would love it if someone else has already tried this however...
Goal: To access my web server (IIS 5) that connects to internet via dialup, running ISA firewall also on same dialup, continuously from internet using DNS via a dynamic dns service (in this case **recommended**)
Config: Everything sits on the same W2K server box for now - 56kbp dialup interface, ISA configured to listen for inbound requests on port 80 for HTTP which will route to website (still on same box) on port 81 using a web publishing rule, HTTP/FTP fully open, default web site allows anonymous access etc.. Latest service packs / updates applied. Security is minimal at present until system darn well works properly.
In the beginning: On machine boot it runs beautifully, the dynamic dns client on server happily detects IP on dialup interface and notifies dyndns accordingly, any requests made via ping/browser to the web server are acknowledged/page served
And then (This is where I get stuck btw): once the dialup has disconnected and then reconnected, new ip allocated from ISP, ip updated at dyndns etc. the following occurs - can ping the dns name fine (my server's new ip is returned) but when trying an HTTP request I get error messages such as 10060 (timeout) etc., and the page is not displayed.
Conclusion: I have no idea as yet, tried many different things and would love a fresh look at it from another colleague out there, did the wise move of just opening up everything but no joy - I hazard a guess that it might be something to do with my local dns config or the ISA LAT but still have not been able to figure it out. Oh and of course in true IT style FTP works fine.
Well all I can say now is any replies or suggestions no matter how daft would be welcome.
Waiting in antici...pation.
Rgds.,
Edward
Goal: To access my web server (IIS 5) that connects to internet via dialup, running ISA firewall also on same dialup, continuously from internet using DNS via a dynamic dns service (in this case **recommended**)
Config: Everything sits on the same W2K server box for now - 56kbp dialup interface, ISA configured to listen for inbound requests on port 80 for HTTP which will route to website (still on same box) on port 81 using a web publishing rule, HTTP/FTP fully open, default web site allows anonymous access etc.. Latest service packs / updates applied. Security is minimal at present until system darn well works properly.
In the beginning: On machine boot it runs beautifully, the dynamic dns client on server happily detects IP on dialup interface and notifies dyndns accordingly, any requests made via ping/browser to the web server are acknowledged/page served
And then (This is where I get stuck btw): once the dialup has disconnected and then reconnected, new ip allocated from ISP, ip updated at dyndns etc. the following occurs - can ping the dns name fine (my server's new ip is returned) but when trying an HTTP request I get error messages such as 10060 (timeout) etc., and the page is not displayed.
Conclusion: I have no idea as yet, tried many different things and would love a fresh look at it from another colleague out there, did the wise move of just opening up everything but no joy - I hazard a guess that it might be something to do with my local dns config or the ISA LAT but still have not been able to figure it out. Oh and of course in true IT style FTP works fine.
Well all I can say now is any replies or suggestions no matter how daft would be welcome.
Waiting in antici...pation.
Rgds.,
Edward