On Mon, 2013-08-26 at 16:09 +0300, Alexander Kapshuk wrote: > Problem is, I can't seem to log onto the router's amin console at > 192.168.1.1 from my desktop. I did manage to log onto it from my > laptop wirelessly. The DHCP server was reported as running. All the > other settings seemed OK as well. >
You should probably re-read Zenaan's mail. It offered the most sensible test until now and you didn't even care. nm is know to offer headaches from time to time so you should first single out if it's not nm related. > > On Aug 26, 2013 3:55 PM, "Zenaan Harkness" <z...@freedbms.net> wrote: > On 8/26/13, Alexander Kapshuk <alexander.kaps...@gmail.com> > wrote: > > My desktop uses wired networking. While my laptop is capable > of utilizing > > both wired and wireless interfaces. My modem is a TP-LINK > ADSL + wireless > > router. > > Wired networking stopped working on both the desktop and > laptop, while the > > wireless networking continues to work on my laptop. > > Tried using a different cable. Still no luck. > > Is there a way to check if there's anything amiss with my > modem? > > read the manual, or duckduckgo the manual if you don't have > it, and > log in and check it out > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > > http://lists.debian.org/caosgnsrjg2nsq2_aiwvcqusvwo4uzuq17ibtgvsp_ym5dzv...@mail.gmail.com > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1377535659.16085.27.camel@tagesuhu-pc