Re: How can I access http://192.168.1.100:6000#

[sean]

Roland de Ruiter wrote:
> sean wrote:
>> How can I access http://192.168.1.100:6000# in FF1.5, works fine in IE
>> to make changes to NAS.
>> I cannot find any setting in Tools-Options menu to allow this.
>>
>> This is the dialog from FF1.5
>>
>> This address is restricted
>> This address uses a network port which is normally used for purposes
>> other than Web browsing. Firefox has canceled the request for your
>> protection.
>>
>> Thanks.
>
> Port 6000 is blocked by default (see
> <http://www.mozilla.org/projects/netlib/PortBanning.html>).
>
> To unblock this port (or other ports), type about:config in the address
> bar and locate the preference
>
> network.security.ports.banned.override
>
> It's possible that this pref doesn't exist (yet). To create it, do the
> following. Right-click on an existing pref (doesn't matter which) and
> from the popup menu select New > String. Type
> network.security.ports.banned.override
> as its name and
> 6000
> as its value.
>
> The preference accepts a comma separated list of ports or port ranges as
> its value, for example: 6000,8000-8088,500-511
>
> Apart from the "network.security.ports.banned.override" pref (used to
> *enable* ports), there's also the "network.security.ports.banned"
> preference for *disabling* ports.
>
> Regards,
>
> Roland

Does it makes any difference that I added a space at the end of

network.security.ports.banned.override

because the same "This address is restricted" dialog,
while on other ports, "Unable to connect" dialog appears.

If it makes a difference(the extra space), how do I delete this entry
from Pref page?

From the PortBanning Link, Port 6000 is for X1(what is this?).
I can find all.js file, but not the new pref entry in this file while
there is not such user.js in FF1.5 directory as

[gwtc]

sean wrote:

you're looking in the wrong area. You profile is located separate
from where the program is located.

To find your profile, you can read this:
http://www.mozilla.org/support/firefox/edit#profile

but first, if you're using windows, you can read this:
http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/hiddenfiles.mspx

You won't find the user.js file, because its a self made file. That
means you create it. You create it using a texted based editor, and
save the file in text format and name is user.js. It is save in the
same place as your prefs.js file, which is located in your profile.

--
so you think you've got computer problems!? HA! Its probably nothing
compared to this kids problem:
http://www.break.com/index/patiencechild.html

[sean]

Jay Garcia wrote:
> On 13.03.2006 05:45, sean wrote:

>
> --- Original Message ---
>
>> How can I access http://192.168.1.100:6000# in FF1.5, works fine in IE
>> to make changes to NAS.
>> I cannot find any setting in Tools-Options menu to allow this.
>>
>> This is the dialog from FF1.5
>>
>> This address is restricted
>> This address uses a network port which is normally used for purposes
>> other than Web browsing. Firefox has canceled the request for your
>> protection.
>>
>> Thanks.
>

> First of all I assume you realize that the IP address is used locally
> only and is not a public IP address. Have you tried dropping the # and
> use :6000 only?
>

Thanks for your help, it does not work...
I have also tried the method recommended by Roland de Ruiter to no avail.

[Jay Garcia]

On 13.03.2006 13:27, Roland de Ruiter wrote:

--- Original Message ---

> sean wrote:
>> How can I access http://192.168.1.100:6000# in FF1.5, works fine in IE
>> to make changes to NAS.
>> I cannot find any setting in Tools-Options menu to allow this.
>>
>> This is the dialog from FF1.5
>>
>> This address is restricted
>> This address uses a network port which is normally used for purposes
>> other than Web browsing. Firefox has canceled the request for your
>> protection.
>>
>> Thanks.
>

> Port 6000 is blocked by default (see
> <http://www.mozilla.org/projects/netlib/PortBanning.html>).
>
> To unblock this port (or other ports), type about:config in the address
> bar and locate the preference
>
> network.security.ports.banned.override
>
> It's possible that this pref doesn't exist (yet). To create it, do the
> following. Right-click on an existing pref (doesn't matter which) and
> from the popup menu select New > String. Type
> network.security.ports.banned.override
> as its name and
> 6000
> as its value.
>
> The preference accepts a comma separated list of ports or port ranges as
> its value, for example: 6000,8000-8088,500-511
>
> Apart from the "network.security.ports.banned.override" pref (used to
> *enable* ports), there's also the "network.security.ports.banned"
> preference for *disabling* ports.
>
> Regards,
>
> Roland

No such pref here in 1.5.0.1 and adding it in doesn't work either.

--
Jay Garcia Netscape/Mozilla Champion
UFAQ - http://www.UFAQ.org

[gwtc]

"network.security.ports.banned.override" yes, but no to
"network.security.ports.banned"

for more info, see: http://preferential.mozdev.org/preferences.html

[Roland de Ruiter]

There should be *no* leading or trailing spaces in the name of the pref.

To remove the faulty pref from the about:config list, right-click on the
pref and select 'Reset' from the popup menu. When you open a new tab
with about:config (or after restarting Firefox), the pref shouldn't be
there any more (if it didn't appear in the about:config list in the
first place).

In your profile directory (see gwtc's reply for its location) there
should be a file named
prefs.js
which contains the prefs that have been set by you (i.e. different from
Firefox' default values, bold in the about:config list). Like gwtc
wrote, the user.js file doesn't exist by default, and you won't find it
in the Firefox installation directory, but it should be located in your
profile directory.

[X11 is a GUI framework for Unix systems. For more info see
<http://en.wikipedia.org/wiki/History_of_the_graphical_user_interface#The_X_Window_System>
or <http://en.wikipedia.org/wiki/X_Window_System>.]

Regards,

Roland

[Roland de Ruiter]

The pref isn't there by default, so that's OK.

What doesn't work? After adding the pref (...banned.override), when you
visit <http://192.168.1.100:6000>the value 6000, did you get a "The
connection has timed out" message, instead of "This address is
restricted" message? If this is the case, the pref does work properly.

Regards,

Roland

[Melchert Fruitema]

On 14-03-2006 06:03 CET, gwtc composed this enchanting statement:

> Jay Garcia wrote:
>> On 13.03.2006 13:27, Roland de Ruiter wrote:

>> <x>

>>> Port 6000 is blocked by default (see
>>> <http://www.mozilla.org/projects/netlib/PortBanning.html>).
>>>
>>> To unblock this port (or other ports), type about:config in the
>>> address bar and locate the preference
>>> network.security.ports.banned.override
>>>
>>> It's possible that this pref doesn't exist (yet). To create it, do
>>> the following. Right-click on an existing pref (doesn't matter
>>> which) and from the popup menu select New > String. Type
>>> network.security.ports.banned.override as its name and 6000 as its
>>> value.
>>>
>>> The preference accepts a comma separated list of ports or port
>>> ranges as its value, for example: 6000,8000-8088,500-511
>>>
>>> Apart from the "network.security.ports.banned.override" pref (used
>>> to *enable* ports), there's also the "network.security.ports.banned"
>>> preference for *disabling* ports.

>> No such pref here in 1.5.0.1 and adding it in doesn't work either.
> "network.security.ports.banned.override" yes, but no to
> "network.security.ports.banned"
>
> for more info, see: http://preferential.mozdev.org/preferences.html
>

This reference states that the override only works for port numbers
below 1024.

--
Kind regards,

Melchert

MacOS 10.3.9/Firefox 1.5/Thunderbird 1.5

[Roland de Ruiter]

The page must be wrong, then 8-). It also works for port 6000 (in
FF1.5.0.1).

Regards,

Roland

[Jay Garcia]

On 13.03.2006 23:03, gwtc wrote:

--- Original Message ---

>> No such pref here in 1.5.0.1 and adding it in doesn't work either.
>>
> "network.security.ports.banned.override" yes, but no to
> "network.security.ports.banned"
>
> for more info, see: http://preferential.mozdev.org/preferences.html
>

Like I said, it doesn't work here for .override port 6000 .. Ok, I
didn't specify port 6000 but that should be "understood" as it is the
topic of discussion.

Also, on the preferential site, it mentions:

"Allow Mozilla to retrieve web pages from non-standard ports below 1024"

"Below" 1024.

I added the preference and port 6000 still brought up the error message.

[Jay Garcia]

On 14.03.2006 05:27, Roland de Ruiter wrote:

--- Original Message ---

> The page must be wrong, then 8-). It also works for port 6000 (in
> FF1.5.0.1).
>
> Regards,
>
> Roland

Doesn't work here in my 1.5.0.1 .. Either you or I have something else
configured for mine to disallow or yours to allow, dunno.

[Jay Garcia]

--- Original Message ---

I can't access that local IP address, but typing it in anyway to
reference the port 6000, it still produces the "restricted" message. As
I replied to you in another message, I may possibly have something else
active in my prefs that will not allow it, who knows.

[Melchert Fruitema]

On 14-03-2006 12:27 CET, Roland de Ruiter composed this enchanting
statement:

Yes, indeed. Should have tried it on (my own) IP address. That attempt
gives:

Unable to connect

Firefox can't establish a connection to the server at 192.168.11.2:6000.

* The site could be temporarily unavailable or too busy. Try again
in a few
moments.

* If you are unable to load any pages, check your computer's network
connection.

* If your computer or network is protected by a firewall or proxy,
make sure
that Firefox is permitted to access the Web.
:-)

[sean]

Yes, Roland you are right,it works for port 6000(FF1.5.0.1).
Make sure there is no extra spaces either before or at the end of
"network.security.ports.banned.override" which I made earlier and did
not how to delete the entry. Now everything works fine.
THANK YOU very much guys.