Discussion:
"No access" when visiting status node page
Joel Konkle-Parker
2003-09-27 15:31:13 UTC
Permalink
I have Freenet 0.5.2.5 running on Windows XP Professional. When I
double-click on the tray icon, it opens up a browser to
http://127.0.0.1:8888/, but the only thing that shows up is a line
saying "No access".

I've messed with a few configuration settings, but nothing that seems
like it would have this side effect. Any idea what's going on here?
--
Joel Konkle-Parker
Webmaster [Ballsome.com]

Phone [662-518-1636]
E-mail [jjk3-***@public.gmane.org]
Toad
2003-09-27 15:35:45 UTC
Permalink
Post by Joel Konkle-Parker
I have Freenet 0.5.2.5 running on Windows XP Professional. When I
double-click on the tray icon, it opens up a browser to
http://127.0.0.1:8888/, but the only thing that shows up is a line
saying "No access".
Check your browser proxy settings. The most likely cause is that your
browser sends everything through the proxy. Change it so that 127.0.0.1
is excluded from the proxy. There should be a box for this in the
browser configuration somewhere. If that's not it, maybe you have
something else running on :8888 ?
Post by Joel Konkle-Parker
I've messed with a few configuration settings, but nothing that seems
like it would have this side effect. Any idea what's going on here?
--
Joel Konkle-Parker
Webmaster [Ballsome.com]
Phone [662-518-1636]
--
Matthew J Toseland - toad-EI5O+8PHWbJeeLb3ft/vUmD2FQJk+8+***@public.gmane.org
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.
Joel Konkle-Parker
2003-09-27 16:45:44 UTC
Permalink
Post by Toad
If that's not it, maybe you have
something else running on :8888 ?
Thanks, it looks like that was it. I changed the FProxy port from 8888
to 9000 and now I can get to the gateway. No idea what could be running
on 8888, though...
--
Joel Konkle-Parker
Webmaster [Ballsome.com]

Phone [662-518-1636]
E-mail [jjk3-***@public.gmane.org]
Toad
2003-09-27 16:46:44 UTC
Permalink
Post by Joel Konkle-Parker
Post by Toad
If that's not it, maybe you have
something else running on :8888 ?
Thanks, it looks like that was it. I changed the FProxy port from 8888
to 9000 and now I can get to the gateway. No idea what could be running
on 8888, though...
A trojan? :)
Post by Joel Konkle-Parker
--
Joel Konkle-Parker
Webmaster [Ballsome.com]
Phone [662-518-1636]
--
Matthew J Toseland - toad-EI5O+8PHWbJeeLb3ft/vUmD2FQJk+8+***@public.gmane.org
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.
Todd Walton
2003-09-27 20:38:42 UTC
Permalink
Post by Joel Konkle-Parker
Post by Toad
If that's not it, maybe you have
something else running on :8888 ?
Thanks, it looks like that was it. I changed the FProxy port from 8888
to 9000 and now I can get to the gateway. No idea what could be running
on 8888, though...
Amphetadesk?

-todd
Joel Konkle-Parker
2003-09-27 20:50:18 UTC
Permalink
Post by Todd Walton
Amphetadesk?
I don't really know what Amphetadesk is... here's an output of netstat
with Freenet stopped:

