[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 301
  • Last Modified:

Network problems using NForce3 150 chipset

Hi,

I recently build a new computer using the NForce3 150 chipset, and installed Linux Mandrake 10 Community on it. After seemingly configuring the NIC correctly (I use DHCP to lease an IP from a server, running MDK 9.1), I failed to be able to receive an IP. I therefore specified a static IP, but was unable to ping any of the other nodes on the network.

Thinking that there was probably a problem with the NIC I installed another PCI NIC which uses the tulip driver, and that I know to have worked on previous versions of Mandrake. This did exactly the same thing. The cable used to connect has been used previously by my laptop and so isn't damaged. The same happened when I connected it directly to the server with a crossover cable.

I then ran Knoppix on the machine to see whether this could just be a software problem, but again I was unable to receive a DHCP lease, or ping anything with a static IP.

I am about to install Windows on a partition to see if it will work, however I know the tupip driver to work with the PCI NIC, and so am not particularly hopeful that it's just a driver problem. The other nodes on the network all receive leases.

Any suggestions will be gratefully received :)

Adam
0
asbfraser
Asked:
asbfraser
  • 9
  • 9
1 Solution
 
pseudocyberCommented:
Try pinging 127.0.0.1 to test the tcp/ip stack.  If that works, try pinging itself to test the NIC - you have to assign an address first.  You should be able to ping itself without a cable plugged in and it should work - if not, problem with NIC.
0
 
asbfraserAuthor Commented:
Thanks for replying so quickly. I've successfully pinged both 127.0.0.1 and the static IP I set. Does this mean that the NIC is ok? I still can't ping any other nodes on the network.

Adam
0
 
pseudocyberCommented:
Check the subnet mask - make sure it's exactly the same as other hosts on the network.

What does your route table look like?  Any weird routes?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
asbfraserAuthor Commented:
I'm fairly sure the subnet mask is the same, but I'll double-check that. Would having the wrong netmask cause this problem?

The packets don't get any further than the IP I've set for the box - I can't ping any other nodes and there are no routes out of it. It's all very strange...

Adam
0
 
asbfraserAuthor Commented:
OK, just checked again - the netmask is the same across the network, and with the new box - 255.255.255.0

Adam
0
 
pseudocyberCommented:
Do you have any firewall software running on the box - if so, turn it off.
0
 
asbfraserAuthor Commented:
Yeah, I've turned off the firewall, although the NIC I'm using is on eth0 which should be allowed through anyway.
0
 
pseudocyberCommented:
Did you say you have NO routes on your box?  You need at least a default route, probably a route to the loopback, and one for multicast.  I'm on an XP box and mine looks like this (no manually config'd routes):

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0              x.x.x.129           x.x.x.239      20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
  x.x.x.128  255.255.255.128           x.x.x.239        x.x.x.239      20
  x.x.x.239  255.255.255.255        127.0.0.1       127.0.0.1       20
  x.x.x.255  255.255.255.255          x.x.x.239        x.x.x.239      20
        224.0.0.0        240.0.0.0         x.x.x.239  x.x.x.239      20
  255.255.255.255  255.255.255.255  x.x.x.239               3       1
  255.255.255.255  255.255.255.255  x.x.x.239  x.x.x.239      1
Default Gateway:   x.x.x.129
0
 
asbfraserAuthor Commented:
Sorry, I meant I couldn't trace any external routes.

I have a loopback to localhost configured, as is standard. The gateway and metric is the same for each interface, as is the netmask.

Adam
0
 
pseudocyberCommented:
Any chance of using a protocol analyzer to look at the traffic?  Or can you use "snoop" on it.
0
 
pseudocyberCommented:
Any chance of using a protocol analyzer to look at the traffic?  Or can you use "snoop" on it.
0
 
asbfraserAuthor Commented:
Yeah, I've had a look with ethereal - there's no traffic at all. Basically it's exactly as if the network cable wasn't plugged in. And yes, it is :)
0
 
pseudocyberCommented:
Well, I'm a total Linux NuB - so I can't really help going at it from a hardware OS perspective.  But it sounds like a hardware issue - maybe mobo?
0
 
pseudocyberCommented:
Take a known good working machine - totally different one - and connect it to that cable - that will eliminate everything from the cable onward.
0
 
asbfraserAuthor Commented:
Yeah, it's the same cable that my laptop usually connects on, and it never has a problem.

I appreciate your help - do you think that it could be a mobo problem, bearing in mind that neither an onboard NIC or a PCI NIC work? This is what I've been thinking is most likely, as I don't think the nforce3 chipset gets on too well with linux. I'll get round to putting windows on and see how it does.

Adam
0
 
pseudocyberCommented:
It's about all I can think of.  Do you have any support on the mobo?  Is it new?
0
 
asbfraserAuthor Commented:
Ok, I've just installed Windows and it works fine. I think the main problem is that the nforce3 chipset doesn't play well with linux, and there don't appear to be any drivers out that work with the 2.6 kernel. I suspect that I probably need a driver for the PCI bus, as neither NIC would work.

Thanks for your help,

Adam
0
 
asbfraserAuthor Commented:
Ok, just for anyone else with the same problem - I downloaded and installed Linux Mandrake 10.0beta AMD64, and everything now works perfectly. Obviously all the relevant drivers etc are including in this distribution, as there are currently only a few chipsets for Athlon 64.

Adam
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 9
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now