Access to my own webserver

  • Thread starter Thread starter Pelle
  • Start date Start date
P

Pelle

Hello all,

I have a webserver application that was not written by me, but it's
not a publicly available one. I have installed this application on a
server on port 8080. I can access the server on localhost:8080 as
expected.
When I try to access the server from a different machine, the request
fails.
I have checked DNS, firewall and other settings (ping,...) but I
didn't achieve any results.
I have installed tcptrace and rerouted localhost:8080 to localhost:
8181 and now I can access the server on 8181 without problems.
Which settings may prevent me from accessing the original web-server?

Any hints on this one greatly appreciated!

Regards,
Pelle.
 
Pelle said:
I have a webserver application that was not written by me, but it's
not a publicly available one. I have installed this application on a
server on port 8080. I can access the server on localhost:8080 as
expected.
When I try to access the server from a different machine, the request
fails.
I have checked DNS, firewall and other settings (ping,...) but I
didn't achieve any results.
Click to expand...

On which interfaces does the web server listen? What you describe sounds
to me as if the web server is only listening on localhost and thus only
responds on localhost and nowhere else. Check with "netstat -a" or
"netstat -a -n".

Gerald
 
On which interfaces does the web server listen? What you describe sounds
to me as if the web server is only listening on localhost and thus only
responds on localhost and nowhere else. Check with "netstat -a" or
"netstat -a -n".

Gerald
Click to expand...

Hello Gerald,

thanks for the hint, it seems you have struck the core of the problem.
Using netstat -a, I didn't see anything special, but using netstat -a -
n I saw that the regular services are listening on 0.0.0.0:xx, but my
webserver is indeed listening on 127.0.0.1 (localhost)!

Thank you very much.

Regards,
Pelle.
 
Back
Top