AeonG wrote on 2022-03-07, 19:54:
I tried the subnet thing. I might have misunderstood what you wanted me to do, but on the routers settings page it did not allow me to set an ip out of range. I did set the router to hand my Windows 98 PC (which for some reason only shows up as Sunrich Technology on the client list) and hooked my 98 PC up to my newer router. It did not register the change and thought it was still connected to my network (see confusion.png in attachments). I set windows 98 to set the IP manually, and while it seems to have registered that change on the connection info program I showed in that picture, now the windows 98 pc will not even show up in the client list on my router.
.
Not exactly...
If you're not up to speed with IP networks, I suggest a good primer (TCP/IP for Dummies is a good place to start, but there's lots of info online too).
Just to clarify the terms I was using:
- subnet. That's the network that your router is routing (connecting to the internet). Judging by the pic from your router GUI I suspect it is 192.168.1.0-192.168.1.255, which is generally written as 192.168.1.0/24. Note that the first IP (.0) is the network addres, the last IP (.255) the broadcast address, and somewhere in there (usually .1 or .254) is the router address aka Default Gateway.
- DHCP scope. The addresses within that range that the DHCP server hands out. That could be almost anything in that subnet, but usually you'll see something like 192.168.1.10 - 192.168.1.100.
- I was suggesting to manually set IP in the Win98 PC (so not in the router). That means any IP that is in the subnet that is not in the DHCP scope and is not network, broadcast or router address. So in my example 192.168.1.2 would be OK, as would 192.168.1.101. This may not be the same in your case, you need to check DHCP scope in the router to be sure.
In your manual setting, you have set an IP 192.168.2.2, which is in a different subnet (192.168.2.0/24). That won't work if your router is in 192.168.1.0/24 😮
Proposed steps:
- set the Win98 PC manually to 192.168.1.2 with subnet mask 255.255.255.0 and default gateway 192.168.1.1, with DNS servers 192.168.1.1 and 8.8.8.8
- in a DOS prompt, try the following commands, in this order. If they all work, you're 100% on internet. If not, the first command to fail tells you where the problem is.
PING 127.0.0.1 (should always give four replies, if not your whole networking stack is messed up)
PING 192.168.1.2 (should give four replies if you set the IP correctly)
PING 192.168.1.1 (this is the important one, if this gives replies you're OK with the current IP address, if not, the problem is between PC and router)
PING 8.8.8.8 (this is a Google IP on the internet, if this does not work but the last one did, there's some router setting not giving you internet access)
PING GOOGLE.COM (this tests DNS. If everything is set as listed and the previous steps worked, this one should too)
Note that it could start failing at PING 192.168.1.1 if there is another device on the network using the same 192.168.1.2 IP. I'm assuming it will be free, but you really should check first.
dionb wrote on 2022-03-07, 00:00:
What motherboard are you using? Knowing its PCI revision might also help determine compatibility.
I have included a CPU-Z report of my entire system.
Mainboard Manufacturer: IntelCorporation
Mainboard Name: D815EEA
So an Intel OEM motherboard in a Dell system with i815E chipset. That means PCI 2.2 and native 3.3V support. Whatever else is going wrong, it's not your network card getting the wrong voltage.
As for the network cards you suggested, I do not have any PCI-X slots on my machine. Never actually used any PCI-X cards in my life, but apparently they are backwards compatible?
It is, but I wouldn't recommend it. They're big, hot and cumbersome. The Intel cards I recommended are 32b PCI, not PCI-X. But tbh, now we know you have a PCI 2.2 system, the current card should be good enough. I suspect either driver issues (have you tried new Realtek drivers yet?) or Win98SE networking messed up. Or just a damaged/not properly inserted cable.