Mark,
I have the Win 8.1 machine switched on and am using the ethernet cable connected to the router. I have logged on here to write this and was wondering if I should leave this machine logged on until something happens ?
I will start up the Linux machine on the WiFi downstairs and work on that today while I can if that is ok. ?
Yeah, we need em both switched on.
Doesn’t really matter which you’re working on when it fails as long as you then run the pings on both machines (without having to start them).
so copy the output to text files on both PC’s before doing whatever you need to re-establish a connection and post the results back here.
I’m just rying to see if BOTH pc’s are kicked off the network at the same time, and whether they are both able (or not) to ping the router and the internet … but I don’t want you to need to START up one of the PC’s because that may re-establish a connection and skew the results.
Hi Mark,
I lost the connection today again but only have the Linux computer to hand.
There has been no internet connection between 3 o’clock and 5.30 this evening.
I pinged from downstairs and got this
don@ldwatson ~ $ ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.42 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.43 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.41 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.43 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.45 ms
— 192.168.1.1 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.410/1.428/1.453/0.049 ms
don@ldwatson ~ $ ping -c 5 google.com
ping: unknown host google.com
don@ldwatson ~ $
I then went upstairs and connected the cable between router and computer, it said there was a connection but I pinged again and got this
don@ldwatson ~ $ ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.367 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.336 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.290 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.337 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.252 ms
— 192.168.1.1 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
rtt min/avg/max/mdev = 0.252/0.316/0.367/0.043 ms
don@ldwatson ~ $ ping -c 5 google.com
ping: unknown host google.com
don@ldwatson ~ $
That means the connection to your router was working, but we don’t know about the outside world. Next time, please also ping 8.8.8.8 (Google’s DNS server)
Hi Mark,
The computer went offline tonight again but I didn’t have the Win 7 machine running.
By the time I got upstairs and switched it on the internet was back. Actually by the time I switched it on and waited on the blxxdy thing UPDATING the connection was restored.
However the Linux machine went down and is still disconnected. I have pinged and this is the result
Ooooooops wrong machine
right machine here is the result
don@ldwatson ~ $ ping -c 5 192.168.1.1
connect: Network is unreachable
don@ldwatson ~ $ ping -c 5 google.com
ping: unknown host google.com
don@ldwatson ~ $ ping 8.8.8.8
connect: Network is unreachable
don@ldwatson ~ $
Hope this helps
Am I right in thinking you’re back to using the rtl8723be based wireless adapter ?
what’s the output from:
sudo lshw -C network
and
cat /etc/modprobe.d/rtl8723be.conf
[quote author=Mark Greaves (PCNetSpec) link=topic=12507.msg102463#msg102463 date=1439501271]
Am I right in thinking you’re back to using the rtl8723be based wireless adapter ?
Eh ???
I am using the Virgin Media superhub as a router and the TP-LINK WiFi router as the wifi.
I have the result of the 2 commands here
don@ldwatson ~ $ sudo lshw -C network
[sudo] password for don:
*-network
description: Wireless interface
product: RTL8723AE PCIe Wireless Network Adapter
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlan0
version: 00
serial: a4:db:30:c7:44:e8
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=rtl8723ae driverversion=3.16.0-45-generic firmware=N/A ip=192.168.1.103 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn
resources: irq:18 ioport:e000(size=256) memory:f7d00000-f7d03fff
*-network
description: Ethernet interface
product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0.2
bus info: pci@0000:03:00.2
logical name: eth0
version: 06
serial: 00:90:f5:f3:67:bf
size: 10Mbit/s
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8402-1_0.0.1 10/26/11 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
resources: irq:41 ioport:d000(size=256) memory:f0004000-f0004fff memory:f0000000-f0003fff
don@ldwatson ~ $ cat /etc/modprobe.d/rtl8723be.conf
cat: /etc/modprobe.d/rtl8723be.conf: No such file or directory
don@ldwatson ~ $
Hope this helps
So your machine lost connection to the router - sounds like the Windows PC did at the same time, but it managed to recover (following a reboot).
It would be interesting to get the result of the following command following a failure:
sudo rfkill
Also, a potential (temporary) fix might be:
sudo modprobe -r rtl8723ae && sudo modprobe rtl8723ae
This should “cycle” the wireless driver, and should allow network manager to have another go at establishing a connection to the router.
Edit: Found this link - the first method might be useful for future reference/diagnosis - [ubuntu] ASUS laptop wireless
What’s the output from:
cat /etc/modprobe.d/rtl8723ae.conf
Hi Mark,
This is the result
don@ldwatson ~ $ cat /etc/modprobe.d/rtl8723ae.conf
cat: /etc/modprobe.d/rtl8723ae.conf: No such file or directory
don@ldwatson ~ $
Sorry chemicalfan,
I will stick with Marks advice at the moment. I don’t want to throw too many equations in the pot. 
I would like to get back to my original setup just using the Virgin Media Superhub 2 as the desk is very cluttered with cables at the moment 
OK, try running:
echo "options rtl8723ae fwlps=0" | sudo tee /etc/modprobe.d/rtl8723ae.conf
then unload/reload the driver with:
sudo modprobe -r rtl8723ae
then:
sudo modprobe rtl8723ae
that’ll disable firmware link power saving for the wireless adapter.
This made a HUGE difference to my rtl8723be wireless adapter … hopefully it’ll also work for the rtl8723ae too.
Obviously this won’t stop the dropouts between the superhub and the internet … but hopefully it’ll allow Linux to reconnect like Windows did.
Hi Mark,
Carried out those instructions but they have disconnected me from the network.
I am using the Win computer to write this.
the first modprobe command WILL disconnect you … the second one should reconnect you
if it didn’t try rebooting
if you’re still unable to connect, run:
sudo rm -v /etc/modprobe.d/rtl8723ae.conf
then reboot.
Hi Mark,
The reboot worked ok ;D
What now ?
Nothing … as long as you didn’t delete the rtl8723ae.conf file you just need to wait and see if Linux reconnects the same as Windows next time the router kicks you off for a bit.
Ok. Thanks again.
I was playing a game on the internet this evening and the message came up ’ you have lost connection to the server’
I pinged the numbers with this result
don@ldwatson ~ $ ping -c 5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.56 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.42 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.36 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.49 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.46 ms
— 192.168.1.1 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.367/1.463/1.561/0.076 ms
don@ldwatson ~ $ ping -c 5 google.com
PING google.com (216.58.210.46) 56(84) bytes of data.
64 bytes from lhr14s23-in-f46.1e100.net (216.58.210.46): icmp_seq=1 ttl=55 time=22.5 ms
64 bytes from lhr14s23-in-f46.1e100.net (216.58.210.46): icmp_seq=2 ttl=55 time=25.5 ms
64 bytes from lhr14s23-in-f46.1e100.net (216.58.210.46): icmp_seq=3 ttl=55 time=22.4 ms
64 bytes from lhr14s23-in-f46.1e100.net (216.58.210.46): icmp_seq=4 ttl=55 time=22.3 ms
64 bytes from lhr14s23-in-f46.1e100.net (216.58.210.46): icmp_seq=5 ttl=55 time=22.7 ms
— google.com ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 22.394/23.150/25.565/1.219 ms
don@ldwatson ~ $
Is this ok ?
it’s perfectly OK … in fact it says there’s no connection problem, so I’m confused ???
Mark,
Could this be a problem with the game server. I play the games at ‘Royal Games’ and this is when the error pops up, but only when I play backgammon. I play other games on that site but it only throws up the error in backgammon.
This is where the original error started when I asked about dropped connections, maybe VM Superhub is ok