Re: router login - error 401, unauthorized

2018-08-17 Thread arpannarita 
The 401 Unauthorized blunder is a HTTP status code that implies the page you 
were attempting to get to can't be stacked until you first sign in with a 
legitimate client ID and secret key. In the event that you have quite recently 
signed in and got the 401 Unauthorized mistake, it implies that the 
certifications you entered were invalid for reasons unknown

https://www.belkinroutersupportnumber.com/how-to-reset-recover-change-belkin-router-password-or-login/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

2018-06-26 Thread 420230102 
On Saturday, October 7, 2017 at 12:34:18 PM UTC-4, rjkrjk wrote:
> win7/64, SM 2.48
> 
> 
> attempted to log on to my router (Netgear AC1900/R7000) using the all of the 
> following
> standard netgear address
> 10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net
> 
> NONE workand I get an 401 Error,   unauthorized
> 
> however, when using FF 56, I have NO Problem accessing the router
> using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)
> 
> the 401 error message
> Access to this resource is denied, your client has not supplied the correct 
> authentication
> 
> does even have the netgear standard 2 line sign in box, I'm not supplying an 
> passwords
> just typing the netgear url,
> where is SM looking in order to get the correct authtication
> 
> I have cleared cache, removed the 192.168.x.x passwords
> 
> not really sure if Seamonkey is at fault here,   comments appreciated !
> 
> ---
> This email has been checked for viruses by AVG.
> http://www.avg.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

2018-06-26 Thread 420230102 
On Saturday, October 7, 2017 at 12:34:18 PM UTC-4, rjkrjk wrote:
> win7/64, SM 2.48
> 
> 
> attempted to log on to my router (Netgear AC1900/R7000) using the all of the 
> following
> standard netgear address
> 10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net
> 
> NONE workand I get an 401 Error,   unauthorized
> 
> however, when using FF 56, I have NO Problem accessing the router
> using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)
> 
> the 401 error message
> Access to this resource is denied, your client has not supplied the correct 
> authentication
> 
> does even have the netgear standard 2 line sign in box, I'm not supplying an 
> passwords
> just typing the netgear url,
> where is SM looking in order to get the correct authtication
> 
> I have cleared cache, removed the 192.168.x.x passwords
> 
> not really sure if Seamonkey is at fault here,   comments appreciated !
> 
> ---
> This email has been checked for viruses by AVG.
> http://www.avg.com

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

Re: router login - error 401, unauthorized

2017-10-13 Thread Keith N. McKenna 
On 10/13/2017 3:05 PM, Mason83 wrote:
> On 10/10/2017 08:38, Frank-Rainer Grahl wrote:
> 
>> You can update Adrians build to the official candidate 3:
>>
>> https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/
>>
>> Should behave way better than the May build I hope :)
> 
> No Win64 build?
> 
> Regards.
> 
Win 64 has never been a supported build from the project. All win64
builds were unofficial ones contributed by individual members of the
community.

Regards
Keith



signature.asc
Description: OpenPGP digital signature
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

2017-10-13 Thread Mason83 
On 10/10/2017 08:38, Frank-Rainer Grahl wrote:

> You can update Adrians build to the official candidate 3:
> 
> https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/
> 
> Should behave way better than the May build I hope :)

No Win64 build?

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

Re: router login - error 401, unauthorized

2017-10-11 Thread Daniel 

On 11/10/2017 6:12 PM, Frank-Rainer Grahl wrote:

So using .1 does not distinguish the official build from
Adrian's ESR-based builds.


1 will be release channel and 2 it will distingush it from his 2.49
(without the .1)

FRG


Frank-Rainer, over this recent period where the SeaMonkey-Project has 
had troubles getting their Official SeaMonkey releases out, it seems to 
me that Adrian has been releasing his own versions, from his server or 
wherever, with the same User Agent as the Official version.


Perhaps it would be better if Adrian were to alter his User Agent 
string, as Hartmut Figge does with his personally built versions by 
adding, in Hartmut's case, an "-h" to the end, e.g. SeaMonkey/2.43a1-h.


--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 
SeaMonkey/2.48 Build identifier: 20170329183526


Go Dallas Cowgirls!!  Err!! ... Um!! .. I mean *Go Dallas Cowboys* !!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

2017-10-11 Thread Frank-Rainer Grahl 

> So using .1 does not distinguish the official build from
> Adrian's ESR-based builds.
>
1 will be release channel and 2 it will distingush it from his 2.49 
(without the .1)


FRG

Mason83 wrote:

On 10/10/2017 08:38, Frank-Rainer Grahl wrote:


