|
Home > Archive > Web Servers on Windows > July 2005 > cannot access webserver from host pc
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
cannot access webserver from host pc
|
|
| jsantos8 2005-07-01, 2:47 am |
| problem accessing my server from the host computer. I had a problem
accessing it outside the network but that's fixed now I don't know how
to make it work from localhost again.
I have
Listen 8082 # because cablevision blocks 80
ServerName localhost # i've tried my external IP, lan IP, and
localhost:8082 and neither enables me to access apache from the host
computer. Any ideas?
| |
| Kees Nuyt 2005-07-01, 5:54 pm |
| On 30 Jun 2005 19:36:12 -0700, "jsantos8"
<jsantos8@optonline.net> wrote:
>problem accessing my server from the host computer. I had a problem
>accessing it outside the network but that's fixed now I don't know how
>to make it work from localhost again.
>I have
>Listen 8082 # because cablevision blocks 80
>ServerName localhost # i've tried my external IP, lan IP, and
>localhost:8082 and neither enables me to access apache from the host
>computer. Any ideas?
It can be reached from the outside without a problem, so indeed
port 8082 isn't blocked.
Does http://YOURWANIP:8082/ work from inside your LAN ?
Didn't you forget to add :8082 to http://LANIP:8082/ ?
Did you try hostname http://yourhost.at.your.domain:8082/
or http://a.b.c.d:8082/ (a.b.c.d being a numeric IP address) ?
To use hostname something has to resolve them to addresses.
The simplest way is to hardcode the relation in your hosts file
( C:\WINDOWS\SYSTEM32\DRIVERS\etc\hosts ), but that is not
suitable if your WAN IP changes all the time.
http://localhost:8082/ might not work if you use the virtual
hosts feature (though I don't think you do).
To reach http://yourhost.at.your.domain:8082/ from the inside
you have to
- either configure your router (if you have one) for loopback,
- or define yourhost.at.your.domain for 127.0.0.1 in hosts,
- or configure the usage of an outside proxy in your browser.
With the last method all requests go out to the proxy first and
the proxy will target them back to you.
There were several other contributions to this newsgroups on
this subject in the last few months. A search in google
newsgroups might give you more answers.
Hope this helps.
--
) Kees Nuyt
(
c[_]
|
|
|
|
|