Lighting fried my Ethernet port

A Lightning strike fried my Router and Ethernet Port.
I've bought and new asdl router and this works with my laptop.
I've done a hardware test on my desktop g4 and everything appears fine. Using both the 'System Profile' and 'Hardware Test' the ethernet hardware is visible i.e. it tells me I have "built-in ethernet" and that nothing is awry. Connecting the g4 to the router with a new cable no light turns on indicating that a conection is made and the network preferences on the g4 state "The cable for Built-in Ethernet is not plugged in."
Has anybody replaced the physical port for their built in ethernet?
Or do I just buy myself an Scsi ethernet card and plug this in?
Are there any command line tools for diagnosing the status of the ehternet port with more detail than "the cable isn't plugged in'?
cheers, ewan.
dual 1.42ghz g4 desktop powerpc Mac OS X (10.4.6)
Mac OS X (10.4.6)

Many UPS models have an RJ-45 that you want to use for wired connections between the modem and router/switch. Even if you have a surge protector on your phone line before it gets to the modem (and you should) it still lets through more than is safe.
Just add a PCI ethernet card. Take a look on www.xlr8yourmac.com
or www.macwireless.com has them also.

Similar Messages

Link Light on the Ethernet port ?

Hi,
Is there a link light on the Ethernet port on the MacBook Pro ? It looks pretty dark to me ;-(
MacBook Pro Mac OS X (10.4)

No I have a feeling it's a 2-bit ethernet card, not a gigabit one.
I just opened up the box yesterday. I thought the
world of Apple was going to be better.
I am going to locate an Apple Store next week to see
see what their repair calendar looks like.

Time Machine's WAN port doesn't light up, but Ethernet port does

Hi there,
We have a guest sleeping in the spare room where our Time Machine is also located and because of they are a light sleeper we've had to turn off the power at night. I've then noticed that it has become more and more difficult to setup my internet again.
Firstly, when I powered it back up, it began to flash amber and wouldn't recognise the modem plugged into the WAN. My first approach was to turn everything off and then turn them on again. This had worked the first few mornings after having the issue. But this method doesnt seem to fix the problem anymore.
Regardless, I now continue to receive the flashing amber light. For troubleshooting, I tested the internet connection direct to my Laptop and it worked fine, so I know the internet modem isnt the problem. I then plugged the internet into the Time Machine ethernet port and the green light began to work. I can also access the internet by airport through the TC with this connection.
My question is, why is the Time Machine able to detect the internet through the Ethernet Port, but not through the WAP port?
Also, by using this setup going forward, am I be putting myself at risk of any damage to my TC device, or exposing my personal data to the internet?
thanks for any and all suggestions.
Regards,
Elise

Is the TIme Capsule in Router mode or Bridge mode.. ??
It makes all the difference in the world.
How old is this TC?
It might be worth just doing a reset and set it up again.. make sure you use bridge not router if the modem already is running router function, otherwise TC will pop up an error due to the double NAT.

Fried Ethernet port?

My Late 2012 Imac (13,2) was brutally attacked by a power surge during a recent thunderstorm;
it fried every connected ethernet port on my network (ie: modem, router, TV, AppleTV, TV receiver) and the ethernet port on my imac. Once i had the modem and router replaced; i find my ethernet port on my imac is dead; it still shows up in system profiler but no connection can be established;
of course i was a nitwit and didn't extend the coverage of my applecare, but i am wondering what steps i can take to get it back online, or if i need to take the imac in for repair.
and if i need to get it repaired, how much it would cost to have what i assume would be the logic board replaced?
any suggestions would be a great help!
In the mean time, i can still get online with my wireless card and gently weep for the loss of my damaged port.

AppleCare would not have fixed it any cheaper than without. They only fix manufacturer defects. The only foolproof way to prevent issues with lightning on a computer is to unplug it during a storm. You can bring it in for repair, but it is unlikely to be cheap. If your hard drive is still useable, get it removed and install it in an external hard drive case. You'd be better off replacing the machine with a comparable machine used or refurbished*:
http://www.macmaps.com/usedrefurbished.html
Unless you are certain that all your applications and drivers are 10.9 compatible:
http://www.roaringapps.com/
OS X: Printer and scanner software available for download have 10.9 compatible updates from these vendors:
HP, Ricoh, Canon, Epson, Brother,Lexmark, Samsung, and Fuji/Xerox
OS X Mavericks: Supported digital camera RAW formats
In which case, you can get a new Mac which would have 10.9 prebundled. Any Mac from
late 2013 on would have 10.9 prebundled and can't have 10.8 installed.
* Links to my pages may give me compensation.

Why do the three ethernet port green lights go out?

At random times my 802.11n (gigabit) AEBS seems to get very confused and I have to power cycle it. I noticed that one indication of things amiss is the fact that the 3 ethernet port status lights are out. Anyone know why that would happen?

I don't know, but I have the Airport Extreme with Gigabit ethernet, and I notice that the ethernet ports' lights go out whenever I make changes to the base station (ex. if I change port mappings). So after it reboots, that's when the lights go out. Everything seems to work fine after that though, even though the lights are out. The indicator light on the front is always on though.
Another member, Akislot, posted a similar problem in the following thread:
http://discussions.apple.com/thread.jspa?messageID=5748864
So we are not alone, but I wonder if this issue is normal. I have tried both the soft reset and hard reset, and I have also reinstalled the firmware to the latest version (7.2.1). The issue still persists, and power-cycling allows the ethernet lights to return. Sometimes attempting to change the port mappings allows the lights to return, but not always. Power-cycling always allows the lights to return.
I just bought this 2 days ago too, so it is brand new.
If I still cannot find information online today, I think I will contact AppleCare. Does anyone know anything about this? Please let us know if you do. Thanks so much!
Cya!
\m/ Mage \m/

Ethernet port fried by lightning strike?

My phone line and home was struck by lightning this weekend. All of the DSL filters in my home were fried and blown open simultaneously, the DSL modem was fried, and even with a new modem, I cannot connect. Is there any way (without taking it in) to test the ethernet port itself? Is there some sort of internal diagnostic that can detect a faulty port? The computer works fine otherwise. IF the port is dead, is it better to buy a new computer? (My insurance is covering all damages), or is the cost to repair something like this minor? I have read about using an airport as a go-around, but I'd rather fix the problem, not patch it. ANY and all info will be helpful. Thanks.

caparsons wrote:
My phone line and home was struck by lightning this weekend. All of the DSL filters in my home were fried and blown open simultaneously, the DSL modem was fried, and even with a new modem, I cannot connect. Is there any way (without taking it in) to test the ethernet port itself? Is there some sort of internal diagnostic that can detect a faulty port? The computer works fine otherwise. IF the port is dead, is it better to buy a new computer? (My insurance is covering all damages), or is the cost to repair something like this minor? I have read about using an airport as a go-around, but I'd rather fix the problem, not patch it. ANY and all info will be helpful. Thanks.
If the Ethernet port on an iMac is fried, you can replace that port only by _replacing the entire motherboard_. Depending on the kind of motherboard, the price could be several hundred dollars. It might be more cost-effective to get a new computer.

Can't login to Mac App store on mac mini. Is it because my ethernet port is fried?

Hi
like many others, I am unable to log in to the mac app store on my mac mini. I get the error message saying "An unknown error has occured". I believe the ethernet port is damaged after an electrical storm, but I can still get online wirelessly. I've read on these forums that the app store verifys the account using the ethernet port. Can anybody confirm if this is the case, is there a workaround that anyone knows of?
I can log into the App store on my laptop fine, just not the mac mini.
Thanks in advance
Paul

This is happening on 2 of my machines. One is OSX Lion, the other OSX Mountain Lion. My personal rig works just fine - all on the same network, all with the same basic configuration. All can log in and out of iTunes, but the two servers can't login via Appstore. My rig and one of the servers even use the same Ethernet driver, so it's not that.
I would seriously doubt your Ethernet card would be working at all if it was indeed damaged by the lightning. The transducers are relatively sensitive, and it would either fry or not. You won't get "intermittent" operation as you have described. Here is a list of all the things I've tried (based on a number of forum suggestions), none of which has worked:
1) Sign out of itunes, sign back in, try to sign in to AppStore.
2) Re-enter information in your account info and save it again (knew that wasn't it but tried anyway).
3) Ran AppStore as root.
4) Using EFIStudio, I got the hex string ID of my ethernet card and specifically reference "device-properties" in the boot.plist. Others have said this works, so you might give it a try -
http://legacy.tonymacx86.com/viewtopic.php?f=169&t=28477
5) Deleted all other ethernet devices to avoid "confusion" of the return.
6) Verified I can get HTTPS returned from NAT device.
7) Used Wireshark to get a packet capture of it working on mine and not working on the other. On the one that doesn't work, all I get is a couple of SYNs to the appstore and then nothing. It was along these lines that I was hoping the "device-properties" would work.
I just thought of something though. If I don't see that ACK at all, it might be sending the packets somewhere else. hmmm. I'm going to hard-code in all HTTPS to be routed to that box and try it just for S&G.
Good luck!

