"Michael W. Cocke" wrote
> "Michael Gong" wrote:
>
> >I have 2 computers with names LinxuBox and XpBox , which access internet
by
> >a router.
> >
> >Say my router's ip is 65.95.184.188, and I forward the 8080 port to
> >LinuxBox, which has an Apache web server listening on port 8080.
> >
> >Then from my LinuxBox machine, I can use:
> > http://localhost:8080/
> > http://65.95.184.188:8080/
> > to see the webpage.
> >
> >From my XpBox, I can only use http://LinuxBox:8080/ to access the
page.
> > But when using http://65.95.184.188:8080/ , the page didn't show up.
>
> My offhand guess is that your ISP is blocking port 80. Many of them do.
>
> Mike-
They'd either have to be blocking port 8080 or be blocking based on http
type.
a) you claim your linux box is ip address 65.95.184.188 too?
Unconventional;
I'd expect it to be something like 192.168.0.2 on your LAN, and the router
forwards packets to it with address translation when outside users hit your
isp-assigned ip address, port 8080.
b) is your http demon {apache or whatever} really listening on port 8080?
You
can either recheck the configuration files or read man netstat to learn
how to
make your linux netstat show all ports being listened-to. I forget, right
now.
c) after you've verified your linux ip address and listening-port in a),b)
above
then go recheck your router's forwarding setup and make sure it matches.
d) clutching at straws here, but your XpBox could using the squid proxy
service on the linux box; make sure you're testing with no proxy set up in
your
internet explorer or netscape or whatever.
e) you could take your linux box firewall down altogether for long enough to
run your web browser, and see if your firewall's been the culprit here.
Using
an assistant for the distant end you'd only be at increased risk for say 15
seconds.
The script kiddies can't _always_ be hammering your firewall, and might very
well
miss their opportunity.