Ethernet connected but no internet

[kiwipeso1]

I have two Macs connected to the same router via ethernet cables.

One connects to the internet fine (via Safari), the other won't connect.

These are my settings per System Preferences -> Network:

Working Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.61.2
Configure IPv4: Using DHCP
IP address 192.168.61.2
Subnet Mask: 255.255.255.0
Router: 192.168.61.1
DNS Server: 192.168.1.254

Failing Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.1.146
Configure IPv4: Using DHCP
IP address 192.168.1.146
Subnet Mask: 255.255.255.0
Router: 192.168.1.254
DNS Server: 192.168.1.254

I wondered which addresses should be the same on both machines?
I noticed that the router address is different, should this be the same on both machines?

Any other suggestions to determine the problem would be much appreciated.

Router has to be the same, you need to set the router to 192.168.1.1 on the failing mac.
[doublepost=1455393687][/doublepost]

Do you understand the for those two machine to "talk" to each other the must be in THE SAME first three sets of numbers (subnet) in each Computer station! Your switch has been VLANed into two subnetworks. That second IP( subnet it us in) has no connection to the Internet modem!

No, actually all subnets are 255.255.255.0 for local networks.
The real problem is with the router number not being 192.168.1.1
Please learn basic IP addressing before offering mere opinion satcomer.

 

[satcomer]

Router has to be the same, you need to set the router to 192.168.1.1 on the failing mac.
[doublepost=1455393687][/doublepost]

No, actually all subnets are 255.255.255.0 for local networks.
The real problem is with the router number not being 192.168.1.1
Please learn basic IP addressing before offering mere opinion satcomer.

That is a system for determining the number of devices that need an IP! You don't seem to understand simple networking!

 

[JohnDS]

@kiwipeso: The issue of the two different router IP addresses has already been dealt with much earlier in this thread.

 

[Mr. Buzzcut]

We need to hear from the OP. This is just shooting in the dark and adding to his/her frustration.

It's true that there may be two DHCP servers but we have to know which device has the Internet connection to know which one to turn off.

So we need the topology (what connects to what) to get this going in the right direction. The OP can't even ping the gateway so something is wrong that we haven't quite figured out. Knowing the topology, interfaces, and routes will help a lot.

 

[kiwipeso1]

That is a system for determining the number of devices that need an IP! You don't seem to understand simple networking!

I understand networking, and have done so since doing the network assurance on the first internet video concert in 1993, ensuring a direct connection to Antartica was maintained from a Quadra 840av.
As a basic level of advice is assumed to be more helpful than a full description in technical detail that most lecturers don't understand, that is the level of advice I offer.
[doublepost=1455401407][/doublepost]

@kiwipeso: The issue of the two different router IP addresses has already been dealt with much earlier in this thread.

Yes, and unless there is a bridge between the two routers, then

We need to hear from the OP. This is just shooting in the dark and adding to his/her frustration.

It's true that there may be two DHCP servers but we have to know which device has the Internet connection to know which one to turn off.

So we need the topology (what connects to what) to get this going in the right direction. The OP can't even ping the gateway so something is wrong that we haven't quite figured out. Knowing the topology, interfaces, and routes will help a lot.

Suggested network topology is that the router and dns should always be x.x.x.1 , so that the network populates above ranging from x.x.x.2 to x.x.x.254

 

[RandomKamikaze]

I understand networking, and have done so since doing the network assurance on the first internet video concert in 1993, ensuring a direct connection to Antartica was maintained from a Quadra 840av.
As a basic level of advice is assumed to be more helpful than a full description in technical detail that most lecturers don't understand, that is the level of advice I offer.
[doublepost=1455401407][/doublepost]
Yes, and unless there is a bridge between the two routers, then


Suggested network topology is that the router and dns should always be x.x.x.1 , so that the network populates above ranging from x.x.x.2 to x.x.x.254

Is that also the last time you dealt with networking?! Everything you wrote in both your posts is so completely and utterly wrong I don't even know where to start

 

[Mr. Buzzcut]

I understand networking, and have done so since doing the network assurance on the first internet video concert in 1993, ensuring a direct connection to Antartica was maintained from a Quadra 840av.
As a basic level of advice is assumed to be more helpful than a full description in technical detail that most lecturers don't understand, that is the level of advice I offer.
[doublepost=1455401407][/doublepost]
Yes, and unless there is a bridge between the two routers, then