You can update Adrians build to the official candidate 3:

https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/

Should behave way better than the May build I hope :)

.1 because Adrian built 2.49 from the comm-release branch and we wanted
to distinguish it from this one. All 2.49.1 ones are build from the
esr52 branch.


I'm confused. Adrian's build shows up as
SeaMonkey version 2.49.1
You are currently on the esr update channel.
User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1

So using .1 does not distinguish the official build from
Adrian's ESR-based builds.


2.49.1 is at current esr52.4 level. The next release will
be .2 Hopefully when 52.5 arrives but depends on how long it takes to
bake a release and how much time ewong has. In any case there will be a
.2 at a future 52.x esr level.


Thanks for that info.

Regards.



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

Re: router login - error 401, unauthorized

2017-10-10 Thread Mason83 
On 10/10/2017 08:38, Frank-Rainer Grahl wrote:

> You can update Adrians build to the official candidate 3:
> 
> https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/
> 
> Should behave way better than the May build I hope :)
> 
> .1 because Adrian built 2.49 from the comm-release branch and we wanted 
> to distinguish it from this one. All 2.49.1 ones are build from the 
> esr52 branch.

I'm confused. Adrian's build shows up as
SeaMonkey version 2.49.1
You are currently on the esr update channel.
User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1

So using .1 does not distinguish the official build from
Adrian's ESR-based builds.

> 2.49.1 is at current esr52.4 level. The next release will 
> be .2 Hopefully when 52.5 arrives but depends on how long it takes to 
> bake a release and how much time ewong has. In any case there will be a 
> .2 at a future 52.x esr level.

Thanks for that info.

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

Re: router login - error 401, unauthorized

2017-10-10 Thread Frank-Rainer Grahl 

You can update Adrians build to the official candidate 3:

https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/

Should behave way better than the May build I hope :)

.1 because Adrian built 2.49 from the comm-release branch and we wanted 
to distinguish it from this one. All 2.49.1 ones are build from the 
esr52 branch. 2.49.1 is at current esr52.4 level. The next release will 
be .2 Hopefully when 52.5 arrives but depends on how long it takes to 
bake a release and how much time ewong has. In any case there will be a 
.2 at a future 52.x esr level.


FRG

Mason83 wrote:

On 08/10/2017 18:44, Frank-Rainer Grahl wrote:


Likely point 3 in the known issues in the 2.48 release notes:

https://www.seamonkey-project.org/releases/seamonkey2.48/

Fix will be in 2.49.1.

Maybe we should just drop the release notes and tell everyone to open a
lenghty thread in one of the support groups if he7she/it runs into a known
problem :)


FWIW, the problem still existed in 2.49.1 from 20170528045907
Which is expected since you FIXED the bug in August...

What does the .1 mean? When will it increase to .2?

Regards.



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

Re: router login - error 401, unauthorized

2017-10-09 Thread rjkrjk 



Lee wrote on 10/8/17 6:47 PM:

On 10/8/17, Frank-Rainer Grahl  wrote:

Likely point 3 in the known issues in the 2.48 release notes:

https://www.seamonkey-project.org/releases/seamonkey2.48/


My understanding is that the 'steps to reproduce' requires one to have
only the email client running, open the browser from the email client
and then try to login somewhere.

So the work-around is to open the browser, from there open email/news
reader/whatever **and leave the browser window open** - correct?


leave broswer open ONLY.that worked for me.
(as well as using firefox)













Fix will be in 2.49.1.

Maybe we should just drop the release notes and tell everyone to open a
lenghty thread in one of the support groups if he7she/it runs into a known
problem :)


I would have never guessed that "you may no longer be prompted for
authentication in certain scenarios" meant getting a 401 error when
trying to login somewhere.  In my mind, not being prompted for
authentication means not getting the userid/password popup.

Lee



FRG


Jonathan Wilson wrote:

I just quit and restarted SeaMonkey and like magic the login worked if I
went
straight there and didn't open anything else (mail, ChatZilla etc)

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



---
This email has been checked for viruses by AVG.
http://www.avg.com


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

Re: router login - error 401, unauthorized

2017-10-09 Thread Mason83 
On 08/10/2017 18:44, Frank-Rainer Grahl wrote:

> Likely point 3 in the known issues in the 2.48 release notes:
> 
> https://www.seamonkey-project.org/releases/seamonkey2.48/
> 
> Fix will be in 2.49.1.
> 
> Maybe we should just drop the release notes and tell everyone to open a 
> lenghty thread in one of the support groups if he7she/it runs into a known 
> problem :)

