I upgraded to ubuntu 18.04 about a month ago on my MSI 7REX Leopard Pro. Although the system works fine with the usual performance, somehow the internet is always slow to connect for the first time AND when I reopen the browser tabs after waking it up from the suspend mode. I need to wait at least 2-3 mins before the webpage starts to load.
I've tried to change the "nameserver" settings in the \etc\resolv.conf from the default like this:
#nameserver 127.0.0.53
nameserver 8.8.8.8
nameserver 8.8.4.4
search home
the added commands are on line2 and line3 (the rest were default). But it didn't change anything so I reverted back.
This problem is not browser specific (I use firefox and chrome). I've tried to use Cinnamon but that too didn't solve the issue. Any solution?
Related
I just tried to connect to internet using my home WiFi network and didn't manage. I use Ubuntu 18.04.
I am able to connect using hotspot or any other network, but not this one from home. Also it works fine with Windows. I tried with the Ethernet cable as well and didn't work.
I mention I have Atheros QCA9565 .
I tried:
ping 8.8.8.8 and this was successful.
Then:
ping google.com and got this error message: name or service unknown.
Therefore I added:
nameserver 8.8.8.8 in /etc/resolv.conf file and made this persistent after noticing it is reinitialised at reboot: https://www.tecmint.com/set-permanent-dns-nameservers-in-ubuntu-debian/
Sometimes I can do ping google.com but the time is badly increasing, so it's super slow.
And when I can't connect at all, ping google.com has the same error message.
I mention that I tried to turn off DNS automatic from IPv4 tab from WiFi network settings and the connection persisted for 10 seconds or so: https://www.configserverfirewall.com/ubuntu-linux/ubuntu-set-dns-server/
Might it be a hardware problem or what should I try next?
Although it may not be the issue, I recently had problems with the built-in Wifi on my computer's motherboard. I could access some sites at a good speed while others were unreachable. I tried several things I found online but nothing helped. I spent 30 USD on Amazon for a generic AC1200 PCIe Adapter and all the problems/issues have been resolved. Apparently, something was off with the card that was originally part of the computer.
I was told this should not have made some websites not load but the new card has none of the issues at all.
My setup is that I have a machine running little eclipse server in node, and I want to configure other machines on the LAN to run a website off of that first computer. Everything is working fine, but I have to manually tell the other computers which local IP address to use when opening chrome.
All computers at this point are running ubuntu.
Ideally I'd like to make a bash script on any new computer which finds the IP address of the computer running the express server, then opens chrome at that address.
Googling tends to get me answers for the question 'how to see all computers on my LAN'. It seems that I can achieve that in many ways, most notably nmap.
NMap works fine, but now my question is how I can make the server computer broadcast its status as the desired machine, then extract its sepcific IP address?
Some of the other possibilities I've considered are the following (I state why I'm not sure they're right for me, but please correct me if I'm wrong):
Hosts File
This requires setup for each collection of computers, which is undesirable
DHCP+DNS on router
Again requires set up on the router, which can't be guaranteed to have the required functionality every time.
DNS server on a machine
Again this requires knowing the IP address of the server
What I'd really like is for the process to be automatic – the server machine is happily running its local website, then any other computer that joins the network is able to find it then open that website in chrome, without the person installing the computer having to know the server's IP address. Is such a thing feasible?
I'm attempting to redirect an existing web address to a remote machine on my subnet. To do that, I put the following into /etc/hosts
192.168.1.249 holub.com
and flush the DNS cache with
sudo dscacheutil -flushcache;sudo killall -HUP mDNSResponder
However, when I ping holub.com (the most reliable way that I know to see how the address is actually resolved), I see the real web address (204.13.10.74), not the one specified in /etc/hosts (192.168.1.249). Interestingly, the mysqladmin utility does not resolve the address correctly, but the Chrome browser does resolve the address correctly. I'm guessing that Chrome has some sort of internal workaround.
In general, it looks like /etc/hosts is being used after the actual DNS lookup, not before as it should be, so an external address is not overridable.
I've tried using various IPv6 equivalents to my local address (0:0:0:0:0:ffff:c0a8:01f9 ::ffff:192.168.1.249 ::192.168.1.249), but that doesn't help. Rebooting (instead of flushing the cache) doesn't help either.
I have found one unsatisfactory workaround. If I disable the DNS reponder with
sudo launchctl unload -w
/System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
then /etc/hosts is used, but then I can't access the internet.
If anybody's encountered this problem, I'd love to know if there's a workaround.
I came across this while searching for an answer to a similar problem and wanted to post my findings for anyone else in the same position.
As a team of three, we found that edits to my /etc/hosts file appeared to work, while editing the other two's host files seemingly did not. Upon further digging, we realized I was on OS X 10.10, while they were on newer versions.
We found, after trying about a million things, that additions to the hosts file in 10.11 and up apparently could not have more than one space between the IP and the domain, for example:
DID NOT WORK:
1.2.3.4 some.site.com
DID WORK:
1.2.3.4 some.site.com
After making this change, we immediately started seeing expected results without any cache clears, reboots, or otherwise.
I know in your example you are only showing one space, but in the off chance that's now how it appeared in your actual file I wanted to share this anyway.
I have set up tigervnc-server on my CentOS 6 machine following this guide. At first everything worked fine, I could connect to the server using TightVNC Viewer on my Windows machine. I left the session running in the background for a while. The server closed the inactive connection, which it also does for ssh or any other connections, so that's still normal. So I reconnected and everything was fine.
Then I decided to add a different user to the VNC users, as I was running my first connections from root. That's where it all broke. I couldn't connect to he server anymore, it always told me that the remote computer denied the connection. I made sure the server ports were open in iptables, tried to reinstall tigervnc-server, changing the config back to how it was before it broke and disabling the Windows Firewall. After reinstalling it, I was able to launch it without setting a vnc password, so it either saved it somehow from before or something broke entirely. None of my attempted fixes worked.
Turned out to be me not working on linux for over a year and I finally figured out I had to start the vnc server from the user I wanted it to run on.
I have installed andlinux Beta 2 on my WinXP. Everything works fine until last night, I don't recall that I ever changed anything on network configuration or andlinux setup, the network stop working inside andlinux. With that said, I mean open a KDE console, I do "ping yahoo.com", I see DNS is resolved correctly, however, no response at all.
My andlinux is startup as a WinXP service. Open windows task manager I can see following services are up and running:colinux-daemon.exe colinux-net-daemon.exe colinux-slirp-net-daemon.exe
On andlinux side, there are two network interface eth0 and eth1. eth1 is configured to communicate with local WinXP. I configured it to use samba to access windows directories, no problem. From WinXP side, I can use ssh to login into andlinux box via eth1 IP address.
eth0 is configured as slirp, no port forwarding. eth0 has IP=10.0.2.15, default gateway is 10.0.2.2, netmask=255.255.255.0; These are configured in /etc/network/interfaces. DNS is 10.0.2.3, which as I just mentioned resolve yahoo.com correctly.
On the windows side, internet works fine. I disabled firewall on all network interface. I rebooted my laptop, no luck. I searched over inet, seem no one has this problem. People say network is done if they kill the colinux-slirp-net-daemon. What frustrated me is that this whole thing worked well, but for no reason it's broken all the sudden. Anyone has experience on this issue, please help, appreciate!
I thought I had the same problem, but then found my andLinux system's network connectivity was actually working fine, and that several things made it difficult to tell what was going on.
Test I did to validate connectivity: wget www.yahoo.com
Behavior I observed that made troubleshooting difficult:
Pings from andLinux - not all hosts will respond to pings from the andLinux OS (ie Ubuntu, not the Host Windows OS). According to my packet captures the pings appear as UDP pings instead of ICMP pings once they leave the host OS's adapter. The major IPs/hosts (like yahoo, google, 4.2.2.2 etc.) on the internet I usually ping to test connectivity currently don't respond to these type of pings.
Traceroutes from andLinux - even when successful, these never show more than 2 hops when done from the andLinux OS. If successful, both hops show 10.0.2.2. If unsuccessful, the second hop just times out. Not sure why, I'm sure there is an explanation.
Packet captures - at the host OS level, the capture (eg wireshark) must be done on the physical interface the traffic is going over. I was initially capturing on the TAP-Win32 Adapter but this only showed X Window traffic.
Installed apt sources URLs no longer valid - Ubuntu 9.04 is long out of support by now, so the URLs in the apt sources.list file didn't exist anymore. This is what got me thrown off in the first place, because I didn't troubleshoot this specifically and just tried to test my internet connectivity first, then got confused by the ping and traceroute behavior seen above. Changed http://us.archive.ubuntu.com/ubuntu to http://old-releases.ubuntu.com/ubuntu/ in sources.list and was good to go.