Bad network card

It seems as though the network card in my L7680 has failed. What is the best way to get this fixed/repaired/replaced? I have already done the typical troublwhooting - new cat 5 cable, different port on switch, etc. Totally dead - no link light.
Thanks.

Hi Kevin1000,
I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial printer. You can do this at http://h30499.www3.hp.com/hpeb/ .
I hope this helps.
Regards,
Happytohelp01
Please click on the Thumbs Up on the right to say “Thanks” for helping!
Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
I work on behalf of HP

Similar Messages

Intel network card

Hi all,
After few days struggling with laptop install for solaris 8, at the end of the day, I successfully run solaris 8 on my laptop. I got my built-in network card to work and graphic card to run at best resolution.
One thing I'm not quite sure is error message that I received after few hours doing network stuff. The error msg as below :
"WARNING: iprb0: statistics generatefailed."
"WARNING: iprb: device never responded."
I tried to bring down the interface and up again but no luck. The only solution is to restart my laptop which is bad. I already applied latest patch for iprb. Anybody could shed some light on this case, please?
Thank in advance.
regards,
zonex

The network card can go bad yes. Here is what i would recommand you do is call tech support and get a case number and send it in for repair also get a shipping address so you can send the thinkpad with the bad network card in for repairs
Thanks
Keep me posted on this.
Matthew C Hilinski Lenovo c200 out of warrenty
ubuntu 9.0

Updated bios via Live Update and now my Network card isn't detected

