Linksys WRTG54S: can't access 192.168.1.1
Closed
zeroth
Posts
1
Registration date
Saturday August 10, 2013
Status
Member
Last seen
August 10, 2013
-
Aug 10, 2013 at 07:41 PM
MothyOz Posts 2 Registration date Thursday March 20, 2014 Status Member Last seen February 15, 2015 - Feb 15, 2015 at 02:11 AM
MothyOz Posts 2 Registration date Thursday March 20, 2014 Status Member Last seen February 15, 2015 - Feb 15, 2015 at 02:11 AM
Related:
- "192.168.l.0"
- Linksys velop password not working - Guide
- Linksys srw2008 ✓ - Linksys Forum
- Linksys wrt54g reset ✓ - Linksys Forum
- Linksys wrt54g2 v1 specs ✓ - Network Forum
- Linksys forum - Linksys Forum
3 responses
MothyOz
Posts
2
Registration date
Thursday March 20, 2014
Status
Member
Last seen
February 15, 2015
Mar 20, 2014 at 03:11 AM
Mar 20, 2014 at 03:11 AM
Hi zeroth. I searched for help on this problem & the solutions I found did not help me either - you have covered the range of likely problems you know don't exist. I hope this helps you or others searching for an answer not yet 'out there'!
I experienced the same problem with Windows 7 & Explorer 64bit versions opening the Windows Security log in window briefly "this page is requesting username..." then "Windows Explorer has experienced a problem / shutting down" when trying to access (http:)//192.168.1.1 over Ethernet to the router. I can't remember if it began when I started to use W7, I don't often need to access the router.
After a similar initial `panic' I tried access using the 32bit Explorer (accessed under C: program files X86, Internet /Explorer), which (relief) has worked fine for 5 years! I have since tried Google Chrome which was also successful. First solution found.
I have since found a better solution that allowed me to use the 64bit browser to login / access the router. I used the 32bit browser (I was not concerned with router, firewall, antivirus etc as a cause when 32bit success pointed to browser issues) until a recent upgrade to Explorer 11 when I decided to explore possible browser security issues in WEx 11 as a reason for the router login crash.
My solution was to add the address http://198.192.1.1 to the Local Intranet Security Zone under WEx 11 browser (settings cog) Internet Options, Security tab, Local Intranet zone, Advanced button. No need to add it as a Trusted Site or add to Allow in Privacy Sites (cookies). The Login Pop-up window must trigger an intrusion attempt?
Note that "Enable Protected Mode" is checked for the Internet Zone, but not the Local intranet; perhaps this may also cause issues if checked for Local intranet?
https://docs.microsoft.com/en-us/archive/blogs/
I experienced the same problem with Windows 7 & Explorer 64bit versions opening the Windows Security log in window briefly "this page is requesting username..." then "Windows Explorer has experienced a problem / shutting down" when trying to access (http:)//192.168.1.1 over Ethernet to the router. I can't remember if it began when I started to use W7, I don't often need to access the router.
After a similar initial `panic' I tried access using the 32bit Explorer (accessed under C: program files X86, Internet /Explorer), which (relief) has worked fine for 5 years! I have since tried Google Chrome which was also successful. First solution found.
I have since found a better solution that allowed me to use the 64bit browser to login / access the router. I used the 32bit browser (I was not concerned with router, firewall, antivirus etc as a cause when 32bit success pointed to browser issues) until a recent upgrade to Explorer 11 when I decided to explore possible browser security issues in WEx 11 as a reason for the router login crash.
My solution was to add the address http://198.192.1.1 to the Local Intranet Security Zone under WEx 11 browser (settings cog) Internet Options, Security tab, Local Intranet zone, Advanced button. No need to add it as a Trusted Site or add to Allow in Privacy Sites (cookies). The Login Pop-up window must trigger an intrusion attempt?
Note that "Enable Protected Mode" is checked for the Internet Zone, but not the Local intranet; perhaps this may also cause issues if checked for Local intranet?
https://docs.microsoft.com/en-us/archive/blogs/
johnicook
Posts
6
Registration date
Friday May 23, 2014
Status
Member
Last seen
June 3, 2014
May 28, 2014 at 01:27 AM
May 28, 2014 at 01:27 AM
you can see the discussions for help- https://ccm.net/computing/networks/1905-how-to-fix-a-wireless-router-that-can-t-connect/
MothyOz
Posts
2
Registration date
Thursday March 20, 2014
Status
Member
Last seen
February 15, 2015
Feb 15, 2015 at 02:11 AM
Feb 15, 2015 at 02:11 AM
There is an error in my answer above as to address added to Security / Local Intranet / Advanced, it should read the factory default address of the router e.g. http://192.168.1.1.
My failure to login to the router was directly related to the purchase of a Windows 7 PC and my solution points to the way that the 64bit Windows Explorer browser handles security with LAN access to the router (Ethernet cable). This solution is unlikely to apply to earlier 32bit Windows versions nor other browsers - I could still access the router using Chrome or the 32bit WE.
My failure to login to the router was directly related to the purchase of a Windows 7 PC and my solution points to the way that the 64bit Windows Explorer browser handles security with LAN access to the router (Ethernet cable). This solution is unlikely to apply to earlier 32bit Windows versions nor other browsers - I could still access the router using Chrome or the 32bit WE.