Suggested network topology is that the router and dns should always be x.x.x.1 , so that the network populates above ranging from x.x.x.2 to x.x.x.254

It doesn't make a bit of difference what the IPs are. The DHCP scope will avoid assigning the infrastructure IPs and DHCP will hand out the gateway and DNS IPs.

 

[kiwipeso1]

The point is to make a bridge between the directly connected (working router) to the other router as in :
192.168.a.1 to 192.168.b.1 .
This then allows for the secondary network, not to run on the same network spaces.
The specifics of how to do this should be listed on the manufacturers website of at least one of the routers, or even on the admin page in your router if it is new enough.

As before, the router and dns IP should be the same 192.168.x.1 , with DHCP starting from 192.168.x.2 ~ 192.168.x.254

Gateway should be almost the same as the WAN IP (assuming it's a fixed IP), except it should have x.x.x.1 at the end instead of your x.x.x.x IP address. (This is only entered on the direct router, the bridging router uses a fixed DHCP number on your direct router's network eg: 192.168.a.2 is reserved on your direct router for your other router, which bridges across to your other router.)

This should be reasonably straightforward, but my advice is to check both your routers manuals first if you are unclear on how to bridge between them.

 

[martin2a]

I wonder if that "VOIP box" (whatever that's supposed to be) is throwing a wrench into the works?

A couple of scenarios I would try:

1. Disconnect the VOIP box temporarily.
2. Plug both Macs into the router.
3. Power EVERYTHING off for 30 seconds, then reboot
How are the Macs now?

If both are ok, I might consider doing this:

Since the "working Mac" was connected to the VOIP box, I would do this:
1. Put an ethernet switch "after" the VOIP box
2. Connect both Macs to the switch
3. Power EVERYTHING off for 30 seconds, then reboot.
How are the Macs now?

I disconnected the VOIP box and re-booted everything, still no connection.

For the purposes of resolving my problem, I will keep it disconnected whilst this thread is active, I hope this eliminates a number of the discussion points above.

[doublepost=1455459662][/doublepost]

1. Which MAC was plugged into the VOIP box? The IP of the working one changed according to the last post.
2. Can the non-working MAC ping google.com (open terminal window and type "ping google.com") Reply with the output.
3. Do you have access to the router's LAN settings to see what IP addressing is configured?
4. What is / where is the Internet connection?

3) I managed to open the router settings on the working MAC in a browser on the url bthomehub.home/index.htm, I can also access this url from a Windows PC on the same network but not from the failing MAC, it just hangs. In the home page of the BT Home Hub menu I can see the IP addresses of all 3 machines. The IP Address for the failing MAC is the same as the one it shows in System Preferences on that machine.
[doublepost=1455460250][/doublepost]

I think you may be right, Fishrrman. I suggested unplugging the VOIP box a couple of posts ago.

I have a voip box myself and my recollection is that there are two ways to install it, either before or after the router. My recollection is also that the default setting are for the installation before the router and with those settings the VOIP box acts as a router and provides DHCP. It sounds as if those are the setting the OP is using, even though is VOIP box is connected after the router.

To connect the VOIP box after the router, you have to get into the settings and turn off its DHCP server or you will have two DHCP servers on the same network, which is a recipe for chaos.

Martin, can you tell us what VOIP service you are using and which VOIP box?

It is a Netgear VOIP box that connects to Sipgate. It gets its ethernet connection from the BT Router so I think it comes after the router. Either way I have disconnected it for now.
[doublepost=1455460689][/doublepost]

On the non-working Mac in the network prefs under TCP, click on Renew DCHP lease and see if you get an different IP address.

Also, under the Proxies tab, make sure NOTHING is checked.
[doublepost=1455306039][/doublepost]Also, as an experiment, disconnect the VOIP box, reboot the router and reboot both Macs and see what happens.

Renew DCHP lease does not generate a new IP Address.

Nothing checked under the Proxies tab select a protocol, just *.local, 169.254/16 in the Bypass section, use Passive FTP Mode is checked.

 

[martin2a]

If that is really your router and you can't ping it then we found much of your problem.

The command I listed has r and n, not m and s.

netstat -rn

Add ifconfig while you're in there!

If that is really your router and you can't ping it then we found much of your problem.

The command I listed has r and n, not m and s.

netstat -rn

Add ifconfig while you're in there!

This is a paste from the terminal exported onto a usb in PDF.
I have uploaded the file which hopefully has a better format.

Mac-Pro:~ root# netstat -rn Routing tables
Internet: Destination default 127 127.0.0.1 169.254 192.168.1 192.168.1.146/32 192.168.1.254/32 192.168.1.254
Gateway 192.168.1.254 127.0.0.1 127.0.0.1 link#4
link#4 link#4 link#4 4c:9:d4:d:67:c1
Flags Refs UGSc 1 UCS 0 UH 2 UCS 0 UCS 1 UCS 0 UCS 1 UHLWIir 14
Gateway
::1 fe80::1%lo0 link#1 link#4 f0:1f:af:1f:b7:32 ::1 link#4 ::1 link#4
Use Netif Expire 0 en0 0 lo0
18 lo0 0 en0 0 en0 0 en0 0 en0
112 en0 1036
Internet6: Destination Expire ::1 fe80::%lo0/64 fe80::1%lo0 fe80::%en0/64 fe80::f21f:afff:fe1f:b732%en0 ff01::%lo0/32
Flags Netif
UHL lo0 UcI lo0 UHLI lo0 UCI en0 UHLI lo0 UmCI lo0 UmCI en0 UmCI lo0 UmCI en0
ff01::%en0/32 ff02::%lo0/32 ff02::%en0/32

Mac-Pro:~ root# ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM> inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4> ether f0:1f:af:1f:b7:32 inet6 fe80::f21f:afff:fe1f:b732%en0 prefixlen 64 scopeid 0x4 inet 192.168.1.146 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=1<PERFORMNUD> media: autoselect (100baseTX <full-duplex>) status: active
Mac-Pro:~ root#
[doublepost=1455463717][/doublepost]

I have two Macs connected to the same router via ethernet cables.

One connects to the internet fine (via Safari), the other won't connect.

These are my settings per System Preferences -> Network:

Working Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.61.2
Configure IPv4: Using DHCP
IP address 192.168.61.2
Subnet Mask: 255.255.255.0
Router: 192.168.61.1
DNS Server: 192.168.1.254

Failing Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.1.146
Configure IPv4: Using DHCP
IP address 192.168.1.146
Subnet Mask: 255.255.255.0
Router: 192.168.1.254
DNS Server: 192.168.1.254

I wondered which addresses should be the same on both machines?
I noticed that the router address is different, should this be the same on both machines?

Any other suggestions to determine the problem would be much appreciated.

Just to add some further content to my original question:

If I search for www.google.co.uk in Safari it just hangs.
If I disconnect the ethernet cable then search in Safari I get "You are not connected to the internet".
So there is some difference.

I have a local apache server (via XAMPP) on my home network. On the failing MAC I can't connect via that address either.

 

[Mr. Buzzcut]

That actually looks okay. I hate driving you crazy running a bunch of commands. The best thing is to detail how everything is connected because I believe that's where the problem is. List how each device is connected, be specific with which port on the router connects to which MAC, where the Internet connects, etc. All the detail you can provide.

I am curious if the MACs can ping each other. Also, since one can ping the gateway and one can't, and they are both allegedly connected to the same router, we can compare the ARPs of each MAC "arp -a" to see if the MAC address of the router is the same.

 

[JohnDS]

Did you try swapping the location of the two Macs? I.e. unplug the ethernet cable from the good Mac and plug it into the bad Mac?

Also, in the network control panel, what are the DNS settings?

When connected by ethernet, try turning off WiFi.

Try turning off IPV6.
[doublepost=1455544003][/doublepost]Long shot, but is there any chance your /etc/hosts file has been compromised? Can you copy and paste its contents here?
[doublepost=1455544156][/doublepost]Is the problematic Mac a laptop or a desktop? If it is a laptop, will it connect from a different location, say an internet cafe?

 

[satcomer]

This is a paste from the terminal exported onto a usb in PDF.
I have uploaded the file which hopefully has a better format.

Mac-Pro:~ root# netstat -rn Routing tables
Internet: Destination default 127 127.0.0.1 169.254 192.168.1 192.168.1.146/32 192.168.1.254/32 192.168.1.254
Gateway 192.168.1.254 127.0.0.1 127.0.0.1 link#4
link#4 link#4 link#4 4c:9:d4:d:67:c1
Flags Refs UGSc 1 UCS 0 UH 2 UCS 0 UCS 1 UCS 0 UCS 1 UHLWIir 14
Gateway
::1 fe80::1%lo0 link#1 link#4 f0:1f:af:1f:b7:32 ::1 link#4 ::1 link#4
Use Netif Expire 0 en0 0 lo0
18 lo0 0 en0 0 en0 0 en0 0 en0
112 en0 1036
Internet6: Destination Expire ::1 fe80::%lo0/64 fe80::1%lo0 fe80::%en0/64 fe80::f21f:afff:fe1f:b732%en0 ff01::%lo0/32
Flags Netif
UHL lo0 UcI lo0 UHLI lo0 UCI en0 UHLI lo0 UmCI lo0 UmCI en0 UmCI lo0 UmCI en0
ff01::%en0/32 ff02::%lo0/32 ff02::%en0/32

Mac-Pro:~ root# ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM> inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4> ether f0:1f:af:1f:b7:32 inet6 fe80::f21f:afff:fe1f:b732%en0 prefixlen 64 scopeid 0x4 inet 192.168.1.146 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=1<PERFORMNUD> media: autoselect (100baseTX <full-duplex>) status: active
Mac-Pro:~ root#
[doublepost=1455463717][/doublepost]

You using a Linux command for a Mac OS X BSD machine. The command you need to learn is in man networksetup.

 

[martin2a]

I have two Macs connected to the same router via ethernet cables.

One connects to the internet fine (via Safari), the other won't connect.

These are my settings per System Preferences -> Network:

Working Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.61.2
Configure IPv4: Using DHCP
IP address 192.168.61.2
Subnet Mask: 255.255.255.0
Router: 192.168.61.1
DNS Server: 192.168.1.254

Failing Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.1.146
Configure IPv4: Using DHCP
IP address 192.168.1.146
Subnet Mask: 255.255.255.0
Router: 192.168.1.254
DNS Server: 192.168.1.254

I wondered which addresses should be the same on both machines?
I noticed that the router address is different, should this be the same on both machines?

Any other suggestions to determine the problem would be much appreciated.

I just wanted to say thanks to everyone that endeavoured to help me with this.

At the moment I have it working after installing a kext. Lets hope it stays that way.

Martin

 

[Fishrrman]

Hmmm....

What kext did you install?

 

[ScottyB123]

I have two Macs connected to the same router via ethernet cables.

One connects to the internet fine (via Safari), the other won't connect.

These are my settings per System Preferences -> Network:

Working Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.61.2
Configure IPv4: Using DHCP
IP address 192.168.61.2
Subnet Mask: 255.255.255.0
Router: 192.168.61.1
DNS Server: 192.168.1.254

Failing Mac:

Ethernet Connected and green circle.
Location: Automatic
Status: Connected
Ethernet is currently active and has the IP address 192.168.1.146
Configure IPv4: Using DHCP
IP address 192.168.1.146
Subnet Mask: 255.255.255.0
Router: 192.168.1.254
DNS Server: 192.168.1.254

I wondered which addresses should be the same on both machines?
I noticed that the router address is different, should this be the same on both machines?

Any other suggestions to determine the problem would be much appreciated.

[doublepost=1551455425][/doublepost]Help. I have the same problem. This first happened to my sons 2008 Mac Pro desktop a couple months ago, and now it is happened to mine. I have an ethernet connection, it is green, but I cannot connect to anything on the Internet. No mail, no messages, no webpages. Here are some shots.

 

[hobowankenobi]

[doublepost=1551455425][/doublepost]
Help. I have the same problem. This first happened to my sons 2008 Mac Pro desktop a couple months ago, and now it is happened to mine. I have an ethernet connection, it is green, but I cannot connect to anything on the Internet. No mail, no messages, no webpages. Here are some shots.

A 169 address....functionally means NO address. Think of it as an error. It means your device is connected physically. Like a plugged in phone with no dial tone.

Most commonly this comes from the local router on your network not handing out IP addresses as it should. Could be several reasons.

First thing first: reboot your router, and see how everything behaves.

You can also try the Renew DHCP License button, which asks the router for an IP address. The same thing happens automatically each time you reboot a device....a request for an IP address. This seems unlikely to solve any issues; the fact that 2 devices have this issue points to the router.

Do any devices get a working IP address (typically starting with 192.....and not 169)?