I have an msi Z87-GD65 Gaming Motherboard and I updated some drivers and the bios via msi Live Update 6 last night and now my computer refuses to recognize my network adapter. The adapter is a TRENDnet N600, plugs into PCIe if I'm not mistaken. Wifi if my only option with this computer, I can't use ethernet, so it's really important I get the network card working again. I have had zero issues with it until this.
The reason I was updating was to try to get my third monitor to work when plugged into the mobo, while my other two were plugged into the graphics card (which I also installed yesterday, but it's working fine). Note that it still was not working, but I had enabled the IGD Multi-Monitor from bios.
Any suggestions would be appreciated. I did try uninstalling the drivers but it still won't detect the network card. I also tried disconnecting and reconnecting the network card (and I cleaned the port for good measure).
I've only been using Windows computers for a year, so bear with me if there's stuff I don't know. Thanks in advance. I can try to get a full list of what was installed later tonight, but all of it that I can find has been uninstalled at this point.
Note: I did not flash the bios when I installed, which I have now heard is a bad idea, apparently. l:

what OS you are running?
Quote
Note: I did not flash the bios when I installed, which I have now heard is a bad idea, apparently. l:
you said you've updated drivers & BIOS:
Quote
I updated some drivers and the bios via msi Live Update 6 last night and now my computer refuses to recognize my network adapter.
can you clarify is you update BIOS too or not?
and what is your current bios version?
Quote
and I updated some drivers
what kind of drivers?
Quote
I did try uninstalling the drivers but it still won't detect the network card. I also tried disconnecting and reconnecting the network card (and I cleaned the port for good measure).
have you tried to load last good known configuration or the last windows restore point?
or to reinstall OS?

Kernel panic / Internet access with a bad AirPort card

My iBook G4 started suffering kernel panics just over a week ago. They have rapidly increased in frequency to the extent that it can take several attempts to boot up because they have started occurring during the boot up process (originally they occurred after the iBook had been on for a while).
I've looked through the forum and have seen that there seem to be some common causes -RAM, AirPort card, or something to do with the HD. I ran disk utility on the HD and it didn't find any problems and I also successfully ran the 'repair disk permissions'. I have tried taking out the RAM -that didn't do anything. The kernel panic does frequently occur when I am either using Mail or Safari, but as I've said, it also occurs when I'm booting up -does the fact that it happens when I boot up mean that it cannot be the AirPort card (which incidentally is not under the keyboard -so it must be inside)?
Earlier today I switched off AirPort and was able to work on the computer for almost three hours without any kernel panic (but also without internet access). Less than a minute after switching it back on, it froze again.
If this does mean that the problem is with the AirPort card, I have a question about internet access. I use the iBook on a wireless network that stems from a modem with a Mac downstairs and I do not have any internet cables, or a phone line, in the room where the iBook is used. Is it possible to use something like AirPort Express even with a bad AirPort card? And does AirPort Express connect to the iBook, or to the main modem downstairs?
Apologies for so many questions and many thanks for any help you are able to give -this has been driving me around the bend for the past week?

Update:
An acquaintance who works for Apple suggested that before assuming that the problem was the AirPort card / buying further equipment, I should boot up with the original installation disk in and use the disk utility function to 'repair disk'. I did that and got a 'Volume Header needs minor repair' message. It repaired that & I restarted the iBook. I was able to do an update back-up to my external hard drive & all was fine until I switched AirPort back on -there was an instant kernel panic.
I figured that it couldn't hurt to run the Apple Hardware Test -did that and restarted again. Was able to open Mail (AirPort was on) but then the AirPort connection disappeared and the pointer froze, but there was no kernel panic screen. I had to force quit -restarted again. This time I was able to use Mail, downloaded a song on iTunes, and was on the internet for about 45mins before the connection disappeared and the pointer froze again. I could force quit the app but with a frozen pointer I ended up having to force quit again.
I waited a while and then booted up again (without problem) but this time I was told that there was no Airport card present! Shut down and reran the Hardware Test (which said that AirPort 'Passed'). When I restarted AirPort was briefly there but disappeared when I opened AirPort Utility and at this point the pointer also froze. I did force quit to get out of the app and then there was a kernel panic. Is this now pretty conclusive that the AirPort card is the problem?
I would appreciate any feedback -I've had a very frustrating week with this.
Thanks.

KA780G second network card doesn't work

Hi everybody,
Today, I put an second network card on the KA780G board (it's for a round robin network), on a free PCI slot, and this card isn't recognised by Linux and Windows (in Windows XP, when the network card is connected, my graphical card works bad as well).
I tested this network card in another computer and it's working well, I try with another type of network card and it's not working.
I upgraded the BIOS with the latest release and reset the bios parameters but it doesn't work.
Do I need to put some specifics parameters in the BIOS ?
Someone as an idea ?
Thanks
Matt

As you want... but I know the truth
Transfert a file takes me twice the time when the second network card was unpluged (the test was made with two differents files with the same size, this is for keeping disk caching speeding the transfert).
I think, your're not understanding, so let me explain the achitecture of my network : two computers pluged to my "super magic switch" (each with one network card) and my NAS with two round robin's network card.
I transfert one file from the NAS to the first computer and at the same time another file from the NAS to the second computer. The network speed was (on the NAS) about 24MB/s (see with the system monitor).
If you're right explain me why many people using port trunking with their switches ?
Matt.

?? configure network-cards under Sol. 8 ?? please heeellpplp

Hi,
I'm a stand alone Solaris's user (at home). Since about 2 months I've installed Solaris 8 on my PC, and wont be able to configure my Internet-Connection and my privat Home-Network.
I'd already read about 500 different publication's pages, but wont be able to go any further. My main PC contain Solaris 8 and has two RTL-Network-Cards. One for the Internet Connection(LAN), and the other (interne hub) for my small privat network at home. I've read there should be two files named: /etc/hostname.XXX0, XXX1. But there arent such files to see by me. The only file I have is "/dev/hostname.". I've tried to create them and lunch some commands I've seen in some manual's page.
Result ===> some error messages by the boot sequence.
Please can anyone help? Without having these cards working, I can't have any Internet connection.
The OS (Solaris) is already working on my PC, and I love it. But the only problem is how to set up these damned hardware, Network-Cards, Sound-Card and. I don't really know how to start with.
Please help!! Dont want to give up and I will not! Please help me to enjoy that hard work.
Thanks for helping.
PS: I'm connected to the internet trought Network (LAN), i.e I'm using a RTL 8029 PCI Ethernet network-card, and the interne Hub is also a RTL 8029 PCI Ethernet card.

yes. you got it .... eg..
/etc/hostname.le0
/etc/hostname.le1
in here put the hostname ... so at the shell prompt:
# hostname <cr>
should give your hostname.
now, in the hosts file: eg:
# Internet host table
127.0.0.1 localhost
<your ip address> <your hostname> loghost
129.156.89.252 host2
you need to reboot after this.
if you get a 'bad address' error on boot,
you probably have a mismatch of hostnames/ip addresses somewhere in their respective files.
also, see:
# man hosts
# man ifconfig

Network card: e1000g (Intel PRO/1000 MT) did not working properly

Hi to everyone!
I'm having some strange trouble.
All computers attached to one DLink gigabit switch
Server #1:
nf4-based motherboard, Intel PRO/1000 MT net card, onboard net card (forcedeth driver used) Ubuntu Linux 2.6.25 kernel version.
All just working.
Server #2:
nf6-based motherboard, same Intel net card, SunOS 5.11 snv_86.
All just working.
Server #3:
Same as server's #1 nf4-based motherboard. Same onboard card. Same SunOS 5.11 snv_86 as server #2 have installed.
Its work. BUT..
Intel card is not working as expected.
It is seen by system. It is properly up and running. It is sending packent and receiving packets. Ierrs=Oerrs=Collis=Queue=0.
But thru e1000g0 interface no one computer can reach this one, and from server #3 no one computer is seen thru e1000g0. Exept...
Except two old Sunray1 devices (attached to the same switch for testing purposes)! But even these devices seen only by arp requests, and is not pingable.
It is some mistery, but if I turn on jubmo frames, these rays got a picture from SRSS, testing on this sevrer! Not for long, heh, they hung up fast, but this is proof a physical connection :)
So, I can not disable onboard network card on Server #3 - server becoming unreachable :(
I know, those network cards must work on Solaris - as they did it on server #2. I know, those network cards work with my nf4-based motherboards - as they did it on server #1.
But I can't uderstand, whait is going on with e1000g driver on server #3!
P.S. Kernel driver e1000g settings are the same. All difference from servers #2 and #3 is: #2 had Intel netcard installed then Solaris was setting up, and #3 had Intel netcard installed later. All netcards are working (I trying to swap them from one computer to another - did not change anything).

*) #3 thinks it is sending, but a NIC/driver error prevents it.NIC is fully health. It is tested on another PC. Driver error - or driver's bad implementation - is the one I'm thinking.
*) #3 has a bad transmit pair of wires (would affect all communication)This patchcord works w/o problems on other PCs and even on onboard NIC of server #3.
*) Network problemsHeh :)
*) Firewall or other device is dropping the ARP repliesIt is some very stealthy and very selective firewall, affecting only external NICs :)
BTW, then cord is attached to NIC, it sends "who has this IP" requests, asking to be shure there will not be an IP conflict. No one seen this requests.
*) #1 has a NIC/driver error preventing it from seeing the reply.Only for send from #3? It is like a firewall on #3 :) And, there is more PCs, not only #1-#3. No one can see #3's replays (or asks), not only #1..
I'm repeating: this PC works in network now on onboard NIC w/o problems. But onboard NIC is only 100 Mb/s, and we need 1 Gb/s.
I was thinking, Solaris took wrong MAC for NICs - but not, ifconfig shows the same MACs as marked on NICs.
Even more, yesterday i plumbed e1000g1 - second Intel NIC in server #3. And I was surprised - it worked perfectly!
But I make "touch /reconfigure; init 6" - and after reboot, no one of two Intel NICs working again :( They both have the same behavior - no one can see packets they sends.)
I even try to restrict connection on 100 Mb/s by driver's .conf modify - it works, link become yellow instead of green (take a note, NIC is able to "speak" properly with switch!), but all other stay the same.
Strange, really strange behavior. More strange is a fact this NICs work on another instance of same SunOS, but on different motherboard, while the same MB with same NIC is working w/o problems under Ubuntu. Looks like some bug in Solaris driver.

