This is a discussion on automatic redirecting?? within the Windows Web Servers forums, part of the Web Server and Related Forums category; ok my apache 2 server was running fine. now all of a sudden it is redirecting to the lan ip. ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
ok my apache 2 server was running fine. now all of a sudden it is
redirecting to the lan ip. eg i have http://203.173.6.6 and it will redirect to http://1.2.3.12 or http://computername this is frustrating for people that vis it the WAN IP which i have mapped to the lan ip *.*.*.12 i dont think i have changed anything, it just started happening 2 days ago, then i did something, and it stopped, now it is back to haunt me thanks in advance f00l -- " If at first you dont succeed, destroy all evidence you ever tried....." |
|
|||
|
f00l wrote:
> my apache 2 server was running fine. now all of a sudden it is > redirecting to the lan ip. > i have http://203.173.6.6 and it will redirect to http://1.2.3.12 > i dont think i have changed anything, it just started happening 2 days ago, > then i did something, and it stopped, now it is back to haunt me Keep meticulous notes on changes you make, regardless of how minor. Doing so will not leave you in a position of "I did something" and not being recall what you did. I keep a clipboard with notepaper and a pencil in front of our machines to remind me to make notes. Use only an official Number 2 pencil. Some notes on WAN / LAN ip address structures. When running a webserver, always use static ip address assignments. Configure each machine for a static address and turn off your DHCP server within your router and within any DHCP hosting machine, if appropriate. Router, no DHCP server. For a DHCP host machine, this depends on your LAN physical layout. Using DHCP will change machine addresses frequently; first machine booted, receives the first assignment, second, the next and so forth. Otherwords, machine addresses will change depending on boot order which can cause conflicts. Machine "names" remain the same but ip addresses change. It is exceptionally common for your server access log to reflect LAN addresses instead of your WAN address. For many, possibly most routers, when an http request is made by a LAN machine, that request is _not_ sent out to the internet, it is simply routed LAN locally, when you are running a public webserver, or other services such as email and dns. Assign static addresses to your machines, turn off any DHCP server running, then test. Your problems should vanish. Do remember to keep meticulous notes as you do this. Purl Gurl -- Amazing Perl Scripts! http://www.purlgurl.net/~callgirl/android.html |
|
|||
|
Thaks Purl Gurl for the advice on keeping a changelog
but i think my windows installation has hit the wierd factor... ok well for some reason it is not redirecting anynore...even though i havent changed anything this time..other than restart. posible bug? f00l -- " If at first you dont succeed, destroy all evidence you ever tried....." "Purl Gurl" <purlgurl@purlgurl.net> wrote in message news:40D1D75D.D4F52D6E@purlgurl.net... > f00l wrote: > > > my apache 2 server was running fine. now all of a sudden it is > > redirecting to the lan ip. > > > i have http://203.173.6.6 and it will redirect to http://1.2.3.12 > > > i dont think i have changed anything, it just started happening 2 days ago, > > then i did something, and it stopped, now it is back to haunt me > > Keep meticulous notes on changes you make, regardless of > how minor. Doing so will not leave you in a position of > "I did something" and not being recall what you did. > > I keep a clipboard with notepaper and a pencil in front > of our machines to remind me to make notes. > > Use only an official Number 2 pencil. > > Some notes on WAN / LAN ip address structures. > > When running a webserver, always use static ip address > assignments. Configure each machine for a static address > and turn off your DHCP server within your router and > within any DHCP hosting machine, if appropriate. > > Router, no DHCP server. For a DHCP host machine, > this depends on your LAN physical layout. > > Using DHCP will change machine addresses frequently; > first machine booted, receives the first assignment, > second, the next and so forth. Otherwords, machine > addresses will change depending on boot order which > can cause conflicts. Machine "names" remain the same > but ip addresses change. > > It is exceptionally common for your server access log > to reflect LAN addresses instead of your WAN address. > For many, possibly most routers, when an http request > is made by a LAN machine, that request is _not_ sent > out to the internet, it is simply routed LAN locally, > when you are running a public webserver, or other > services such as email and dns. > > Assign static addresses to your machines, turn off > any DHCP server running, then test. Your problems > should vanish. > > Do remember to keep meticulous notes as you do this. > > > Purl Gurl > -- > Amazing Perl Scripts! > http://www.purlgurl.net/~callgirl/android.html |