Guigsy Posted May 18, 2009 Share Posted May 18, 2009 So its pc to pc. no hub/switch or anything? oh i just read the one line i missed before in your origonal post... your useing the right cable No wonder. I was thinking as i was reading "how come nobody has said your useing the wrong cable yet" Ill get my coat Quote Link to comment Share on other sites More sharing options...
Pixelfill Posted May 19, 2009 Author Share Posted May 19, 2009 So its pc to pc. no hub/switch or anything? oh i just read the one line i missed before in your origonal post... your useing the right cable No wonder. I was thinking as i was reading "how come nobody has said your useing the wrong cable yet" Ill get my coat Thanks for that , I hadn't appreciated there might be a different crossover cable for gigabit One quick question though, if I dropped to 100Mbps would it still need the gigabit crossover, or would a standard crossover "work" - 'cos it didn't yesterday at 100Mbps. Mike Quote Link to comment Share on other sites More sharing options...
MaveriK Posted May 19, 2009 Share Posted May 19, 2009 Although Autoneg seems likes a thing of beauty it can be a real pain in the behind and i much prefer hard setting speed/duplex on both nic and switch. I have had 2 cards in my long IT career that have just played up for no reason whatsoever and it sounds like you may have another. To test i would put a hub or preferably a switch in the middle and start at 10/half hard coded at all sides and work up from there, making sure only to move move sides speed at a time. If that fails i would go for another nic, from another vendor in another pci slot. Good luck! Quote Link to comment Share on other sites More sharing options...
Pixelfill Posted May 19, 2009 Author Share Posted May 19, 2009 Although Autoneg seems likes a thing of beauty it can be a real pain in the behind and i much prefer hard setting speed/duplex on both nic and switch. I have had 2 cards in my long IT career that have just played up for no reason whatsoever and it sounds like you may have another. To test i would put a hub or preferably a switch in the middle and start at 10/half hard coded at all sides and work up from there, making sure only to move move sides speed at a time. If that fails i would go for another nic, from another vendor in another pci slot. Good luck! I would love to go for another NIC in another PCI slot, unfortunately the NICs in question are built onto a single board computer. I tried an Intel NIC on the PCI backplane today and unfortunately it as "unable to get the interrupt it wanted" so I got the dreaded Exclamation mark in Device Manager. I wasted another day today, and am no further. I tried a gigabit crossover cable with no succes, and I was convinced that should have fixed it. I'm tempted to try a Windows Repair / Reinstall tosee if that fixes it b ut banging my head against a brick wall at the moment. Mike Quote Link to comment Share on other sites More sharing options...
Guest Dizzmystar Posted May 19, 2009 Share Posted May 19, 2009 are both in the same workgroup and is IP Forwarding enabled? Quote Link to comment Share on other sites More sharing options...
kill1308 Posted May 19, 2009 Share Posted May 19, 2009 I'm sure you've tried all the below, but will write it all down anyway.... just thinking out loud really. So have you tried fixing link speed/duplex at both sides to 100/FullDuplex yet with your crossover cable yet? If so what was the result... are packets being sent/received? Failing that, set it to 10mbit/Half at both sides as someone suggested earlier, this will work even in a harsh environment, I think if you've gone through the obvious settings, checked cables then all that is really left is an auto-negotiation issue. This really shouldn't be causing much trouble, as you know it's real simple, I'm sure you've checked everything's the same as below... but just for clarity's sake. (Disable any software firewalls (including windows firewall)) Test 1 ===== PC---IP Address-----Subnet Mask----Link Speed/Duplex ========================================== PC1. 192.168.1.10 - 255.255.255.0 - 100mbit/Full Duplex PC2. 192.168.1.11 - 255.255.255.0 - 100mbit/Full Duplex Test 2 ===== PC---IP Address-----Subnet Mask----Link Speed/Duplex ========================================== PC1. 192.168.1.10 - 255.255.255.0 - 10mbit/Half Duplex PC2. 192.168.1.11 - 255.255.255.0 - 10mbit/Half Duplex When you do "ipconfig /all" at the command prompt, I assume that you get the same IP parameters that you entered manually? If you do an 'arp -a' from the command prompt do the entries in there correspond with the MAC address of each machine? If you do 'arp -d ipaddress' for the entries that exist in there and then try and ping again, what happens? You've tried different cables so it's definately not that..... - I assume you've got nothing entered in the 'Gateway' box and no WINS/DNS entries configured. Probably not, but worth checking. Disabled all other network adapters (physical and virtual) on your computer as well whilst performing the tests. Man this is really wierd, peer-to-peer networking is such a simple procedure. If for some strange reason you still can't get it working, I've got a spare Netgear 10/100 managed switch (or an unmanaged one if you prefer) I can send you if you like? I know you wanted Gbit but it might do in the short term? (Thinking about the managed switch might have a few gbit links, I'd have to check) Edit - sorry if you think I'm doubting your knowledge at all in my post I'm not, didn't want to come across as 'know-it-all-e' lol you've tried most of the things I'd have tried, just re-read your post and the wireshark results are strange. Best of luck anyway, if in doubt chuck em out the Window. Quote Link to comment Share on other sites More sharing options...
Pete Posted May 19, 2009 Share Posted May 19, 2009 Still not working? Format, reinstall with FreeBSD. Quote Link to comment Share on other sites More sharing options...
Pixelfill Posted May 27, 2009 Author Share Posted May 27, 2009 For anyone who is interested, I eventually solved this (well actually worked around it is a better description). The problem in a nutshell - IRQ sharing ! Windows was not reporting any conflicts at all (well it won't as IRQ sharing is not normally a problem, except for Network cards where it can be an issue). I ended up removing all PCI cards, and reinstalling Windows, where the onboard network ports both functioned correctly. Installing one PCI card at a time and checking the ports were still working. When I installed the third PCI card, one of the network cards stopped "receiving", move the PCI card to the next slot, the other Network card stopped "receiving", moved again both worked. Out of my 12 port PCI backplane at least 4 slots caused an IRQ clash where the network cards stopped working. Thanks to everyone for your time and assistance, and I hope to God I never experience anything as infuriating again. I'm now working with the Single Board Computer manufacturer to see if we can amend the PCI steering in the BIOS to avoid this issue in future. PnP Operating System ... My ASS Mike Quote Link to comment Share on other sites More sharing options...
JustGav Posted May 27, 2009 Share Posted May 27, 2009 For anyone who is interested, I eventually solved this (well actually worked around it is a better description). The problem in a nutshell - IRQ sharing ! Windows was not reporting any conflicts at all (well it won't as IRQ sharing is not normally a problem, except for Network cards where it can be an issue). I ended up removing all PCI cards, and reinstalling Windows, where the onboard network ports both functioned correctly. Installing one PCI card at a time and checking the ports were still working. When I installed the third PCI card, one of the network cards stopped "receiving", move the PCI card to the next slot, the other Network card stopped "receiving", moved again both worked. Out of my 12 port PCI backplane at least 4 slots caused an IRQ clash where the network cards stopped working. Thanks to everyone for your time and assistance, and I hope to God I never experience anything as infuriating again. I'm now working with the Single Board Computer manufacturer to see if we can amend the PCI steering in the BIOS to avoid this issue in future. PnP Operating System ... My ASS Mike Good to hear it is solved, wouldn't have expected that. Quote Link to comment Share on other sites More sharing options...
kill1308 Posted May 27, 2009 Share Posted May 27, 2009 Glad you got it sorted To be honest I'd have never thought of that as had assumed the cards were working correctly. I hate pain in the ass problems like that, bet you're happy it's now sorted. Quote Link to comment Share on other sites More sharing options...
Wez Posted May 27, 2009 Share Posted May 27, 2009 What a PITA, good job fixing it Quote Link to comment Share on other sites More sharing options...
Pete Posted May 28, 2009 Share Posted May 28, 2009 Ah, back to the good old days of DOS when it was an art to build a computer. Quote Link to comment Share on other sites More sharing options...
MarkR Posted May 28, 2009 Share Posted May 28, 2009 Sweet mother of creation. What a nightmare. Good job solving it. I was racking my brains but everyone suggested what I was thinking anyway. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.