How to specify 2nd network card to TCP open and write?

TCP-Open does not have an option to choose which network card to use. It only has an open to connection but not an open from connection to enter. Is there anyway to select the second network card instead of letting the computer to choose?

pwrdesoto wrote:
Only the TCP-Listen allows the user to choose which network adapter to listen. The TCP-Open is require to open an connection to write to and it only has an input on where to connect to but not which network adapter to connect from.
tst is completely right. If you have two network cards they usually have different subnets that should not overlap. If the desired target adress belongs to one of those subnets the TCP/IP routing will automatically select the correct network card to bind the connection to. If you use an address outside of those subnets the default gateway will be selected.
And according to a Microsoft knowledgebase article it is a very bad idea to have more than one default gateway defined in the entire setup. If you do that the default gateway of the default (primary adapter) should be selected automatically but the routing can get really weird sometimes.
If this is not enough for your routing requirements you will have to manipulate the routing tables manually (and no it is no pretty business to do so). Look at http://support.microsoft.com/kb/140859 for a starting point about routing table manipulations under Windows NT (still applicable to XP) based systems.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

WRT54G Extremely slow navigating pages @ 192.168.1.1 - Could this be a network card problem?

Friend of mine is having Internet connection issues on his main PC which is hard wired to the router, He's using Comcast cable (18Mbit) and all of a sudden today the speed dropped to dialup speeds, literally, however its ONLY this main pc with the speed issue, there are 2 other computers connected wireless to the router and they are running full speed when testing on speedtest.net
While troubleshooting the problem I tried bypassing the router and the speed issue still remains, So I can pretty much rule out the router, But as part of my troubleshooting whenever I try to access the router's configuration pages via 192.168.1.1 it is VERY slow at responding.
For example when hitting enter after typing 192.168.1.1 it takes around 45 seconds to display the router configuration page, and at that point clicking on any other tabs takes 30 - 45 seconds as well to respond.
So my main question with this post is, is it possible his network card went bad? What would cause really slow access to the router configuration?
The PC is running Win 7 Ultimate 32bit and Ive tried running the network troubleshooter, uninstalled his network card in device manager / reinstalled the drivers but nothing seems to be working.
I also ran Malware Bytes and scan results were clean.
Any ideas appreciated!
Solved!
Go to Solution.