FWIW, the problem still existed in 2.49.1 from 20170528045907
Which is expected since you FIXED the bug in August...

What does the .1 mean? When will it increase to .2?

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

Re: router login - error 401, unauthorized

2017-10-08 Thread Paul B. Gallagher 

Lee wrote:


On 10/8/17, Paul B. Gallagher 
wrote:

Lee wrote:


I would have never guessed that "you may no longer be prompted
for authentication in certain scenarios" meant getting a 401
error when trying to login somewhere. In my mind, not being
prompted for authentication means not getting the userid/password
popup.


Keep reading.


"The problem is tracked in bug 1347857. Check the bug for
workarounds. The issue will be fixed in the next SeaMonkey release."

and that's it for the item in the release notes.


Sure. So read the bug:



The bug goes on to say that the failure to prompt eventually leads
to an error message. Presumably because failure to prompt leads to
failure to authenticate (you can't answer a question it doesn't
ask), so when the unauthorized user tries to execute commands, they
are rejected.


I followed the directions to duplicate the bug & never saw a failure
to prompt.  Have you seen something different?


I'm not having trouble.

But here are some quotes from the bug:

"Summary: blank login not displaying error → Browser: Basic 
Authentication will not open auth. dialog (eventually error message 
instead) under particular Email Window related conditions


...

Workaround to get over the error just close the mail window and reopen it.

...

The required fixes are now in the TB mozilla-esr52 release branch which 
we will use for building 2.49.1."



^shrug^ but I'd bet even if the release notes had said something
about a 401 error when trying to authenticate we'd have still had
this conversation :)


Could be. If you sample enough people, some of them will understand a 
given message differently and some won't understand it at all. That's life.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

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

Re: router login - error 401, unauthorized

2017-10-08 Thread Lee 
On 10/8/17, Paul B. Gallagher  wrote:
> Lee wrote:
>
>> I would have never guessed that "you may no longer be prompted for
>> authentication in certain scenarios" meant getting a 401 error when
>> trying to login somewhere. In my mind, not being prompted for
>> authentication means not getting the userid/password popup.
>
> Keep reading.

"The problem is tracked in bug 1347857. Check the bug for workarounds.
The issue will be fixed in the next SeaMonkey release."

and that's it for the item in the release notes.

> The bug goes on to say that the failure to prompt
> eventually leads to an error message. Presumably because failure to
> prompt leads to failure to authenticate (you can't answer a question it
> doesn't ask), so when the unauthorized user tries to execute commands,
> they are rejected.

I followed the directions to duplicate the bug & never saw a failure
to prompt.  Have you seen something different?

If you haven't, try it yourself:
- open seamonkey browser
- click on window / mail & newsgroups
- close the browser window
- from the mail & newsgroups window click on window / browser
- goto https://auth-demo.aerobatic.io/
- click on tools / web development / toggle tools
- click on the network tab (so you can see the status code returned)
- click on the standard auth button
- get the userid/password popup
- give it aerobatic/aerobatic as the userid / password
- see the 401 error returned

^shrug^ but I'd bet even if the release notes had said something about
a 401 error when trying to authenticate we'd have still had this
conversation :)

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

Re: router login - error 401, unauthorized

2017-10-08 Thread Paul B. Gallagher 

Lee wrote:


I would have never guessed that "you may no longer be prompted for
authentication in certain scenarios" meant getting a 401 error when
trying to login somewhere. In my mind, not being prompted for
authentication means not getting the userid/password popup.


Keep reading. The bug goes on to say that the failure to prompt 
eventually leads to an error message. Presumably because failure to 
prompt leads to failure to authenticate (you can't answer a question it 
doesn't ask), so when the unauthorized user tries to execute commands, 
they are rejected.


--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

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

Re: router login - error 401, unauthorized

2017-10-08 Thread Lee 
On 10/8/17, Frank-Rainer Grahl  wrote:
> Likely point 3 in the known issues in the 2.48 release notes:
>
> https://www.seamonkey-project.org/releases/seamonkey2.48/

My understanding is that the 'steps to reproduce' requires one to have
only the email client running, open the browser from the email client
and then try to login somewhere.

So the work-around is to open the browser, from there open email/news
reader/whatever **and leave the browser window open** - correct?

> Fix will be in 2.49.1.
>
> Maybe we should just drop the release notes and tell everyone to open a
> lenghty thread in one of the support groups if he7she/it runs into a known
> problem :)

I would have never guessed that "you may no longer be prompted for
authentication in certain scenarios" meant getting a 401 error when
trying to login somewhere.  In my mind, not being prompted for
authentication means not getting the userid/password popup.