--
Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:3047 127.0.0.1:3048 ESTABLISHED
TCP 127.0.0.1:3048 127.0.0.1:3047 ESTABLISHED
TCP 192.168.0.101:3009 205.188.9.232:5190 ESTABLISHED
TCP 192.168.0.101:3330 207.46.106.55:1863 ESTABLISHED
TCP 192.168.0.101:3669 204.29.187.156:563 ESTABLISHED
TCP 192.168.0.101:4030 167.206.76.23:119 ESTABLISHED
TCP 192.168.0.101:4194 209.249.123.45:80 ESTABLISHED
TCP 192.168.0.101:4196 209.249.123.91:80 ESTABLISHED
TCP 192.168.0.101:4199 209.249.123.151:80 ESTABLISHED
TCP 192.168.0.101:4241 63.250.205.15:80 ESTABLISHED
TCP 192.168.0.101:4246 63.250.215.236:80 TIME_WAIT
TCP 192.168.0.101:4251 192.168.0.1:5678 TIME_WAIT
TCP 192.168.0.101:4256 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4257 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4258 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4260 192.168.0.1:5678 TIME_WAIT
TCP 192.168.0.101:4264 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4265 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4267 207.200.83.88:80 TIME_WAIT
TCP 192.168.0.101:4703 205.188.10.13:5190 ESTABLISHED
TCP 192.168.0.101:4704 64.12.27.100:5190 ESTABLISHED
TCP 192.168.0.101:4999 66.216.70.167:80 CLOSE_WAIT
--

I immediately start it using FProxy port 8888, and I get the 'No access'
message in my browser. It doesn't look like anything's already using
8888. I stop it, change it to port 9000, and it works.
--
Joel Konkle-Parker
Webmaster [Ballsome.com]

Phone [662-518-1636]
E-mail [jjk3-***@public.gmane.org]
Todd Walton
2003-09-27 22:12:51 UTC
Permalink
Post by Joel Konkle-Parker
I don't really know what Amphetadesk is... here's an output of netstat
A news aggregator:
http://www.disobey.com/amphetadesk/

It happens to use port 8888 as well. I guess this means you don't use
it...
Post by Joel Konkle-Parker
I immediately start it using FProxy port 8888, and I get the 'No access'
message in my browser. It doesn't look like anything's already using
8888. I stop it, change it to port 9000, and it works.
Maybe it's a firewall issue. Do you have a firewall set up in the router
or on your system?

You said it wasn't a proxy issue, right?

-todd
Dave Hooper
2003-09-27 22:19:08 UTC
Permalink
Yeh, you might want to use "netstat -a " or similar to show listening
sockets as well ... I bet you'll find something listening on 8888

----- Original Message -----
From: "Joel Konkle-Parker" <jjk3-***@public.gmane.org>
To: <support-***@public.gmane.org>
Sent: Saturday, September 27, 2003 9:50 PM
Subject: Re: [freenet-support] "No access" when visiting status node page
Post by Joel Konkle-Parker
Active Connections
Proto Local Address Foreign Address State
TCP 127.0.0.1:3047 127.0.0.1:3048 ESTABLISHED
TCP 127.0.0.1:3048 127.0.0.1:3047 ESTABLISHED
[...]
Edward J. Huff
2003-09-27 23:04:29 UTC
Permalink
Post by Joel Konkle-Parker
I immediately start it using FProxy port 8888, and I get the 'No access'
message in my browser. It doesn't look like anything's already using
8888. I stop it, change it to port 9000, and it works.
Try loading port 8888 when Fred isn't running. Probably you will
see the same thing, which would show that it is not related to the
freenet software.