can you "borrow" a card? its the only way to be sure, eliminating hours of trial and error procedures. one of the mega electronics stores is a good source, if it solves your problem you keep the card, if not there is the return option
ps. i am not a tech, i just play one on tv!
pps. free speech is a human right! join Reporters Without Borders (http://en.rsf.org/) and help save the planet from censorship predators!

Edge E530 network card - 'no link'

Hello,
My Thinkpad edge of nearly 2 years has as of today stopped showing a carrier signal on it's network port.
This follows constant use under Slackware 14 since purchase (have tested with stock OS and knoppix). The first sign of trouble was in april this year when plugging in to a specific client network caused the transfer speed to slow to a permanent crawl after dhcp, and may have been triggered by plugging in to a bad wall socket at another site today.
Anyone had luck replacing them, are they too much hassle, and is there a good usb network card that could do the trick?
Shame to lose it, really liked these - and bought them for clients too.

Does the order in which you boot up the VMs have any impact on which one can reach the internet?
Such as; the first one that boots always gets out, no matter the VM.
This would point to a MAC limiting feature on your physical switch.
The other is, since you have teamed NICs, do both have active connections.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.

Bad wifi card macbook?

I use a late 2008 MacBook. My wireless internet connection seems to time out and slow dramatically from time to time. If I turn the airport off and then back on, it seems to get it going again. I use ATT U-verse and our connection is typically extremely fast but lately the speed has been intermittent and won't load webpages. However, when I connect my computer directly to the router via ethernet cable, the speed is constant and the problem goes away. Is this a sign of a bad wifi card?

Not necessarily...if the card failed, you'd most likely not be able to use it at all. Which protocol are you using to connect? It may be useful to delete the current network 'location' and recreate to see if that helps.

Installing new network card...how?

The built in ethernet on my computer does not appear to be working. How do I get the Mac to see a new network card once i plug it into the board? Same for a sound card. I know that the built in sound is bad.
I have extensive knowledge of these processes for a PC, but not at all for a Mac. A PC will automatically detect new hardware, but the Mac doesn't appear to see it.
Thanks for any help.

The built in ethernet on my computer does not appear
to be working. How do I get the Mac to see a new
network card once i plug it into the board? Same for
a sound card.
There aren't a lot of PCI Ethernet cards supported natively in OS X, and even then those that are usually still need a driver installed for them to function. D-Link is the only one I know off-hand that markets a 10/100 card billed as Mac-compatible. A Mac-compatible generic sound card will be even harder to track down.. the only ones I know of are very expensive ones aimed at digital audio production.
-Douggo

Windows sharing with two network cards

Hello,
I am running OSX 10.4.11 and enables Windows file service.
I have two network cards. one is public (due to the web server) and one is private (192.x.x.x).
Is there a way to make only the 192.x.x.x accessible via the Windows file services? I don't want anyone that is a local user to be able to get to any of the shared folders via the public address. Like if they were at home or something.
Hope this makes sense.
Thanks,
Jay

Hello Jay,
Your question does make sense!
And in fact Samba (the software that delivers the Windows file service on a Mac) has configuration options to do just what you want. That's the good news. The bad news is that I don't know a way to set those configuration options from the GUI. If you are confident to use a terminal and edit configuration files by hand then you should be able to establish the Windows file service running on just one interface.
First you need to find out the real name of the interface on which the Windows file service should run. One way is to look under Apple\About this Mac\Network or in a terminal enter:
ifconfig
My Mac Mini has en0 (wired) and en1 (airport) as network interfaces. Suppose en1 is the interface on which file sharing is wanted (you should replace en1 in my example by the name of your network interface!)
Next edit the file /etc/smb.conf in a terminal by:
sudo nano /etc/smb.conf
In the [global] section add the following lines:
interfaces = en1
bind interfaces only = true
Save your edits by pressing Ctrl-O and exit the editor by pressing Ctrl-X
After restarting you can check if it works as expected.
Good luck,
Max

Teamed network cards for domain controllers?

can someone help me to resolve a debate we have: my colleage states that domain controllers (in our case Win2003SP2) should "not" have their network cards teamed for high availability (via HP's NIC teaming software).? I've not heard of this and cannot Bing/Google anything like this. I'm under the impression that a domain controller "should" have it's gigabit NICs teamed to make sure that directory services are highly available.
any information on this would be great. thanks...Peter A. Berger Jr.

Fault Tolerance and Network Teaming
                Anyone who has called Microsoft for help with a networking problem has likely heard the question: "Are you using network teaming?" I have often heard this referred to by Microsoft's customers as a "quick out" or an excuse that Microsoft was looking to pass the responsibility on to someone else. As someone that has been on both ends of the phone, and at the highest escalation point within Microsoft's Network queues I can tell you that it is a question born of wisdom and tempered with experience. While working the phones at Microsoft, supporting the largest and most critical systems in the US it was rare to ever get a call about the same problem more than once. Even more rare was for everyone on our group to get the same calls, and have the same experiences. I recall it happening when we fought the blaster worm, and when Microsoft's "Scalable Networking Pack" was released with 2003 SP2. These were bad, but a few months went by and except for a few straggles the phone calls stopped, the world got wise to the issue and the problem was resolved. I was amazed though to experience 1-3 calls a week with network issues CAUSED by network teaming. I could not help but be blown away by the irony of a program meant to avoid network failure so often causing it. I talked to colleagues, (of which I have found no better single source in the industry than at Microsoft), and found that even the old timers having more than 15 years with the company had the same stories of problems caused by networking teaming as we are constantly experiencing today. I am amazed that an industry as wise and agile as the computer industry has been (and is), has stuck with such a poor technology. I always asked my customers as the called with problems, usually critical ones, "What is teaming these network cards getting you". Almost unanimously the answer would come fault tolerance, to which I would reply rhetorically "How often do you NICs or Switches fail and how often has teaming caused network failure?" In my opinion, it is unforgivable for an application to constantly cause the problem that it is written to avoid. It should cause pause and reflection as to whether the technology is well suited for its function, whether it is just written poorly or if all of its implementations have similar problems. Technology today is beyond network teaming. There are far better methods of providing fault tolerance with manual and automatic failover. Most application writers have taken into consideration fault tolerance at the service level superseding anything that network teaming offers, so that network teaming should be a dead technology, because it is killing us.
                Finally, if you are considering using network teaming, or have had reason to reconsider its use, maybe these questions will help your assessment:
                What is my goal with using network teaming?
                Can I gain Availability through use of a more capable NIC card?
                How often have my NIC cards failed?
                When NIC cards have failed were they the only failure, or was it in conjunction with a Motherboard or other failure causing the service to be unavailable?
                What are my needs for uptime for these services?
                Would a manual failover (the simplest of options) be viable for this service?
                What options for automatic failover do I have (since most applications can have multiple providers through configuration)?
                One other note to add. While working on the phones at Microsoft, and later as a consultant to large and federal organizations, I found one thing that seemed to be true most of the time. When a problem occurred, it was rarely the OS itself, but something unnatural to its processes. Simplicity and minimalism is really one of the keys to a healthy server and environment. Often it is necessary to introduce other applications and services, but I do not think near as often as we do.
Note: MSFT does not support network teaming, because they do not own the software that provides it. In certain instances though, like with OCS, they flat out will not support OCS if teaming is enabled on the server.
Note2: I realize my comments above are very general, and so I want to apply these to this exact question. When I consider AD and how to make it fault tolerant, I cannot help but realize that the protocols, clients and services that make up Directory Services, are beautifully fault tolerant. In most cases, the loss of any one DC would not greatly affect the user's ability to authenticate to a computer or service within the domain. Even more, Directory services is inherently so fault tolerant that it can still function with the loss of a major part of the servers that make it up.
Don't forget to give credit where credit is due, vote this as helpful if it helped you.

VIA KT400 Network Card Problems!

I've read allot about the problems I've been having and done many searches on Google and it all seems to come down to this: ALL VIA Motherboards in the KT400 series(and many other chipsets) lock up when using ANY Wireless Card\Usb Adapter. The frusterating part is nobody seems to have a clear answer on how to fix this or if it's even fixable
The forum linked down below tries to claim this only happens with Linksys cards.. This is false as I have a Microsoft Wireless G USB adapter and the EXACT SAME thing happens to me.
The strange part is if you are just browsing the web and reading text, everything works 100% fine. But as soon as you do something that uses DirectX or 3D Acceleration, like say Streaming Videos.. it freezes with the mouse curser just sitting there and I must hard reset the system.
Does anyone out there know of ANY kind of fix? I'm dying to know.
You can view someone elses post referring to the exact problem I have in the VIA Arena Forum
AMD Athlon XP 2500+ @ 2.00 Ghz
512 MB Ram
GeForceMX 5900XT
Antec 420 Watt Power Supply
Windows XP SP2
Latest VIA Hyperion Drivers

Hey guys it's me again.. Well the computer now seems to freeze less than it did before, but it still freezes.
After all this going back and forth and troubleshooting hassle ive decided it has to unfortunatlely be a hardware problem. I've stated before that it only freezed when running a 3d app and network card running.. but now it freezes even when I'm just on the web. It's just so totally random, sometimes it will freeze twice in one minute and sometimes it won't freeze for almost a whole day.
I've narrowed it down to 3 things: Bad HD, Bad Processor, and worst of all Bad Motherboard. Another possibility, does a the lithium battery on the motherboard ever cause problems if it's almost dead?(Assuming it's the CMOS battery?) And could that cause problems?
I had an episode before that I didn't tell you guys before. This was still after i had the network card, but probably unrelated. The computer once or twice made a very strange electrical zapping noise or screetching noise before and the whole system would almost fail and then try to resume again, and then just shut down.
After this event happened I figured it was the PSU not putting out enough power as I had installed new hardware lately. I bought a new 430W psu and while I haven't had the strange problem I had before, I still get random lockups.
I'm pretty sure it is the harddive, because it would make sense since I heard this noise before and the fact that it just freezes could just be the HD getting stuck and not spinning anymore.
It's funny because I had just replaced a faulty harddrive before in one of my older computers. However that one was much more obvious as it would constantly have to repair files in sectors. The HD I have now never comes up with errors, but maybe It is running fine before it decides to lockup.
Yet another thing it could be is the processor maybe just not generating enough juice to keep the processes going or something.
I did have problems with freezing before the network adapter now that I think back, but they were far and few between and now the problems are more pronounced. I'm going to hope it just the HD, if not it's really going to suck to already have to buy another motherboard or processor. I just built the system from scratch last year.
Sigh, Oh well. Glad for anymore insight on this issue and your opinions on what is most likely the problem. I'm going to go looking for a HD in the mean time.

Bad network card

Similar Messages

Maybe you are looking for