Lee

>
> FRG
>
>
> Jonathan Wilson wrote:
>> I just quit and restarted SeaMonkey and like magic the login worked if I
>> went
>> straight there and didn't open anything else (mail, ChatZilla etc)
> ___
> support-seamonkey mailing list
> support-seamonkey@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-seamonkey
>
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

2017-10-08 Thread Frank-Rainer Grahl 

Likely point 3 in the known issues in the 2.48 release notes:

https://www.seamonkey-project.org/releases/seamonkey2.48/

Fix will be in 2.49.1.

Maybe we should just drop the release notes and tell everyone to open a 
lenghty thread in one of the support groups if he7she/it runs into a known 
problem :)


FRG


Jonathan Wilson wrote:
I just quit and restarted SeaMonkey and like magic the login worked if I went 
straight there and didn't open anything else (mail, ChatZilla etc)

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

Re: router login - error 401, unauthorized

2017-10-08 Thread David E. Ross 
On 10/8/2017 4:26 AM, Jonathan Wilson wrote:
> I just quit and restarted SeaMonkey and like magic the login worked if I 
> went straight there and didn't open anything else (mail, ChatZilla etc)
> 
Windows 7
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101
SeaMonkey/2.48
with 28 enabled extensions and a profile that is at least
4 years old
Netgear N300 Wireless Router Model WNR2000v5

I have been Web surfing this morning for about 30 minutes.  I just now
logged-in to my router without any problem.  The router's user interface
has a purple logout button in the upper-right corner.

-- 
David E. Ross


By allowing employers to eliminate coverage for birth control
from their insurance plans, President Trump has guaranteed there
will be an increase in the demand for abortions.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

2017-10-08 Thread Jonathan Wilson 
I just quit and restarted SeaMonkey and like magic the login worked if I 
went straight there and didn't open anything else (mail, ChatZilla etc)

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

Re: router login - error 401, unauthorized

2017-10-08 Thread Jonathan Wilson 

I am also seeing the same issue.
I have a Netgear DGN2200M router. If I access the admin interface via 
SeaMonkey 2.48 I get the "401 Unauthorized" screen even though I have 
previously stored the correct username and password in the SeaMonkey 
password manager (and even if SM didn't have that info for some reason, it 
should be prompting me for it with a dialog box)


If I try to access the same admin interface via Internet Explorer it works 
just fine.

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

Re: router login - error 401, unauthorized

2017-10-08 Thread Patrick Bégou 
It is not related to a router connection. I had this with web switchs 
interfaces, DELL idrac web interfaces, web interfaces of proxmoxVE 
servers, BackupPC web interface... some, but not all...
It is a problem with the authentication mechanism in seamonkey recent 
version. There is a bug report yet for this problem.


I had got help from this forum to solve it ;-) some weeks ago.

Patrick

Rick & Sharon a écrit :

Patrick Bégou wrote:

I had also such a problem some weeks ago after a seamonkey upgrade. It
seams to be a bug in seamonkey.
Try to connect without the mail window of seamonkey open.
For me it works.

Patrick

Lee a écrit :

On 10/7/17, rjkrjk  wrote:

win7/64, SM 2.48

wireless, rj-45 ethernet connection to your netgear router or ???


attempted to log on to my router (Netgear AC1900/R7000) using the all
of the
following
standard netgear address
10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

don't use routerlogin.net -- it works only if the netgear is your dns
server
which it probably is, ok, but do you check which wireless network
you're connected to before entering the userid/password?

& while we're on the topic:
username: admin, pasword: password
that got changed when you first connected the netgear to your network
- right?


NONE workand I get an 401 Error, unauthorized

have you looked at
https://kb.netgear.com/app/answers/detail/a_id/27199

if nothing there helps,
   if not already, connect your pc directly to the netgear with an
ethernet cable, turn off wireless on the pc & try again
   create a new SM profile & try again


however, when using FF 56, I have NO Problem accessing the router
using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

You're using FF & SM on the same machine?


the 401 error message
Access to this resource is denied, your client has not supplied the
correct
authentication

does even have the netgear standard 2 line sign in box, I'm not
supplying an
passwords
just typing the netgear url,
where is SM looking in order to get the correct authtication

You could always install wireshark
   https://www.wireshark.org/download.html
and see what's actually happening.


I have cleared cache, removed the 192.168.x.x passwords

not really sure if Seamonkey is at fault here,   comments 
appreciated !

I have a netgear at home also.  No problems getting in using seamonkey.

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



