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.
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.
I have two machines, one is Antergos (Arch/Linux) and the other one is Windows 10 connected to each other using LAN. The Antergos PC has a hostname of niffler and the Windows PC has a hostname of phoenix. The IP addresses to both the PCs are assigned by my router and they don't change too often. But still I want to use these PCs using their hostnames instead of their IPs. So I installed avahi and nss-mdns on niffler from the official Arch Wiki and also did everything they mentioned. To double check that I did everything correctly, I pinged niffler (ping niffler.local) using it's own terminal session and it resolved to it's correct IP. However when I use phoenix to ping to niffler, it doesn't work. When I run ping niffler.local from phoenix, it gives the error - Ping request could not find niffler.local. Please check the name and try again.
On my root server, debian 7 is the operation system. Running kernel is 2.6.32.
I have the problem, that TCP/IP-connections seems to be "unstable".
ssh connections often hang or timeout. Webserver sometimes runs fast, sometimes the client (browser) is waiting and waiting for a response.
I dont know where to start right now for this problems. I made a hardware check requests at my ISP ticket system.
Is there a hint you can give me?
I would guess it is DNS related. I would isolate one destination to communicate to, and one location to communicate from. Using ping, I would determine if there was latency in the link itself (ping from the server to one destination and from your client workstation to the troubled server). Once you determine that times are predictable (no **'s)I would learn both IP addresses and put them in /etc/hosts.
When you run ssh I would consider using -vv to see what it is doing and maybe that will help.
The problem was a broken network adapter in the mainframe of the cluster. The provided fixed the issue.
Searched all over the place for a fix for this or even a good way to troubleshoot it. I've read the previous SO threads that seem to cover this issue but nothing in any of them has worked in my case.
Basically, I can't get access to anything that is being served via localhost on my mac in any browser on my Android device.
This is happening despite the fact they are connected to the same WIFI network and I am using the correct network address for my mac on which localhost is running (I have checked and double checked several times). I have no idea what the problem is because it worked perfectly fine before and I haven't changed anything that I believe would interfere with localhost access.
I don't have firewall or port blocking settings on my router either.
I have also tried on several different Android devices to eliminate it being a problem specific to one particular device.
Totally stumped. Any clues or hints on how to fix this would be much appreciated!
***** UPDATE *****
I tried using python -m SimpleHTTPServer 3000and it works. The site is accessible on my Android device. So I am pretty sure it is not a network issue per se.
The site is essentially a Node app which I built using the angular-quickstart template found here. It launches lite-server when npm start is run. Hope that gives some further insight into what the problem might be.
If you open up a terminal on your mac and then run the command ifconfig it will tell you what ip address all your interfaces have. It is probably your en0 interface. That ip address should be used in your browser on your Android device.
You will have to make user that you server (web) is binding to the correct ip address as well. You could be binding to all ip addresses if possible.
So I am a bit puzzled by this. All of this is in a larger corporate network, but all machines are basically on site.
We have one machine (linux) sending SOAP requests to the other machine (windows) and since a few days these requests fail after a certain time. We haven't found any pattern as to which requests fail (doesn't seem to be a particular request).
We tried a traceroute from the requesting machine to the target machine and the target machine doesn't acknowledge the packet (asterisks at the target). A running ping did work and did not drop any packets.
The target machine is a VM on a host hosting many machines.
The problem started after a scheduled restart a few days ago.
Our team is actually only responsible for the application on the target server, but we are invested in helping pinpoint the problem.
Apart from running wireshark on the target server and looking for the traceroute or soap packets, is there any other point of failure where we can investigate?
If you are using domain names (not IP), check that they are resolved properly. ISP dropping the packets would not be an issue since everything is on site.
Ping works, so I assume both machines see each other on the network. But is it should be the sending machine (linux) to send the Ping to be sure that the machine isn't blocked somewhere in the network.
Ping works, but traceroute doesn't, check for possible Firewall issues. Check if its the request not getting to the Windows machine or the reply isn't getting out.