Re: Browser not authentication-capable or authentication failed.

2017-01-09 Thread David C. Mores 

Edmund Wong wrote:

David C. Mores wrote:

I am trying to login on my Cisco/Linksys WRT120N home router admin page
at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting
for 'A username and password are being requested by http://192.168.0.1.
The site says: "WRT120N"'  Clicking the OK button after entering the
info causes the window to close, but pop up again.  Clicking the Cancel
button results in an error page:

401 Authorization Required
Browser not authentication-capable or authentication failed.

I think this may be a bug in seamonkey V2.46 Build identifier:
20161213183751 because the very same login using the Google Chrome or MS
Edge browsers work just fine - i.e. a successful router login.



I'm not entirely sure why the build identifier would make any
difference; and since you've tried the safe mode, can you try it
with 2.40?  What about Firefox?

Edmund

Yes it does work for SM 2.40, and no it does not work in the latest FF 
50.  What do you recommend now?


Dave
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Browser not authentication-capable or authentication failed.

2017-01-08 Thread NoOp 
On 1/7/2017 11:43 AM, David C. Mores wrote:
> Lee wrote:
>> On 1/7/17, David E. Ross  wrote:
>>> On 1/7/2017 9:27 AM, David C. Mores wrote:
 I am trying to login on my Cisco/Linksys WRT120N home router admin page
 at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting
 for 'A username and password are being requested by http://192.168.0.1.
 The site says: "WRT120N"'  Clicking the OK button after entering the
 info causes the window to close, but pop up again.  Clicking the Cancel
 button results in an error page:

 401 Authorization Required
 Browser not authentication-capable or authentication failed.

 I think this may be a bug in seamonkey V2.46 Build identifier:
 20161213183751 because the very same login using the Google Chrome or MS
 Edge browsers work just fine - i.e. a successful router login.

 I can find no setting in about:config that seem to control
 authentication capabilities.

 My workaround is to use the other browsers, but I normally use seamonkey
 for everything.

 Have you seen this?  Ideas?  Bug report it?

 Thanks,
 Dave

>>>
>>> This might be bug #435013.  See
>>> .  Currently, there
>>> is no work-around; and I do not see any indication that a fix is being
>>> developed.
>>
>> Probably not since it's clear-text instead of https:
 A username and password are being requested by http://192.168.0.1
>>
>> I'd check javascript is enabled & cookies are allowed, then try
>> disabling addons or starting seamonkey in safe mode.
>>
>> Lee
>>
> 
> No joy on Lee's suggestions.  Identical symptoms.
> 
> David Ross's pointer to bug 435013, I think, does not apply, as Lee 
> pointed out.  Not a cert issue.
> 
> I'll wait to see if other suggestions come in before filing a bug report.
> 
> Dave
> 

I seem to recall a similar problem accessing a Linksys E1200 a while
back. I can't remember exactly what fixed it but 'think' I resolved it
by enabling TLS 1.0 (Preferences|Privacy & Security|SSL/TLS). For certs
I have: 'Client Certificate Selection: Select Automatically', OCSP
unchecked.

There are also suggestions that turning off "Do not track" does the trick:
https://community.linksys.com/t5/Wireless-Routers/Firefox-cannot-access-WRT120N-setup-but-IE-can/td-p/366977/page/3
and
https://www.google.com/#q=Browser+not+authentication-capable+or+authentication+failed
but I don't recall ever turning on that in Firefox or SeaMonkey - might
be worth checking.


___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Browser not authentication-capable or authentication failed.

2017-01-08 Thread Edmund Wong 
David C. Mores wrote:
> I am trying to login on my Cisco/Linksys WRT120N home router admin page
> at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting
> for 'A username and password are being requested by http://192.168.0.1.
> The site says: "WRT120N"'  Clicking the OK button after entering the
> info causes the window to close, but pop up again.  Clicking the Cancel
> button results in an error page:
> 
> 401 Authorization Required
> Browser not authentication-capable or authentication failed.
> 
> I think this may be a bug in seamonkey V2.46 Build identifier:
> 20161213183751 because the very same login using the Google Chrome or MS
> Edge browsers work just fine - i.e. a successful router login.
> 

I'm not entirely sure why the build identifier would make any
difference; and since you've tried the safe mode, can you try it
with 2.40?  What about Firefox?