Eureka!  It is/must be something in SM, because I can confirm that I 
can once more log into the router, even after having gotten the 
'unauthorised' web page, just by closing my mail client and refreshing 
the web page.


FYI: I am logging into a (Billion) BiPAC 8900AX2400 router through an 
RJ45 cable connection (this PC doesn't have/use wireless). There is no 
'logoff' link in the router interface, so the only way to disconnect 
is to close that browser tab/window.


I guess this rates an entry in Bugzilla?

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



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

Re: router login - error 401, unauthorized

2017-10-08 Thread Rick & Sharon 

Patrick Bégou wrote:

I had also such a problem some weeks ago after a seamonkey upgrade. It
seams to be a bug in seamonkey.
Try to connect without the mail window of seamonkey open.
For me it works.

Patrick

Lee a écrit :

On 10/7/17, rjkrjk  wrote:

win7/64, SM 2.48

wireless, rj-45 ethernet connection to your netgear router or ???


attempted to log on to my router (Netgear AC1900/R7000) using the all
of the
following
standard netgear address
10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

don't use routerlogin.net -- it works only if the netgear is your dns
server
which it probably is, ok, but do you check which wireless network
you're connected to before entering the userid/password?

& while we're on the topic:
username: admin, pasword: password
that got changed when you first connected the netgear to your network
- right?


NONE workand I get an 401 Error,   unauthorized

have you looked at
https://kb.netgear.com/app/answers/detail/a_id/27199

if nothing there helps,
   if not already, connect your pc directly to the netgear with an
ethernet cable, turn off wireless on the pc & try again
   create a new SM profile & try again


however, when using FF 56, I have NO Problem accessing the router
using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

You're using FF & SM on the same machine?


the 401 error message
Access to this resource is denied, your client has not supplied the
correct
authentication

does even have the netgear standard 2 line sign in box, I'm not
supplying an
passwords
just typing the netgear url,
where is SM looking in order to get the correct authtication

You could always install wireshark
   https://www.wireshark.org/download.html
and see what's actually happening.


I have cleared cache, removed the 192.168.x.x passwords

not really sure if Seamonkey is at fault here,   comments appreciated !

I have a netgear at home also.  No problems getting in using seamonkey.

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



Eureka!  It is/must be something in SM, because I can confirm that I can 
once more log into the router, even after having gotten the 
'unauthorised' web page, just by closing my mail client and refreshing 
the web page.


FYI: I am logging into a (Billion) BiPAC 8900AX2400 router through an 
RJ45 cable connection (this PC doesn't have/use wireless).  There is no 
'logoff' link in the router interface, so the only way to disconnect is 
to close that browser tab/window.


I guess this rates an entry in Bugzilla?

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

Re: router login - error 401, unauthorized

2017-10-08 Thread Patrick Bégou 
I had also such a problem some weeks ago after a seamonkey upgrade. It 
seams to be a bug in seamonkey.

Try to connect without the mail window of seamonkey open.
For me it works.

Patrick

Lee a écrit :

On 10/7/17, rjkrjk  wrote:

win7/64, SM 2.48

wireless, rj-45 ethernet connection to your netgear router or ???


attempted to log on to my router (Netgear AC1900/R7000) using the all of the
following
standard netgear address
10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

don't use routerlogin.net -- it works only if the netgear is your dns server
which it probably is, ok, but do you check which wireless network
you're connected to before entering the userid/password?

& while we're on the topic:
username: admin, pasword: password
that got changed when you first connected the netgear to your network - right?


NONE workand I get an 401 Error,   unauthorized

have you looked at
https://kb.netgear.com/app/answers/detail/a_id/27199

if nothing there helps,
   if not already, connect your pc directly to the netgear with an
ethernet cable, turn off wireless on the pc & try again
   create a new SM profile & try again


however, when using FF 56, I have NO Problem accessing the router
using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

You're using FF & SM on the same machine?


the 401 error message
Access to this resource is denied, your client has not supplied the correct
authentication

does even have the netgear standard 2 line sign in box, I'm not supplying an
passwords
just typing the netgear url,
where is SM looking in order to get the correct authtication

You could always install wireshark
   https://www.wireshark.org/download.html
and see what's actually happening.


I have cleared cache, removed the 192.168.x.x passwords

not really sure if Seamonkey is at fault here,   comments appreciated !

I have a netgear at home also.  No problems getting in using seamonkey.

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



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

Re: router login - error 401, unauthorized

2017-10-07 Thread Lee 
On 10/7/17, rjkulman  wrote:
>
> rjkulman wrote on 10/7/17 5:56 PM:
>>
>>
>> Lee wrote on 10/7/17 5:48 PM:
>>> On 10/7/17, rjkulman  wrote:
>>>
 I created a new profile for this "test"
 and it worked Ok  =>  10.0.0.1, and the standard netgear box showed up
 was able to login and had all the netgear info there

 so   Im gonna say that something in SM, add on ??? is not allowing
 access
>>>
>>> It's not SeaMonkey since it works using a new profile.
>>>
>>> I'd start with installing addons one at a time & logging into the
>>> Netgear to see if/which addon is causing the problem.
>>>
>>> Regards,
>>> Lee
>>
>> these are the only add ons that currently show
>> Java, Nvidia (video ) PDF -xchange (pdf viewer), 2007 MS office
>> Picasa, shockwave
>>
>> will "never activate" all, and see what happens, then allow 1 at a time

Noo
make only _one_ change at a time.

> with all NEVER activate, no difference
> still cant access 10.0.0.1

_still_ can't?  You said that you created a new profile & were able to
log in to your netgear, so shouldn't it be "can't access 10.0.0.1
_again_"?  as in you re-created the original problem behavior in your
new profile?

> just looked at my test profile
> it has all the same ad ons, and all marked "ask"
> same as my current profile

Try again with a new profile.
Log into your router
exit from the router however you normally exit
Log in again
If that works, then it's a profile problem

Make one change.  Restart Seamonkey. Do the login/exit/login again test.
If the test works then whatever change you made isn't the problem.

Make another change. Restart Seamonkey. Do the login/exit/login again test.
keep repeating until you make a change & can't log into your router.
That's probably the
problem.  Undo the change. Restart Seamonkey. Do the login/exit/login
again test.
works?  Yay!  you found the problem

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

Re: router login - error 401, unauthorized

2017-10-07 Thread Lee 
On 10/7/17, rjkulman  wrote:

> I created a new profile for this "test"
> and it worked Ok  =>  10.0.0.1, and the standard netgear box showed up
> was able to login and had all the netgear info there
>
> so   Im gonna say that something in SM, add on ??? is not allowing access

It's not SeaMonkey since it works using a new profile.

I'd start with installing addons one at a time & logging into the
Netgear to see if/which addon is causing the problem.

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

Re: router login - error 401, unauthorized

2017-10-07 Thread rjkrjk 



Lee wrote on 10/7/17 2:25 PM:

On 10/7/17, Rick & Sharon  wrote:

rjkrjk wrote:


attempted to log on to my router (Netgear AC1900/R7000)
and I get an 401 Error,   unauthorized


You're not alone, I started getting the same thing with my home router.
Until I saw this, I thought it was just my model of device.  If you
clear ALL your cookies and ALL cache, it'll work fine.  But only once:
the next time you try you'll get the 401 error again, until you clear ot
all your old data.

I'd love to know what this answer is, as well.  Every time I have to
clear everything out, the wife has to log into her pages manually again.


Do you use the logout button or just close the page/browser?

Lee

---
This email has been checked for viruses by AVG.
http://www.avg.com



just X out of it

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

Re: router login - error 401, unauthorized

2017-10-07 Thread Lee 
On 10/7/17, rjkulman  wrote:
>
> Lee wrote on 10/7/17 1:59 PM:
>> On 10/7/17, rjkrjk  wrote:
>>
>>> attempted to log on to my router (Netgear AC1900/R7000) using the all of
>>> the following standard netgear address
>>> 10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net
>>
>> don't use routerlogin.net -- it works only if the netgear is your dns server
>> which it probably is, ok, but do you check which wireless network
>> you're connected to before entering the userid/password?
>
> tested with all 4 potential log insonly 2 worked- with FF (10.0.0.1 and
> routerlogin)
> NONE worked with SM
>
> am connected to the netgear router, have tried both 2.4 and 5.0ghz
> no difference

ok - same pc, ff works, sm doesn't pretty much eliminates the wireless
network as the problem

>>> NONE workand I get an 401 Error,   unauthorized
>>
>> have you looked at
>> https://kb.netgear.com/app/answers/detail/a_id/27199
>>
>> if nothing there helps,
>>if not already, connect your pc directly to the netgear with an
>> ethernet cable, turn off wireless on the pc & try again
>>create a new SM profile & try again
>
> tried that also,   direct connect to netgear router, from the PC, no
> internet connection NONE of the URL's worked

did you create a new profile in SeaMonkey and try logging into your netgear?

My understanding is that a new profile starts off with an empty cache,
no saved credentials, default preferences & no plugins/addons.  So if
the problem is because of an addon, stale cache entry, changed pref
(eg. user.js), etc. a new profile eliminates all of those
possibilities.

>>> however, when using FF 56, I have NO Problem accessing the router
>>> using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)
>>
>> You're using FF & SM on the same machine?
>
> yes, both browsers are on the same system/machine
> which makes it really strange

yup

>>> I have cleared cache, removed the 192.168.x.x passwords

But the 192.168.x.x addresses aren't for your netgear.
Have you cleared the passwords for 10.0.0.1, routerlogin.net & routerlogin.com?

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

Re: router login - error 401, unauthorized

2017-10-07 Thread Lee 
On 10/7/17, Rick & Sharon  wrote:
> rjkrjk wrote:
>>
>> attempted to log on to my router (Netgear AC1900/R7000)
>>and I get an 401 Error,   unauthorized
>
> You're not alone, I started getting the same thing with my home router.
> Until I saw this, I thought it was just my model of device.  If you
> clear ALL your cookies and ALL cache, it'll work fine.  But only once:
> the next time you try you'll get the 401 error again, until you clear ot
> all your old data.
>
> I'd love to know what this answer is, as well.  Every time I have to
> clear everything out, the wife has to log into her pages manually again.

Do you use the logout button or just close the page/browser?

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

Re: router login - error 401, unauthorized

2017-10-07 Thread Lemuel Johnson 

On 10/7/2017 11:58 AM, rjkrjk wrote:



Rick & Sharon wrote on 10/7/17 12:51 PM:

rjkrjk wrote:

win7/64, SM 2.48


attempted to log on to my router (Netgear AC1900/R7000) using the all of
the following
standard netgear address
10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

NONE workand I get an 401 Error,   unauthorized

however, when using FF 56, I have NO Problem accessing the router
using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

the 401 error message
Access to this resource is denied, your client has not supplied the
correct authentication

does even have the netgear standard 2 line sign in box, I'm not
supplying an passwords
just typing the netgear url,
where is SM looking in order to get the correct authtication

I have cleared cache, removed the 192.168.x.x passwords

not really sure if Seamonkey is at fault here,   comments appreciated !

---
This email has been checked for viruses by AVG.
http://www.avg.com


You're not alone, I started getting the same thing with my home
router. Until I saw this, I
thought it was just my model of device.  If you clear ALL your cookies
and ALL cache, it'll
work fine.  But only once: the next time you try you'll get the 401
error again, until you
clear ot all your old data.

I'd love to know what this answer is, as well.  Every time I have to
clear everything out,
the wife has to log into her pages manually again.



just gonna use FF to access the router, dont think I wanna have to clear
everything each time I wanna do something/upgrade/update the
router.PITA
maybe someone else will have another answer,tks




No problem here accessing my Netgear WNR3500Lv2 through cable connection 
with SM 2.48, W7/64.


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

Re: router login - error 401, unauthorized

2017-10-07 Thread Lee 
On 10/7/17, rjkrjk  wrote:
> win7/64, SM 2.48

wireless, rj-45 ethernet connection to your netgear router or ???

> attempted to log on to my router (Netgear AC1900/R7000) using the all of the
> following
> standard netgear address
> 10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

don't use routerlogin.net -- it works only if the netgear is your dns server
which it probably is, ok, but do you check which wireless network
you're connected to before entering the userid/password?

& while we're on the topic:
username: admin, pasword: password
that got changed when you first connected the netgear to your network - right?

> NONE workand I get an 401 Error,   unauthorized

have you looked at
https://kb.netgear.com/app/answers/detail/a_id/27199

if nothing there helps,
  if not already, connect your pc directly to the netgear with an
ethernet cable, turn off wireless on the pc & try again
  create a new SM profile & try again

> however, when using FF 56, I have NO Problem accessing the router
> using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

You're using FF & SM on the same machine?

> the 401 error message
> Access to this resource is denied, your client has not supplied the correct
> authentication
>
> does even have the netgear standard 2 line sign in box, I'm not supplying an
> passwords
> just typing the netgear url,
> where is SM looking in order to get the correct authtication

You could always install wireshark
  https://www.wireshark.org/download.html
and see what's actually happening.

> I have cleared cache, removed the 192.168.x.x passwords
>
> not really sure if Seamonkey is at fault here,   comments appreciated !

I have a netgear at home also.  No problems getting in using seamonkey.

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

Re: router login - error 401, unauthorized

2017-10-07 Thread David E. Ross 
On 10/7/2017 9:34 AM, rjkrjk wrote:
> win7/64, SM 2.48
> 
> 
> attempted to log on to my router (Netgear AC1900/R7000) using the all of the 
> following
> standard netgear address
> 10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net
> 
> NONE workand I get an 401 Error,   unauthorized
> 
> however, when using FF 56, I have NO Problem accessing the router
> using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)
> 
> the 401 error message
> Access to this resource is denied, your client has not supplied the correct 
> authentication
> 
> does even have the netgear standard 2 line sign in box, I'm not supplying an 
> passwords
> just typing the netgear url,
> where is SM looking in order to get the correct authtication
> 
> I have cleared cache, removed the 192.168.x.x passwords
> 
> not really sure if Seamonkey is at fault here,   comments appreciated !

