[SOLVED] Wireless has bad connection from RT-N66R Gigabit Router
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Wireless has bad connection from RT-N66R Gigabit Router
I bought an Asus Wireless Router RT-N66R yesterday, and it has successfully hooked up to everything around my home, except for my personal laptop. I run 14.04 Trusty Tsar on it. The wireless works for about 30 seconds before the computer stops recognizing it, and then I have to reconnect it again by clicking on the network name. Everything else in the house works great with it, and for the 30 or so seconds it stays connected to my laptop, my laptop works great as well. Also, when I am connected to Facebook, it tends to let me continue IMing people, even if I have no connection anywhere else. I can usually google my way to an answer, but I am really stumped on this one, please help!
Might try a b/g protection setting in router. Think it has it. Try it first. Since you say the router first I'd look there.
There still remains a number of issues that could cause it. Various logs in linux and router may offer clues.
If playing with router and looking at logs offer no clues then might have to look at hardware on laptop. Did it ever work correctly? Band and channel issues? Driver issues? Try a few live cd's maybe to compare.
Apr 1 01:38:34 nmbd: process_local_master_announce: Server VERCINGETORIX at IP 192.168.1.50 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Apr 1 01:38:34 nmbd: [2015/04/01 01:38:34, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(149)
Apr 1 01:38:34 nmbd: Samba name server RT-N66R-B418 has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.1.1
Apr 1 01:38:52 nmbd: [2015/04/01 01:38:52, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Apr 1 01:38:52 nmbd: Samba name server RT-N66R-B418 is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1
You've posted log files, but you haven't provided any supporting information. Eg: when is communication established, when does communication stop, when do DNS lookups fail, etc. The timestamps in the log file are only useful when you provide times when you're experiencing connection success/failure.
As for DNS checks, use ping, it's pretty simple. DNS is what maps website names to IP addresses. When you type in "www.google.com", DNS is what tells your computer that you really mean 220.127.116.11 (or whatever the case may be in your location). If your DNS is functioning normally, you can run "ping www.google.com" and you'll see output like this:
$ ping www.google.com
PING www.google.com (18.104.22.168) 56(84) bytes of data.
64 bytes from iad23s43-in-f4.1e100.net (22.214.171.124): icmp_seq=1 ttl=56 time=68.5 ms
64 bytes from iad23s43-in-f4.1e100.net (126.96.36.199): icmp_seq=2 ttl=56 time=71.3 ms
64 bytes from iad23s43-in-f4.1e100.net (188.8.131.52): icmp_seq=3 ttl=56 time=65.4 ms
If your DNS is not functioning normally, you'll see errors saying it couldn't resolve "www.google.com", but pinging the IP itself will work:
$ ping 184.108.40.206
PING 220.127.116.11 (18.104.22.168) 56(84) bytes of data.
64 bytes from 22.214.171.124: icmp_seq=1 ttl=56 time=68.5 ms
64 bytes from 126.96.36.199: icmp_seq=2 ttl=56 time=71.3 ms
64 bytes from 188.8.131.52: icmp_seq=3 ttl=56 time=65.4 ms
Server VERCINGETORIX at IP 192.168.1.50 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
This is a windows networking (samba) message. Has nothing to do with your wireless connection. You can turn off samba to verify.
A quick search indicates a driver bug. Was wireless working before you changed routers?. Have you made any other changes to your PC? Might try changing your wireless parameters on the router like lowering the speed.
The old fix was to use the vendor driver but that is only valid up to 3.2.x kernels. Have not found another fix.