Is my Ethernet port fried?

In the last couple of days I've noticed that I can no longer talk to either of my two DSL routers using a cable and DHCP. Every time I connect either of them to my iMac G5, Network prefs tells me that a self-assigned IP is in use and that I may not be able to connect, which is indeed the case. However, I can connect either router to my Airport Express and then wirelessly connect from my iMac, so DHCP is certainly working, as I can verify if I look at the router's configuration pages in this setup.
So, does this mean the Ethernet port in my iMac has gone belly-up in some way? Is there any way to reset the Ethernet hardware and get it to talk to the routers again?
Thanks.
Message was edited by: RichardLim

UPDATE: Networking has returned to normal! But the way it happened is, to my mind, pretty unbelievable.
I said in my previous post I was just heading out. I was getting to ready to leave, and the computer had gone to sleep. But then, just like it's been doing in the last couple of days and occasionally in previous weeks, I heard the computer's fan suddenly start up and go absolutely crazy, like the iMac was burning up. As usual, there was no option but to do a hard shutdown as the computer will not wake from sleep when this happens. Restarted the computer and, after the 5-minute blue screen, logged in here to read up on what could have caused this sleep issue. Decided to reset the SMU and lo and behold, after I did that, the startup delay disappeared and when I connected my router by wire to the computer, the iMac immediately picked up a correct IP address via DHCP!
So, somehow resetting the SMU has cured all the problems I've been having for the last 48 hours. I'm frustrated but now happy as well.
Message was edited by: RichardLim