Last night, I could not login to my Netgear router (Netgear N300
Wireless Router Model WNR2000v5).  I terminated SeaMonkey and then
relaunched it.  Before trying again, I disabled my Secret Agent
extension.  I was then able to login without any problem.

HOWEVER, I just now tried it with Secret Agent enabled.  I was able to
login without any problem.  So I do not know what caused the failure
last night.




-- 
David E. Ross


By allowing employers to eliminate coverage for birth control
from their insurance plans, President Trump has guaranteed there
will be an increase in the demand for abortions.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: router login - error 401, unauthorized

2017-10-07 Thread rjkrjk 



Rick & Sharon wrote on 10/7/17 12:51 PM:

rjkrjk wrote:

win7/64, SM 2.48


attempted to log on to my router (Netgear AC1900/R7000) using the all of
the following
standard netgear address
10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

NONE workand I get an 401 Error,   unauthorized

however, when using FF 56, I have NO Problem accessing the router
using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

the 401 error message
Access to this resource is denied, your client has not supplied the
correct authentication

does even have the netgear standard 2 line sign in box, I'm not
supplying an passwords
just typing the netgear url,
where is SM looking in order to get the correct authtication

I have cleared cache, removed the 192.168.x.x passwords

not really sure if Seamonkey is at fault here,   comments appreciated !