Edmund
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Browser not authentication-capable or authentication failed.

2017-01-07 Thread David C. Mores 

Lee wrote:

On 1/7/17, David E. Ross  wrote:

On 1/7/2017 9:27 AM, David C. Mores wrote:

I am trying to login on my Cisco/Linksys WRT120N home router admin page
at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting
for 'A username and password are being requested by http://192.168.0.1.
The site says: "WRT120N"'  Clicking the OK button after entering the
info causes the window to close, but pop up again.  Clicking the Cancel
button results in an error page:

401 Authorization Required
Browser not authentication-capable or authentication failed.

I think this may be a bug in seamonkey V2.46 Build identifier:
20161213183751 because the very same login using the Google Chrome or MS
Edge browsers work just fine - i.e. a successful router login.

I can find no setting in about:config that seem to control
authentication capabilities.

My workaround is to use the other browsers, but I normally use seamonkey
for everything.

Have you seen this?  Ideas?  Bug report it?

Thanks,
Dave



This might be bug #435013.  See
.  Currently, there
is no work-around; and I do not see any indication that a fix is being
developed.


Probably not since it's clear-text instead of https:

A username and password are being requested by http://192.168.0.1


I'd check javascript is enabled & cookies are allowed, then try
disabling addons or starting seamonkey in safe mode.

Lee



No joy on Lee's suggestions.  Identical symptoms.

David Ross's pointer to bug 435013, I think, does not apply, as Lee 
pointed out.  Not a cert issue.


I'll wait to see if other suggestions come in before filing a bug report.

Dave
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Browser not authentication-capable or authentication failed.

2017-01-07 Thread Lee 
On 1/7/17, David E. Ross  wrote:
> On 1/7/2017 9:27 AM, David C. Mores wrote:
>> I am trying to login on my Cisco/Linksys WRT120N home router admin page
>> at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting
>> for 'A username and password are being requested by http://192.168.0.1.
>> The site says: "WRT120N"'  Clicking the OK button after entering the
>> info causes the window to close, but pop up again.  Clicking the Cancel
>> button results in an error page:
>>
>> 401 Authorization Required
>> Browser not authentication-capable or authentication failed.
>>
>> I think this may be a bug in seamonkey V2.46 Build identifier:
>> 20161213183751 because the very same login using the Google Chrome or MS
>> Edge browsers work just fine - i.e. a successful router login.
>>
>> I can find no setting in about:config that seem to control
>> authentication capabilities.
>>
>> My workaround is to use the other browsers, but I normally use seamonkey
>> for everything.
>>
>> Have you seen this?  Ideas?  Bug report it?
>>
>> Thanks,
>> Dave
>>
>
> This might be bug #435013.  See
> .  Currently, there
> is no work-around; and I do not see any indication that a fix is being
> developed.

Probably not since it's clear-text instead of https:
>> A username and password are being requested by http://192.168.0.1

I'd check javascript is enabled & cookies are allowed, then try
disabling addons or starting seamonkey in safe mode.

Lee
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Browser not authentication-capable or authentication failed.

2017-01-07 Thread David E. Ross 
On 1/7/2017 9:27 AM, David C. Mores wrote:
> I am trying to login on my Cisco/Linksys WRT120N home router admin page 
> at http://192.168.0.1/ using seamonkey.  I get a pop up window prompting 
> for 'A username and password are being requested by http://192.168.0.1. 
> The site says: "WRT120N"'  Clicking the OK button after entering the 
> info causes the window to close, but pop up again.  Clicking the Cancel 
> button results in an error page:
> 
> 401 Authorization Required
> Browser not authentication-capable or authentication failed.
> 
> I think this may be a bug in seamonkey V2.46 Build identifier: 
> 20161213183751 because the very same login using the Google Chrome or MS 
> Edge browsers work just fine - i.e. a successful router login.
> 
> I can find no setting in about:config that seem to control 
> authentication capabilities.
> 
> My workaround is to use the other browsers, but I normally use seamonkey 
> for everything.
> 
> Have you seen this?  Ideas?  Bug report it?
> 
> Thanks,
> Dave
> 

This might be bug #435013.  See
.  Currently, there
is no work-around; and I do not see any indication that a fix is being
developed.

-- 

David E. Ross
.

The only reason we have so many laws is that not enough people will do
the right thing.  (© 1997 by David Ross)
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey