Home Networking trouble

The NIC is built into the mobo, and when I plug in the ethernet cable, it lights up steady orange, doesnt flash. I plugged the cable into my laptop and got a good signal from it.

Ive disabled IPv6 in Vista, and manually changed the settings that were on there to the settings my laptop shows...Vista says it finds multiple networks, but wont show me any to connect to. It says Im in the network, and have internet, yet I cannot ping my router or get to anything beyond it. Ive tried signing in as admin to the router from this PC, no luck. Can do it from the laptop, though.

I did disable the firewall, no luck there either...

Let me get an ipconfig up here...

more 'undocumented' features from M$ ? [Bang]

Okay, here we go..

Quote:

---

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-18-F3-97-BB-FE
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.110(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.87.85.98
68.87.69.146
NetBIOS over Tcpip. . . . . . . . : Enabled

---

UPDATE!

Used a registry edit I found on the MS website and now my pings are reaching the router, though they are high...

First was 775ms
Second is 1771ms
Third was 1996ms
Fourth was 35964ms...quite possibly a record high ping for a local network...

ummm.. got the latest drivers for that pos os?

http://support.microsoft.com/kb/932134

link dropped

the link also has a link to a nifty tool that may help you out

Router is a Linksys WRT54GL with that useless quick setup button...got it last may, so in theory it would be compatible with Vista....hell, I used to have Vista 32bit on this machine and had internet, just since I installed 64bit that Ive had this problem...

Those ping times could be erroneous due to timer drift. Does your system have a multi-core processor?

Did the registry change relate to disabling the IPv4 Checksum Offload? Most of the folks having problems with Marvell NICs and 64-bit Vista say that this driver fixes the problems;
http://www.marvell.com/drivers/drive...dId=193&pId=40

Your router should be fine. Just make sure your firmware is up-to-date. I have the WRT54Gv5. If I had the Linux version like you I'd probably be running DD-WRT or Tomato firmware. I'm currently running the DD-WRT v24 6.2 Micro release candidate on my router. I get better QOS and throughput along with some features that Cisco didn't include.

Hell, I've installed Vista multiple times on the same system and had it do different things on each install. Don't even get me started on multiple platforms and having different responses. It's far from consistent. Sometimes you add a wireless connection and it works for a while, only to mysteriously stop working.

On one of my Vista Enterprise 32-bit notebooks I had it set to do a boot-time defrag using Diskeeper 2008. I set it to perform a chkdsk before the defrag. The chkdsk found some "free" space that was identified as being used that it was nice enough to free up for me. Problem was, the space ended up belonging to the MFT. I never could recover from that. Had to reformat the disk. That's the first time in 15 years I've had the MFT flake out like that.

So I downloaded that driver and tried to get Vista to install it, but it says the best driver is already installed, even though the installed version is 9.xxx while the new one is 10.xxx

So fuckin stubborn...I uninstalled the driver and Windows immediately reinstalled it...

XP x64 was frustrating enough. I tried to make myself use Vista Ultimate 64-bit, but I got tired of working around the limitations. Even SP1 RC didn't make everything wonderful. You are a brave soul to rely on Vista 64-bit.

I'm using 32-bit at work almost exclusively. When I want to get something done at home, it's usually being done on XP. We probably won't adopt Vista on a wide scale at work. We may just have to hold out for Windows 7 (eta 2010).