---
This email has been checked for viruses by AVG.
http://www.avg.com


You're not alone, I started getting the same thing with my home router. Until I 
saw this, I
thought it was just my model of device.  If you clear ALL your cookies and ALL 
cache, it'll
work fine.  But only once: the next time you try you'll get the 401 error 
again, until you
clear ot all your old data.

I'd love to know what this answer is, as well.  Every time I have to clear 
everything out,
the wife has to log into her pages manually again.



just gonna use FF to access the router, dont think I wanna have to clear everything each 
time I wanna do something/upgrade/update the router.PITA

maybe someone else will have another answer,tks


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

Re: router login - error 401, unauthorized

2017-10-07 Thread Rick & Sharon 

rjkrjk wrote:

win7/64, SM 2.48


attempted to log on to my router (Netgear AC1900/R7000) using the all of
the following
standard netgear address
10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

NONE workand I get an 401 Error,   unauthorized

however, when using FF 56, I have NO Problem accessing the router
using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

the 401 error message
Access to this resource is denied, your client has not supplied the
correct authentication

does even have the netgear standard 2 line sign in box, I'm not
supplying an passwords
just typing the netgear url,
where is SM looking in order to get the correct authtication

I have cleared cache, removed the 192.168.x.x passwords

not really sure if Seamonkey is at fault here,   comments appreciated !

