Intel gigabit nic corrupting downloads

[Dorkenstein]

I used this intel gigabit pci-express nic on my last install of windows with no trouble, everything worked just as it should have. So I re-install windows and then images on web sites will be half-developed, miscolored and corrupted. Also none of my downloads will open properly because of bad checksums. So I am using my on-board realtek nic and everything works fine but I want to use the gigabit nic I paid for. Any ideas how to fix this? Thanks very much.

 

[spidey07]

download latest drivers and try disabling tcp offloading in the NIC drivers properties. Also leave speed/duplex set to auto. Make sure your MTU is 1500 for ethernet.

 

[Dorkenstein]

I am using the most recent drivers, I am trying the other things you mention right now.

 

[jlazzaro]

since you're already on the latest drivers, try going back a few revisions...

 

[Dorkenstein]

Hmm now I am getting intermittent loss of connection. It will appear to die on me for a few minutes and then come back.

 

[RebateMonger]

Have you run Intel's NIC diagnostics?

Warranty replacement form for Intel network adapters.

 

[Fullmetal Chocobo]

Just a thought, but it's an easy thing to do. Download MemTest and run it for a bit to check your memory in the machine as well.
<- recently had RAM issues.

 

[Dorkenstein]

I ran the built-in diagnostic that comes with the drivers but everything passes. The only thing I don't have is a WINS server or something. The only problem now is that the connection eventually dies and I need to reset it.

 

[spidey07]

Next step would be to replace the cable with a good store bought one. Just because it works on the other nic doesn't mean it's good.

 

[RebateMonger]

Originally posted by: spidey07
Next step would be to replace the cable with a good store bought one. Just because it works on the other nic doesn't mean it's good.

Very true. I always assume that nobody's crazy enough to still be using home-made cables in this day of $2 cables.

 

[spidey07]

Originally posted by: RebateMonger

Originally posted by: spidey07
Next step would be to replace the cable with a good store bought one. Just because it works on the other nic doesn't mean it's good.

Very true. I always assume that nobody's crazy enough to still be using home-made cables in this day of $2 cables.

DON'T MUCK WITH THE PHYSICAL LAYER!!!!

and by muck I mean duck.

 

[Dorkenstein]

I bought my cables from monoprice

 

[cmetz]

Dorkenstein, look for any TCP offload options in the device manager hardware config for the NIC and try disabling them. Also try forcing the link speed to a lower speed (1000 -> 100, or 100 -> 10) and see if that helps.

 

[RebateMonger]

I'd put the "questionable" Intel NIC in another slot. If that doesn't work, then put it in another PC and see if it works there. If it works in another PC and not in this one, then you have a mystery.

 

[Dorkenstein]

Well here's the thing, I ran the diagnostics and it keeps saying signal is good but the quality of the cable is very bad. Possible defect or bad connector. However, it has given me that same result for 3 different cables. Each time the source of the problem is at 2 to 4 meters. I am using a wireless bridge to get ethernet upstairs, I didn't want to drill through the floor. I have the bridge going into a gigabit switch. Which part is the problem, how can I rectify it and is there a better way for my setup? Thanks for all the responses so far.

EDIT: My lan monitoring widget says I have 2 'Out Errors' also.

 

[RebateMonger]

Uh...you didn't mention wireless. Where is the wireless link with respect to the PC you are working on and the rest of the network?

 

[jaqie]

Originally posted by: RebateMonger
Very true. I always assume that nobody's crazy enough to still be using home-made cables in this day of $2 cables.

I've been making cables for many years, and I find through the QC/diagnostics always show them as extremely or very good. It's all in your skill at making them and the raw material you use. I like belden cable and use it exclusively, for example. No, not belkin, belden.

 

[jaqie]

On topic: the problem with corrupted transfers with a PRO/1000GT happens with me with a single motherboard I have here, as well. As best I can tell, it is the motherboard itself not liking the card. I have three PRO/1000GTs here, and two of the same mobo (biostar 6100-M9), and nomatter what is done, the one just gets all kinds of trash and disconnects just like you are describing with any of the cards, while the other mobo works fine. It's quite possible you have a picky/flaky mobo, but with you talking about wifi in the connection chain, that's quite likely where the problem is rooted.

 

[Dorkenstein]

The Panasonic Wireless bridge goes from the router downstairs and links wirelessly up here. Then it goes to my Gigabit switch and off to the NIC. I am not sure whats causing the problem. It is probably the wireless bridge because all of these cables can't be bad. Any ideas? I am using the Panasonic HD-PLC model.

 

[spidey07]

This still sounds like a possible MTU problem if you're sure cabling isn't it. Also, it isn't unheard of to get bad premade cables...it happens. The "graphics on web pages don't load" give it away - it's a classic sign. That's also a sign of physical layer problems so maybe take the switch out of the mix and connect directly to the workgroup bridge.

Since you're dealing with wireless update all firmware and try. If all else fails set your MTU on the sending and receiving stations to 1300 - that will eliminate any possible MTU problems.

The only other thing I can think of is a problem with the AP and the workgroup bridge and if these modes are indeed supported by both. The larger frame sizes will show problems in this area. Make sure client and server are set to autonegotiate speed/duplex as well.

Post the counters from your intel nic - you should have ZERO checksum errors on a full duplex connection.

 

[Dorkenstein]

How do I post the counter from the intel nic? Also I have MTU set to 1500.

 

[jaqie]

Originally posted by: spidey07
If all else fails set your MTU on the sending and receiving stations to 1300 - that will eliminate any possible MTU problems.

Actually, to check if MTU is a problem, you just have to set a single PC OS to a lower MTU. An easy way to do this is to get a program from dslr.com called DrTCP. The frame size is not increased anywhere in the transmission (except a tiny bit at the DSL modem for PPPoE encapsulation), so this is an easier and more foolproof method to test for MTU errors.

 

[spidey07]

Originally posted by: jaqie

Originally posted by: spidey07
If all else fails set your MTU on the sending and receiving stations to 1300 - that will eliminate any possible MTU problems.

Actually, to check if MTU is a problem, you just have to set a single PC OS to a lower MTU. An easy way to do this is to get a program from dslr.com called DrTCP. The frame size is not increased anywhere in the transmission (except a tiny bit at the DSL modem for PPPoE encapsulation), so this is an easier and more foolproof method to test for MTU errors.

Actually it depends on the protocol and by setting both sender and receiver to 1300 will eliminate that as a possible source. You're TOTALLY off base by saying the frame size is not increased in transmission. I don't feel like lecturing you.

 

[Dorkenstein]

How do I set both sender and receiver to 1300?

 

[Dorkenstein]

I set the MTU to 1300 but nothing really changed. The card passes all diagnostics, its just the "bad cable" issue now which still puzzles me. For a brief time I didn't have the 2 Out errors but it still lost connection on me after extended use. I also feel like setting the MTU to 1300 slowed my transfer speeds down but I could be wrong. Thanks for the continued help.