Running 10.6.8 on mac mini. ethernet port quick. I can not print using wireless

Can not print using wireless. It printed fine using ethernet
Running 10.6.8 on mac mini. Ethernet port has quit. (lighting strike I think, it fried two routers, did not get anything else)

Nothing to go on here.
Do you have a wifi capable printer? If so, what model? What happens when you try to set it up?

Can a power surge damage the ethernet port?

My internet was working fine, then a storm came in and the lights flickered. Since then my ethernet port says there is no connection even though there is. I have replaced the router and checked the connection and cable on another computer and they work fine, but the imac no longer recognizes my cable plugged into the port, it just says nothing is connected. I have a surge protector on my imac but not on my router, is it possible a charge could have traveled up the line and fried the port?
I can't find any other reason to explain why it stopped working. Does anyone have any tips on getting the ethernet back up and running?
thanks

Yes, that can easily happen if the equipment is not protected in any way.

Airport Extreme Ethernet Port Won't Recognize DSL Connection

Hey ya'll,
We had a big thunderstorm -- power in house stayed on but stupid AT&T DSL connection went down. When I got the connection back up, the Airport Extreme continued to give me blinking amber light saying the ethernet cable is not connected -- even when it is. Tried reconfiguring to no avail. Is my Ethernet port somehow fried? Is there something else to try? Any help will be GREATLY appreciated as having to be wired to the DSL is making me very cranky. Thanks!

OK, I just tried another external HD. This time it was LaCie 1Tb. As soon as I connected it, it was recognized by AirPort Extreme. What's puzzling is, that same thing happened with my SimpleTech 1Tb one last night. It was easily recognized by AE and then all of a sudden AE would never recognize it again.
At first, I though maybe these HDs are not supported by AE, but that's not the case. One is LaCie with Samsung HD103UJ drive inside purchased at Apple store, another one SimpleTech with WD inside, and other two are both super reliable Sygate HDs (never ever had any problems with them).
Hmm... I just disconnected LaCie one and tried SimpleTech one more time and it worked. AE can see it again. What's going on in here? Something is definitely not right.
Can't test this port through printer since I don't have one available at the moment.

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

Can I convert a PB 1400's PC card port to a ethernet port for file sharing?

My plan here is to connect a PowerBook 1400cs/133 running OS 8.6 to an iBook G4 running OS 10.4 by means of an ethernet crossover cable, and move my important files (ClarisWorks 4.0 docs and games mostly) to the new computer. But the PB 1400 has no ethernet port! Is there something I can put in the PC card slot that will convert it to an ethernet port?

