[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: difficult to isolate problem - browser access to router has problems on on machine but not other



On 4/14/2012 11:00 PM, Arthur Marsh wrote:
> Hi, I've tried to run through all I can think of and am getting a bit
> stuck.
> 
> I have two machines running Debian (one a dual-core Pentium4 with i386,
> the other a quad-core AMD64-X2 with amd64), both with built-in ethernet
> cards.
> 
> The Pentium4 machine can access the browser interface of the adsl router
> I use with no problems.
> 
> The AMD64 machine has recently taken to stalling after entering the
> username and password for the adsl router's browser interface, and I've
> tried downgrading recent package upgrades, and different kernels and
> browsers without success.
> 
> However, the AMD64 machine booted with the sysrescuecd can access the
> browser interface of the adsl router without problems.
> 
> The AMD64 machine has a built-in Realtek 8169 NIC.
> 
> debsums has so far been inconclusive at pointing to any corrupted files.
> 
> I've also swapped ports that the pc's use on the router without any
> noticeable change, and have powered-down both the pc and router
> completely to eliminate issues caused by power glitches.
> 
> Are there any browsers on Debian that support javascript without having
> to run under the X window system?
> 
> Any other suggestions welcome.

Read the docs and everything you find online for that make/model of ADSL
router.  What you're looking for specifically is whether it is designed
to use an "admin PC".  Some of these consumer routers force you to enter
an IP address of only one machine that can log into the admin interface.
 Others simply store a cookie on the first machine you log in with then
deny access from any machine without that cookie.  There are probably
other variations on this theme as well.

Given what you describe, I'd be 99% sure something like this is what
you're up against.  Clear the cookies cache on both machines, then try
the "problem machine" first.  In addition to reading all docs you can find.

-- 
Stan


Reply to: