Dead Ethernet Port

I bought this machine used (2 ghz Intel Core Duo). I always wondered why I couldn't get it to connect to the internet with an Ethernet cable. Now, by comparing it with my wife's MacBook, I realize there must be something wrong with the Ethernet port. The jack looks okay -- I can't see any damage, but the plug won't click into position when I push it into the jack. Even if I hold the plug in place with my hand, no connection.
Three questions:
1-I assume replacing the jack would require a difficult board-level repair. True?
2-Is this a well-known syndrome with this machine?
3-What would it take to get a physical connection to the internet via the Fire Wire or USB ports?
Thanks,
Tim

It's me the OP, replying to myself, for the benefit of others who might have the same problem.
The Apple store sells an Ethernet to USB adapter for the MacBook Air, which does not have an Ethernet port. It seems likely it will work with other MacBooks, though one can't be sure.
According to user reviews on Amazon, the Cisco-Linksys USB Ethernet Adapter works on Macs without a driver.
Tim

Similar Messages

Is there a fix for a dead ethernet port besides a new logic board?

My ethernet port went dead on my IMac. I unplugged the ethernet cable and plugged it into my laptop and it worked instantly. I am still able to connect wirelessly. I bought an apple USB to Ethernet converter and plugged it in. It worked for about 3 days and then it went dead. Once again I was able to unplug the ethernet cable, plug it into my laptop and instantly had a connection. Is there a fix for a dead ethernet port besides a new logic board and if not how do I figure out which logic board I need?
Thanks
Step

This problem baffled me. I kept getting the "ethernet cable unplugged" error after testing my cables good. Was abut to write it off as port gone bad when I found this thread.
The YouTube video reference above fixed my problem. (http://www.youtube.com/watch?v=u1P6X87qArs)
Basically go to SETTINGS/NETWORK. Then highlight your ETHERNET port and click the ADVANCED button. From there click the HARDWARE tab.
Set
CONFIGURE to MANUALLY
SPEED to whatever your ethernet speed is, in my case 1000baseT
DUPLEX - FULL DUPLEX, FLOW CONTROL
Leave MTU at Standard
Hit OK.
Then don't forget to hit APPLY. I didn't do this the first couple of times assuming hitting OK applied these settings. You gotta hit APPLY.
In about two seconds, my Ethernet connected again.
I went back and reset it to AUTOMATIC just to test and after doing so got the cable unplugged error again. So I am leaving it on manual and it's working.

Mini ethernet port as a solution to imac dead ethernet port

I have an old imac 2002 version and it works great but the ethernet port is dead ...not sure why...but I have checked the cables and connections with another computer and they are fine...So assuming that the port is dead
Can I purchase a mini and use the ethernet port as my connection to the internet via dsl modem and still use my imac...what I'm wondering is can the mini act as a second hard drive and can I network it to my imac via firewire and the use the etherport from the mini to get on the internet....directing it all through my imac?
I have been told in order to get my imac to connect with a dead ethernet port I need to purchase a new motherboard. That seems like a simple solution...but my imac works great except the ethernet...so if I can find a solution that will just offer me a ethernet connection to the internet and still let me use my imac and give me more memory ...all the better...
I am not well versed on the mini....So I need some expert advise as to whether it could be a alternative solution...that would also give me additional harddrive.
Help!

Yes indeed. Your plan will work (I have done similar with mini/powerbook and powermac).
In a nutshell - set up the new mini to use the ethernet. Once the network is running, go to Sharing preference pane and select the internet "tab". Choose to share the Built-In Ethernet with the Built-in Firewire - and click start.
Then connect the mini to the iMac with a firewire cable. Set the iMac to use firewire for its network.
The only possible gotcha is if you are not on the latest OS (this should work back a version or two - but I don't recall when I first did this). Second gotcha might be the firewall on the mini. You may have to enable logging to see if the firewall is preventing the iMac to connect in and through to the internet. If so - you have to live with opening up some ports on your firewall or learn how to configure that one iMac to get in and not the rest of the world (assuming you don't have a router or other firewall device to protect the new mini.)
Cheers and good luck.

Battery & Dead Ethernet port question

So if my battery is showing no outward signs of getting old but my ethernet port is dead could an older battery cause this? (All other possibilites covered but a new battery... prior to a PCI card purchase... thought I would ask...)

My ethernet port won't work either, so I bought a PCI card. It has the same behavior as my ethernet port. Neither the card nor the port will connect with DHCP anymore (worked for 4 years and stopped a few days ago). If I specify an IP address it will connect manually, however it will only connect me to the router, meaning, I can access the mac on the network with another computer but cannot access the internet on the mac (other computers are connected to the same router and on the internet).
I originally thought it was the battery. Then I thought it was Ethernet port failure until the new PCI card I bought did the same thing. I’ve flashed the PRAM, replaced the battery, and reinstalled OS X. Nothing seems to fix it.
Please help. Thank you in advance.

W500: Dead Ethernet Port

Today my ethernet port stopped working. While Linux can see it (I'm running a brand new install of Linux Mint 14), and it appears to attempt to connect, I cannot acquire an IP address and connect to any network. I've verified that the ethernet cable works just fine, and the ethernet does not work either with a live CD or in Windows (I had beed trying to set up a dual boot, but give up and went Linux-only when I couldn't get Windows 7 to connect to the LAN, erroniously thinking it was a driver issue). What can I do? The wireless on my college campus is absolutely terrible; it's likley going to take three hours just to get my fresh Linux install up to date. I don't have the money for a new computer at this time.

It looks alright. It was going into an infinite loop of trying (and failing) to get an IP address. Ironically it started working again when I got back to my room. I wonder what it is about the network in the applied CS labs that my laptop hates, since the same cable/port on the wall would work fine for other computers.

Dead Ethernet port ATV, will Apple USB connector work?

My ethernet port on my ATV died. I have made sure the cable and switch are okay (by connecting to another device). I have done a factory restore since this port worked until a couple of weeks ago.
Will the Apple USB ethernet adapter and plug this into the ATV to get a wired connection (is the driver in the ATV 2.0 driver library)?
Trying to connect to wireless isn't working on a secure network (tried WPA-PSK, WPA2-PSK and WEP (hex and ascii). ATV sees the network but cannot connect. Using Buffalo Airstation WZR-HP-G300NH. Wireless worked prior to factory restore using WPA2-PSK (was at latest ATV version).

Sorry but no. The USB port (without hacking the OS) serves no user-accessible purpose. If the Ethernet port has failed and your Apple TV is out of warranty, you'll have to try and get wireless working. Perhaps if you start a new topic with that issue, someone here can help you get that sorted.
Regards.

Dead ethernet ports on HH3

Hello. Wifi working but nothing from any of the ethernet ports on the HH3 as of yesterday. We got a lightening strike which set off the burgler alarm and tripped one circuit but no other electrical damage as far as I can see. Rebooting/resetting makes no difference. New unit required?
Solved!
Go to Solution.

Yes, sounds like the lightning roasted it.
If you found this post helpful, please click on the star on the left
If not, I'll try again

My Airport Express ethernet port is not working

I recently purchased a refurb Airport Express (latest version) to extend my home wifi. Extending the network works fine. I then tried to set it up as a wireless bridge to my new AV receiver but the receiver would not connect -- no IP address, nada zip. I had changed the settings to join a wireless network and checked allow ethernet client, rebooted the express several times, even tried a hard reset. I connected two laptops using a spare ethernet cable. The won't connect either. It keeps trying to connect, but it does not succeed. Am i doing something wrong or does the refurb unit have a dead ethernet port. I would appreciate any help you can provide.

When extending the network, my wireless clients get an ip. The Express is just acting as a pass through the router. The laptop I am typing this on is getting its signal from Express.
When I change the configuration to have the express function as a wireless bridge to my new AV receiver, nothing. No IP, no connectivity of any kind. I then tried in with this laptop (Win 7 HP) and my wife's MacBook Pro. No connection. It keeps trying, it goes through an identifying cycle but then says no cable connected. I have tried different cables and still nothing. Are there any other settings in the airport utility that I am supposed to change beside the wireless tab where I set it as join the network and allow ethernet clients. I retyped the WPA2 password just in case. I'm stumped and would appreciate any assistance.

Ethernet port dead on Powerbook firewire

ethernet port dead on my Powerbook Firewire 400MHZ G3 1GB RAM 40GB HARD DRIVE DVD-ROM
I tried Open Firmware Reset and PRAM RESET AND WOULD I NEED TO GET A NEW LOGIC BOARD.
Joshua Lich
The port stopped working for 2 months and i have no AHT DISKS OR PROPER IMAGES TO DO SO

Hi, and Welcome to the Forums..
Ok, since you already did a PRAM reset and that didn't resolve the problem.. there is ONE LAST step before we can say it is or could be the logic board.. Do a PMU reset. This is a hard reset where you would have to do the following:
A full (PMU) reset of the Pismo (Apple calls it a 'PowerBook (FireWire)') follows: If the computer is on, turn it off. Press and release the reset button located on the rear panel of the computer between the external video and modem ports. Wait 5 seconds. Press the Power button to restart the computer.
If and only if you do this and the problem is not resolved, either you will need the Apple Hardware Test which came packaged with the Pismo or you will need MacTest Pro also called: Apple Service Diagnostic to do further diagnostic checking on the Pismo's ethernet port.
Try the PMU reset above and report back.. Try to then plug in an ethernet cable and see if u can get any response from it. If not, I would suggest getting the AHT or MTP from someone.. Actually, if you email me I might be able to further assist as I DO have the tools to make your Pismo work again, hopefullly assuming its not a logic board issue.
Romko

Ethernet port dead after powerdown

Hi All;
I have noticed that my Quad is acting strange after I power it down, in that the ethernet port is dead after I power the unit down. By this I mean that I am unable to connect to the network after I power the Quad back up again. I have noticed that the leds on my ethernet hub are not lite after I power the Quad back up again until I remove and reconnect the ethernet cable out of the back of my Quad. Once I do that everything works normally.
I have been using this ethernet hub with both my Powermac G3 and Powermac G4 and never noticed anything like this before.
Anyone have any ideas as to qhy my Quad is acting so strange? Thanks.
Allan

Hi bonaroo;
Yes, I tried all of the standard fixes without any luck.
The other day we had a power outage and my DSL router failed to start again once the power returned. I went out and bought a new DSL router. The new one gave me a bunch more information about everything.
When I restarted my Quad I noticed that network tried to start but failed most of the time. With the new router I received a brand new Ethernet cable. So I decided to try it. With the new cable, all of my network problems were gone. It appears the old cable was one I got with my old G3. I think it was CAT 1 or CAT2 maybe. I had it in a bundle of cables behind my desk all tie wrapped together and was too lazy to remove them.
Well as soon as I saw how much better the new cable was, I immediately removed the old and I am tie wrapping everything together again.
It appears my old cable could not do the hand shake with the new gigbit Ethernet card in the Quad.
Allan

How can I really check my ethernet port dead or not ?

I have a Imac CRT 266. I tried to connect the ethernet port using a hub but my hub never receive a signal (led off all the time). Everything seems fine on Imac side (I'm running 10.1.5 - no message on console, I can configure my IP). My hub is OK too, I check with others computers.
Ethernet port could be dead without impact for the rest of the computer ?
Thanks.

Ethernet port could be dead without impact for the rest of the computer ?
Unfortunately, yes. Your test for a green light is the simplest way to test the port. Make sure you have tried this using another piece of cord and used all ports in the hub to confirm. There's a chance that reinstalling the OS might make a difference--assuming the problem is software- rather than hardware-related. Good luck.

Ethernet port dead- new logic board needed?

The ethernet port on my 2010 iMac 21.5" died after a storm last week, so I brought it to the Apple store to have it checked out. They said it needs a new logic board since the port is connected to it, which will cost around $700. I can't see spending that much money to fix it, anyone have an ideas on where I could sell it for parts? The guy I spoke to at the store said to give it a shot

Is your wireless still working? You could connect your Mac over Wi-Fi instead, if you still wanted to use the Mac, that is. Or use a USB Ethernet adapter. Apple sells one for $50 that was primarily for the Macbook Air, but will work with any recent mac. But if you already have Wi-Fi, then I'd try that. And if you don't have Wi-Fi, it still may be useful to try Wi-Fi first because even if the Mac's Wi-Fi doesn't work, you can still attach other computers or devices like iPads or iPhones, etc. Whereas it would be a waste to buy the USB ethernet adapter only to find out that the USB ports on your Mac were also affected by the storm.
Otherwise, as usual, you can always sell on eBay & Craigslist.

Ethernet ports probably dead

Took a lightning strike this weekend. Everything in my studio was protected except the DSL modem phone line. So the spike on the phone line killed the DSL modem and the router. The Airport Express connected to the router via Ethernet cable appears to be fully functional. But the Ethernet ports on the Mac Pro connected to the router didn't fare as well, and are not working (the Mac Pro was completely powered down during the storm). I ran the Hardware Test from the OSX DVD, and it revealed no problems. Is the Hardware Test able to check the Ethernet ports?
Both Ethernet ports appear in the Network Prefs Port Configuration list, but they are greyed out. Should I have some hope from that? Why would they be greyed out? Is there anything that I can pursue on the software side to see if I can resurrect my Ethernet connectivity?
Thanks for your thoughts, suggestions, or insight.

APC has RS-series that allows plugging in DSL and then, out of the modem, goes through a 2nd RJ45. The guys from APC when I asked about XS-series pointed me to the RS, to help protect ethernet ports and because what got filtered on DSL is still too high.
They also have network surge protectors that should do the same w/o cost of a full 1500VA UPS. Even though powered down, a system is still vulnerable.
PCI Express ethernet is probably one option. I know Intel supports a number of cards.
The only thing I can imagine helping is to leave everything unplugged over night and use the SMC RESET button, but I don't have high hopes.
Delete the old settings in Network control panel and see, or use ethernet over Firewire?

Ethernet port dead !!??

Hello
I get a router with ethernet connection and ADSL network
After a storm my router crashed but my computer was closed before
When I connect Ethernet cable to the new router : no signal, nada, rien!!!
The cable is good, apparently the router is ok
System profiler says OK for infos
Techtool Pro says OK for test
In the Network Utility infos, I see 2 ethernet interfaces which have both speed=0 and for the link :
ethernet (fw0)= inactive
ethernet (en0)= no signal
Can you explain me the problem and eventually repairing process
Thanks very much
Michel

Hi, Michael -
Welcome to Apple's Discussions.
Some thoughts -
The cable is good...
How do you know? Since you have a new router, it would appear the old one got fried during the storm. If that was the case, any cable connected to the router should be suspect. A visual examination of a cable is often insufficient.
Your G4, like many Mac models, has a peculiarity - if the Mac does not detect the presence of a live device attached to the ethernet port during startup, it will disable the ethernet bus.
The solution - make sure the router is on, warmed up, and connected to the Mac before booting the Mac.
Your G4 400MHz model, unless it is a Gigabit Ethernet model, does not have an auto-sensing ethernet port. If it is not a GE model, that means that the ethernet cable between the Mac and the router should be a Patch type cable, and not a Crossover type.

RT: How do I use two independent Ethernet ports?

I have looked around at the forums and seems like no one has had a real solid answer or example on how to use 2 Ethernet ports with RT.
Right now I have two connections configured on the RT:
Primary Connection:
IP:192.168.2.181
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1
DNS Server: 192.168.1.1
Secondary Connection:
IP:192.168.1.180
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1
DNS Server: 192.168.1.1
After using this initial setup, I made a RT project where I used 'UDP Open' for both 192.168.2.181 and 192.168.1.180, and had them both read and write in a sequence (Read and Write for the 2.181 connection, then Read/Write for 1.180).
The computer I'm using to send the data is connected to a switch, which in turn is connected to the RT. Both the RT and my host computer have 2 ports, one of them with ports configured to be 192.168.2.x and 192.168.1.x
Using this configuration I get some weird results:
If I send a packet to 192.168.2.181, I receive it from the UDP Receive vi that has an input connection from my UDP Open assigned to 1.180. I also receive the data the same way when sending packets to 1.180 (as expected). Basicly, no matter what IP I'm sending it to on the RT, the data from either packet will arrive from the same location/vi.
Why is this? Is there anyway to fix this? Did I not configure something correctly?
Does anyone have an example of dual Ethernet ports actually working with LabView RT?
I tried checking out "KnowledgeBase 3VQ6278T: Can I Use Multiple Network Adapters in a PXI or Desktop Real-Time System?", but after following the link to the page, I get:
"Error You are not authorized to view this document". Can any NI people look into this?
Having to make two IPs with different subnet masks obviously just makes things unnecessarily complicated. Can anyone tell me why LabView/NI did this? I know for a fact this isn't a limitation in hardware.
Any help would be greatly appreciated, thanks!

Hey Weizbox.
Sorry to hear you're having such a difficult time using multiple ethernet devices with RT.
Let me go ahead and get the easy stuff out of the way, the link you
have is dead because it's archived (and thus removed forever) though
unfortunately the link on ni.com wasn't corrected to point to the
following resource, which the KB was a word-for-word duplication of
(which is supposedly why it was removed):
http://zone.ni.com/reference/en-XX/help/370622C-01/lvrthelp/configuringdual/
Unfortunately, though, it's much less useful than it sounds.
Before you start feeling like a woodpecker in a petrified forest, lemme
fill you in on why the requirement is there for the two ethernet NICs
to be on seperate subnets. Simple enough, it has to do with the
network stack on both of the operating systems used for LabVIEW
Real-Time - however, the same falls true for even Windows (without
using fancy vendor-specific drivers), so let's not be too hasty.
Neither PharLap ETS nor VxWorks, the two OS's used under the hood,
support redundant network ports. Because of this, if you give two (or
more in the case of PXI and RT Desktop) ethernet devices IP addresses
on the same subnet the routing tables in the network stack get horribly
confused and literally cannot resolve the proper adapter, which either
brings down the ethernet on the entire system or makes it such that one
or more network adapters becomes useless and one adapter takes over all
network traffic (there's no way to predict which adapter that will be,
nor can you control it based on what's plugged in and what's not). On
Windows this is handled by bridging the adapters, but RT does not yet
support bridging (that opens a whole nother can of worms). Long story
short, you still wouldn't be able to give both NICs individual IP
addresses on the same subnet.
Let's take that even one more step. You cannot simply just assign both
ethernet NICs different IP addresses on "virtual" subnets, you actually
need to put both NICs on literally different subnets for the network
routing to actually work. Multiple ethernet devices for LabVIEW RT
were designed with the following mantra in mind - "The FIRST ethernet
device is designed for a TCP/IP network, the SECOND and SUBSEQUENT
ethernet device is designed for OTHER protocol uses." By "OTHER
protocol uses" I mean the second NIC should be used for RT
Deterministic Ethernet (PXI, RT Desktop, et. al.), direct connections
with other targets, and 3rd party or custom ethernet protocols.
Now, realistically, we can't expect users to not use the second NIC for
TCP/IP use, nor should we. However, if you ARE going to use TCP/IP on
the second NIC, you should only use the second NIC for connecting to an
unroutable network in the eyes of the first NIC. So, for instance, the
FIRST NIC can have an IP address of 10.0.62.128, but the SECOND NIC
would need to have an IP address on 192.168.100.23 - and the
10.0.62.128 should not be able to route a TCP packet to the 192.168.x.x
network, and vice versa. In your example I noticed that both networks
used the same Gateway - unless your Gateway is configured to identify
and seperate the two networks, it's not going to end well, and you
shouldn't expect to be able to send data from one NIC to the other NIC
(at least with what you know now). To reiterate, using multiple NICs
using TCP/IP should only be done in cases where you've got (n-1)
isolated subnets, where n is the number of NICs you have using TCP/IP.
A classic example of this is a command-based measurement environment;
the RT system uses the FIRST NIC to talk to a TCP/IP network, in order
to transfer data or provide status to a network, and the second NIC is
connected to a TCP/IP network designed specifically for measurement or
control, where one node sends commands to a single or multiple nodes on
the network at once to perform tasks (like "Take a Measurement", "Stop
a motor", "Bake me a Pie", etc...). The isolated TCP/IP subnet is free
from "random" TCP/IP traffic (especially system announcement
broadcasts) and can have whatever topology/configuration it wants. The
dual networking allows the RT system to work/communicate/perform on
both networks.
I hope this helps shed some light on your situation.
Cheers!
-Danny

Dead Ethernet Port

Similar Messages

Maybe you are looking for