-- Ed Huff
p***@public.gmane.org
2003-09-27 21:02:49 UTC
Permalink
use 'netstat -a' to see sockets that are in listening mode
Post by Joel Konkle-Parker
Post by Todd Walton
Amphetadesk?
I don't really know what Amphetadesk is... here's an output of netstat
--
Active Connections
Proto Local Address Foreign Address State
TCP 127.0.0.1:3047 127.0.0.1:3048 ESTABLISHED
TCP 127.0.0.1:3048 127.0.0.1:3047 ESTABLISHED
TCP 192.168.0.101:3009 205.188.9.232:5190 ESTABLISHED
TCP 192.168.0.101:3330 207.46.106.55:1863 ESTABLISHED
TCP 192.168.0.101:3669 204.29.187.156:563 ESTABLISHED
TCP 192.168.0.101:4030 167.206.76.23:119 ESTABLISHED
TCP 192.168.0.101:4194 209.249.123.45:80 ESTABLISHED
TCP 192.168.0.101:4196 209.249.123.91:80 ESTABLISHED
TCP 192.168.0.101:4199 209.249.123.151:80 ESTABLISHED
TCP 192.168.0.101:4241 63.250.205.15:80 ESTABLISHED
TCP 192.168.0.101:4246 63.250.215.236:80 TIME_WAIT
TCP 192.168.0.101:4251 192.168.0.1:5678 TIME_WAIT
TCP 192.168.0.101:4256 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4257 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4258 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4260 192.168.0.1:5678 TIME_WAIT
TCP 192.168.0.101:4264 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4265 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4267 207.200.83.88:80 TIME_WAIT
TCP 192.168.0.101:4703 205.188.10.13:5190 ESTABLISHED
TCP 192.168.0.101:4704 64.12.27.100:5190 ESTABLISHED
TCP 192.168.0.101:4999 66.216.70.167:80 CLOSE_WAIT
--
I immediately start it using FProxy port 8888, and I get the 'No access'
message in my browser. It doesn't look like anything's already using
8888. I stop it, change it to port 9000, and it works.
--
Joel Konkle-Parker
Webmaster [Ballsome.com]
Phone [662-518-1636]
_______________________________________________
Support mailing list
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Todd Walton
2003-10-11 20:43:01 UTC
Permalink
I just got this message today, October 11, but it was dated for September
27. Is everybody else just getting it, or is it *my* email that's
withholding emails from me?

-todd
Post by p***@public.gmane.org
use 'netstat -a' to see sockets that are in listening mode
Post by Joel Konkle-Parker
Post by Todd Walton
Amphetadesk?
I don't really know what Amphetadesk is... here's an output of netstat
--
Active Connections
Proto Local Address Foreign Address State
TCP 127.0.0.1:3047 127.0.0.1:3048 ESTABLISHED
TCP 127.0.0.1:3048 127.0.0.1:3047 ESTABLISHED
TCP 192.168.0.101:3009 205.188.9.232:5190 ESTABLISHED
TCP 192.168.0.101:3330 207.46.106.55:1863 ESTABLISHED
TCP 192.168.0.101:3669 204.29.187.156:563 ESTABLISHED
TCP 192.168.0.101:4030 167.206.76.23:119 ESTABLISHED
TCP 192.168.0.101:4194 209.249.123.45:80 ESTABLISHED
TCP 192.168.0.101:4196 209.249.123.91:80 ESTABLISHED
TCP 192.168.0.101:4199 209.249.123.151:80 ESTABLISHED
TCP 192.168.0.101:4241 63.250.205.15:80 ESTABLISHED
TCP 192.168.0.101:4246 63.250.215.236:80 TIME_WAIT
TCP 192.168.0.101:4251 192.168.0.1:5678 TIME_WAIT
TCP 192.168.0.101:4256 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4257 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4258 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4260 192.168.0.1:5678 TIME_WAIT
TCP 192.168.0.101:4264 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4265 216.157.132.2:110 TIME_WAIT
TCP 192.168.0.101:4267 207.200.83.88:80 TIME_WAIT
TCP 192.168.0.101:4703 205.188.10.13:5190 ESTABLISHED
TCP 192.168.0.101:4704 64.12.27.100:5190 ESTABLISHED
TCP 192.168.0.101:4999 66.216.70.167:80 CLOSE_WAIT
--
I immediately start it using FProxy port 8888, and I get the 'No access'
message in my browser. It doesn't look like anything's already using
8888. I stop it, change it to port 9000, and it works.
--
Joel Konkle-Parker
Webmaster [Ballsome.com]
Phone [662-518-1636]
_______________________________________________
Support mailing list
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
_______________________________________________
Support mailing list
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Nick Tarleton
2003-10-14 23:34:40 UTC
Permalink
Post by Todd Walton
I just got this message today, October 11, but it was dated for September
27. Is everybody else just getting it, or is it *my* email that's
withholding emails from me?
Me too.
--
"I love deadlines. I love the whooshing sound they make as they go by."
- Douglas Adams
Nick Tarleton - nickptar-***@public.gmane.org - PGP key available
Continue reading on narkive:
Loading...