@ray326Sep 10.2005 — #Have you set that IP somewhere in your httpd.conf? Is that actually an address assigned you your host? Do you already have IIS or something else running on port 80?
here it is [CODE]# from # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, in addition to the default. See also the <VirtualHost> # directive. # #Listen 3000 #Listen 12.34.56.78:80 Listen 127.0.0.10:80 to # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, in addition to the default. See also the <VirtualHost> # directive. # #Listen 3000 #Listen 12.34.56.78:80 Listen 80.127.160.194:80[/CODE]
@ray326Sep 10.2005 — #The problem isn't with your server. The following leads me to believe it's your firewall. Also, ADSL is a pretty sluggish server transport. For now why not just tell it to listen to port 80 and leave the IP off? <i> </i>C:WINDOWS>ping 80.127.160.194
@dean_de_besteauthorSep 10.2005 — #The problem isn't with your server. The following leads me to believe it's your firewall. Also, ADSL is a pretty sluggish server transport. For now why not just tell it to listen to port 80 and leave the IP off? <i> </i>C:WINDOWS>ping 80.127.160.194
@Stephen_PhilbinSep 10.2005 — #Trust us, just tell the server to listen to any address at port 80, then go into your firewall settings and open up port 80. Do you use a router too by any chance?
@ray326Sep 11.2005 — #What does your network architecture look like? What kind of box do you have sitting between the DSL modem and your network? Did your ISP give you 16 sequential IP addresses like x.192-x.200? Right now I'm wondering whether you can even make use of more than one.