---
This email has been checked for viruses by AVG.
http://www.avg.com

You're not alone, I started getting the same thing with my home router. 
Until I saw this, I thought it was just my model of device.  If you 
clear ALL your cookies and ALL cache, it'll work fine.  But only once: 
the next time you try you'll get the 401 error again, until you clear ot 
all your old data.


I'd love to know what this answer is, as well.  Every time I have to 
clear everything out, the wife has to log into her pages manually again.

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

router login - error 401, unauthorized

2017-10-07 Thread rjkrjk 

win7/64, SM 2.48


attempted to log on to my router (Netgear AC1900/R7000) using the all of the 
following
standard netgear address
10.0.0.1, 192.168.0.1, 192.168.1.1, routerlogin.net

NONE workand I get an 401 Error,   unauthorized

however, when using FF 56, I have NO Problem accessing the router
using routerlogin.net or 10.0.0.1 ( the 192.168.x.x both time out)

the 401 error message
Access to this resource is denied, your client has not supplied the correct 
authentication

does even have the netgear standard 2 line sign in box, I'm not supplying an 
passwords
just typing the netgear url,
where is SM looking in order to get the correct authtication

I have cleared cache, removed the 192.168.x.x passwords

not really sure if Seamonkey is at fault here,   comments appreciated !

---
This email has been checked for viruses by AVG.
http://www.avg.com

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