9NDA3J/+ Networking problems

[ShoCKeD]

I've been having some serious ethernet issues with my second rig (it just recently had its CPU and motherboard replaced). The cables, modem and switch are all in perfect order (and tested on my working computer) so I'm not sure what else it could be.

First I thought it was a faulty motherboard, and RMA'd a 9NDA3J. I replaced it with a 9NDA3+ (the same thing I have in my working rig), only to find the same exact things happen.

I've tried networking it with a switch and connecting it directly to my modem, neither of which work.

From what I can tell, it has problems getting an IP address. I've tried manually setting it, but again, no luck.

With the onboard ethernet, it will say connected, and with a PCI ethernet card it will say something along the lines of "Limited or no connection", and in both cases it will send a couple handful of packets but not receive any.

I've tried updating the BIOS, using latest drivers as well as the provided drivers on the CD, trying the 64-bit version of Windows XP as well as the 32-bit, etc., as well as reinstalling Windows several times. I upgrade my hardware all the time so I've built and rebuilt my computers more times than I can count, and am not doing anything differently here.

I've tried setting the NV LAN Mac Address in BIOS, although in both cases it disables itself right afterwards.

At this point, I have no idea what the problem is. I can only assume the motherboard is having some sort of conflict with another piece of hardware, though everything seems to be in working order.

I'm completely lost. I've already been through hell and back with this computer before replacing its CPU and motherboard (an AXP / A7N8X-X was damaged by UPS, and stupid me was too lazy to go get a claim, and I have no earthly idea why my old s754 3200+ Clawhammer and K8V Deluxe didn't work). Any ideas are more than welcome.

Stats:

Athlon 64 3000+ Venice
EPoX 9NDA3+
1GB (2x512) Corsair XMS PC3200LL
9800 Pro 128
WD 80GB IDE HDD
Antec 450w PSU

[CX23882-19]

Do you have the hardware nVidia firewall enabled?

[ShoCKeD]

Originally Posted by CX23882-19

Do you have the hardware nVidia firewall enabled?

Nope, nor the Windows firewall or any other software firewall.

[danrok]

Problems getting an internal IP or IP from your ISP?

So, you just have a switch, not a router?

[ShoCKeD]

Originally Posted by danrok

Problems getting an internal IP or IP from your ISP?

So, you just have a switch, not a router?

No router. I've been using this switch for a long time and it's worked perfectly, both when I was living in another apartment (no router) and back home (where I did have a router). Getting a router would be no problem at all, but it should at least be able to connect to the internet via my DSL modem when it's connected directly.

Oh, and problems getting an internal IP.

[danrok]

So your modem normally assigns IP addresses?

[ShoCKeD]

Originally Posted by danrok

So your modem normally assigns IP addresses?

I believe so. My main computer works perfectly through either the switch or modem.

If it's a problem with the modem not assigning it an IP address, I'm not sure what to change in its config. It's a Zyxel 645 series.

EDIT: I also don't have a static IP address with my provider. I'd have to pay extra, but would that make any difference?

Any other cable / DSL provider I've ever used had a static IP.

[danrok]

Dynamic IP should work just fine. I use dynamic just fine, a static IP would be expensive for me.

Have you had 2 computers hooked up to that switch and modem before, with both connecting to the net?

On my router, I can access the following screen (might be helpful to you):

[danrok]

What I'm getting at is that you need to have something acting as a DHCP server before IP's can be assigned to multiple machines. It's the DHCP which does this assignment.

[ShoCKeD]

Originally Posted by danrok

Dynamic IP should work just fine. I use dynamic just fine, a static IP would be expensive for me.

Have you had 2 computers hooked up to that switch and modem before, with both connecting to the net?

On my router, I can access the following screen (might be helpful to you):

Last time I had both computers working without any problems was while I was living in an apartment in Washington State back in November of last year, but my second rig had almost a completely different setup back then (AXP 2400+ T-Bred B, A7N8X-X, 2x256 Corsair XMS PC3200C2, 9500 Pro...). In fact, I think the only thing that is still the same is the case, PSU and HDD. (EDIT: Although, I forgot to mention. I've only been in this apartment about three weeks so this modem has never had two computers successfully hooked up to it - sadly, I don't have a third computer to test it against my second to see if its the connection or hardware)

Here's what my modem setup looks like this. I can access it just like I would a typical router.

Anyway, I just noticed something, although I don't know if it'd make any difference or not. When I assign the non-working computer an IP manually, it sets its IP Subnet mask to 255.255.255.0. As shown in my picture above, it says 255.255.255.252. I don't know how to change it, though (it won't let me edit it directly).

[danrok]

Change the size of client IP pool to 2 or more! It should work then, I hope.

[ShoCKeD]

Originally Posted by danrok

Change the size of client IP pool to 2 or more! It should work then, I hope.

Sadly, it won't let me edit that either.

I could try picking up another modem and seeing if that works, if it's worth a try.

EDIT: Would that be causing problems with my LAN? I can't network my computers via the switch whatsoever, though I haven't tried disconnecting the modem yet.

[danrok]

In order for the modem's DHCP to allocate 2 IP's, one for each machine, the pool needs to be at least 2.

I can't understand why it won't let you change that. There's no hope of it working unless you do.

You could look for a firmware update for the modem and see if you can change it after that.

[ShoCKeD]

Looking for updated firmware now, though I don't see any on the official site (apparently modem support for my model has been discontinued).

Otherwise, I guess I'm gonna get stuck buying another modem or contacting Sprint to see what they say.

[danrok]

I recommend getting an all-in-one modem/router if you go down that road.

[ShoCKeD]

Any good brands to look for?

[danrok]

The Netgear DG834G is very popular for home use, that's the one I have.

I think the current version of it is Netgear DG834GT.

Linksys are also popular for home.

[ShoCKeD]

Thanks for all the help!

I have to go out in a few minutes anyway so I'll see what I can find (if not there's always Newegg ).

[Got EpOx]

I have a D-Link DSL-G604T and it works absolutely flawlessly. It also supports computers with 802.11g/b built in. Below is a similar setup to what i have.

http://dlink.com.au/images/UserUploa...4T_diagram.jpg

[BobyJo]

We have a wireless network, and awhile back we had a problem simular to what you are expierencing.

I unpluged the power from the router and there is a small reset button on the back of the router. You take a ball point pen and push in on the reset button, hold the button in for about 15seconds. Then plug in the power supply cable and the connections will began to light up on the front of the router.

After the reset, you should be able to edit all the settings, or maybe the settings are all changed to where they should be after powering up after the reset. Just be sure you have all the computers connected to the router prior to powering up after the reset.

The last time I went through this, I connected everything and made sure all the computers are on while I installed the OS to the raid 0 array.

Win XP Pro made all the needed adjustments to the router settings it found as necessary..

We have VOIP so we have two routers, one NetGear Wireless 108 speed router and the Linksys is only for the VOIP phone service.

Anyway the easiest way was to have all the computers on and connected while installing Win XP Pro.
All the settings were installed automatically and works great ever since.