jpl, Denis, here's my setup:
The PB 1400 is connected to the iBook via a Farallon EtherWave/EtherMac Ethernet PC Card (with a blue arrow, PCMCIA 2.1, PC Card Standard). I have the Farallon software installed and the Farallon extension turned on. A "Farallon EN Card" icon appears on my desktop, and the little light on the cord where it connects to the card is green. I used to use the card to connect to the internet back in the day when the 1400 was my primary computer, so I'm confident it works.
The PB 1400 (name: Ben's PowerBook 1400): AppleTalk, configured to connect via alternate ethernet. File sharing, on. TCP/IP, connected via AppleTalk (Mac IP). I've tried configuring that both "Using Mac IP server" and manually by entering in the iBook's IP address and router address (the 1400 is not connected to the internet). As far as I can tell, Users/Groups is configured; it has "Ben" as "user" and "Guest" as "guest user."
The iBook (name: Ben's iBook G4) is set up basically identical to the way jpl describes his iMac above. Like his, the services panel of sharing on the iBook says "Other Macintosh users can access your computer at afp://x.x.x.6." I also manually entered the iBook's IP address, subnet mask, and router. Under my shared location, under Built-in Ethernet, TCP/IP is configured and AppleTalk is active.
Still, file sharing is not working. When I try to access the iBook from the 1400, I go to the Chooser, click the AppleShare icon, and "Ben's iBook G4" in the file server window. When I select it and click OK, I go to a screen to enter my name (Ben) and password as a registered user. I'm not sure if the password it wants is the file sharing password I set up for the 1400 or the administrator password for the iBook, so I tried them both. I also tried connecting as a "guest." In all cases, after I hit the "Connect" button, I got the error message "The connection to this server has been unexpectedly broken."
No luck going the opposite direction either. When I go to Go: Connect to Server: Browse on the iBook, "Ben's PowerBook 1400" appears in the Network area, but when I select it and hit the "connect" button, I get this error message: "The file server uses an incompatible version of the AFP protocol. You cannot connect to it."

HP Color LaserJet 3600(not 3600n) with Fast Ethernet port - can I use it?

Hello! There is a HP Color LaserJet 3600 in our company connected via USB with XP-based PC. Recently I decided that we need this printer be shared directly trough our ethernet network, so I started to learn manuals - its own manual, Jet Direct, and all that stuff. The printer's manual says that HP Color Laserjet 3600 does not have neither its own ethernet port, nor support for embedded print-server like JetDirect 620n.
But!
Visual check shows that this HP 3600 DOES have its own ethernet port and if I connect it to network or at least to a notebook - it blinks like any other ethernet port with "lights" should do.
However.
Neither front panel, nor back panel says anything about network support(like letter "n" in model name).
Configuration page print also does not know about that mysterious port.
So my questions are:
1. What is this port actually?
2. Can I use it to share printer over network? Maybe, there is a way to upload 3600n's firmware somehow?

The product you have seems to be a commercial printer. For the best chance at finding a solution I would suggest posting in the forum for HP Business Support!
You may find the Commercial Laserjet board here.
http://h30499.www3.hp.com/t5/Printers-LaserJet/bd-p/bsc-413
You can also find the article pertaining to this product here:
http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?lang=en&cc=us&prodTypeId=18972&prodSeriesI...
(contains basic troubleshooting info, manuals, drivers, etc)
Hope this helps!
Help the community by marking this post as a solution if it solved your issue!.
If my post helped you in any way, please click the blue KUDOS star under my name! It would mean a great deal.

The ethernet port on the thunderbolt display is not working

The ethernet is working when the cable is connected directly to my mac laptop but when connected the thunderbolt display there is no connection. Is there some type of set up for the ethernet connection or can this port just be broken?
Thanks for the help!

Afterthought on an older post: it isn't immediately clear that the Ethernet port on the Thunderbolt Display works through the "Display Ethernet" interface, rather than through the "Thunderbolt Ethernet" interface. The latter was already present in the list of network interfaces in Network Preferences, while the former had to be added via the + button --- at least that was the case when I installed the TB display to work with my 15-inch MacBook Pro Retina this week.
The AppleCare rep didn't know the difference either and agreed with me that it was puzzling that using the Thunderbolt Ethernet adapter on the Thunderbolt port of the display did work, wheras using the Ethernet port directly didn't (even though there were lights flashing on the Ethernet port of that other computer I tried to connect to in Internet Sharing mode). Close reading of the above posts made me go look for that mysterious "Display Ethernet" interface... thank you Clinton!

Lighting fried my Ethernet port

Similar Messages

Maybe you are looking for