Why yes....yes it is. Here are those settings: Windows IP Configuration -Host Name . . . . . : XP01 -Primary Dns Suffix : -Node Type . . . . . : Unknown -IP Routing Enabled. : No -WINS Proxy Enabled. : No Ethernet adapter Local Area Connection 5: -Connection-specific DNS Suffix . : -Description . . . . . . . . . . . : Fast Ethernet Adapter -Physical Address. . . . . . . . . : xx-xx-xx xx-xx-xx -Dhcp Enabled. . . . . . . . . . . : Yes -Autoconfiguration Enabled . . . . : Yes -Autoconfiguration IP Address. . . : 169.254.237.184 -Subnet Mask . . . . . . . . . . . : 255.255.0.0 -Default Gateway . . . . . . . . . :

0

The 169.254.x.x address tells me that your computer is not getting an IP address from the router. Now we just need to figure out why. The fact that you have a link light (indicating a working physical connection) on both the router and the computer suggests that the problen is indeed software related. Try this. Go to the Device Manager and select View -> Show Hidden Devices. Expand the "Network Adapters" section of the device manager and delete all "ethernet adapter" items. Also delete any "AOL" entries, if there are any. Reboot, and let Window re-install your network adapter. Post back after you have done all that, and let us know if you are still having the same problem.

0

I gave that a try. I did not see any duplicate adapters (kinda expected to) but I removed/uninstalled all items that would. There were a few WAN items that would not uninstall. I got a message, something like "cannot be removed - may be needed to boot" Anyway...I rebooted, nic reinstalled wonderfully....ran the Network Wizard...but still have the same thing described above. This may not mean anything, but... I have noticed that each time I reinstalled the nic.....its number keeps increasing in the "network connections" window. Only one item is listed, but it is now labeled "Local Area Connection 6." It was 5 before. I kinda expected to see 1-4 with that "show hidden" tab, but there was only one. Thanks very much.

0

What's happened is that when you killed the AOL install process you corrupted your registry. You can try doing a System Restore to roll back your registry to an older, uncorrupted version but you may lose other functionality doing this. First disable your XP firewall to see if this is blocking access to your router - sometimes it turns itself on in full "lockdown" mode when you install new network protocols. If this doesn't work try booting into Safe Mode to remove the problem TCP/IP settings.

0

Thanks for the suggestions. I gave the safe mode a try. I removed any tcp/ip items and uninstalled the nic (while in safe mode). Not as many network config items show up when in safe mode. I may have missed removing some tcp/ip when in safe mode if they are located in some little know areas. Anyway...upon reboot...the nic reinstalled fine...but still...just that default ip shows up...and no connection as before. I'd really rather not have to reinstall Windows just for an ip config issue. Also...I unfortuanately had turned off system restore a few weeks ago when doing a deep virus scan/fix, and forgot to reactivate it. So...I don't have any restore points. This is a real hair-puller....one single item...making the whole pc almost useless.

0

Did you check to see if your XP firewall is up? Take it down if so. From the command prompt ping 127.0.0.1. This is your NIC's address and if you get an OK back the NIC is probably good. Next ping your router's IP gateway address (usually either 192.168.0.1 or 192.168.1.1) to see if your PC can "see" the router.

0

I just pinged that IP. Got a response just fine, so, I suppose that means the NIC is okay. But, the protocol still remains messed up...somewhere "deep down" in the OS config. I really DREAD having to reload XP. Granted....if I'd not forgotten to reactivate System Restore...I wouldn't have this problem. Well....if anything else comes to mind...any other suggestions would be greatly appreciated. Thanks

0

Are you sure you are on the right subnet? Linksys default is 255.255.255.0, not 255.255.0.0 that you have set up. Try adding a default gateway in your TCP/IP advanced settings. I assume your router address is 192.168.0.1 so put that in there. I think we have established that your network card is fine and most of your software is working fine, and I am certain a system restore would have resolved this little problem but as that is disabled the next step is going to be reinstalling windows - after putting AOL on your machine I would do that anyway! Damn awful software... I wouldn't touch it with someone elses... Just a further point, random SHOUTED WORDS is really annoying.

0

Hey...got a sliver of daylight here. I did go in to the connection and mannually configure the IP settings. I had mistakenly assigned 192.168.0.1 to the computer and rightfully gotten the message that it conflicted with another unit on the network (which is the router itself). For a test, I tried 192.168.0.2 which is another PC on the network...and got another "ip conflicts" message. This presumably means that all the ip stuff (hardware and os-wise) is working fine. I used 192.168.0.3 and the config worked fine. HOWEVER....even with these current settings, I cannot pull a web page (with IE or Mozilla). I've gone through the connection wizard a couple of times in IE, but nothing. It's pretty quick too. Within 2 secs of launching either browser, it returns the message "page cannot be found." Anyways...with this additional info about the computer appearing to be connecting to the LAN just fine, does anything else come to mind? THANKS

0

Did you also manually configure: DNS server addresses? Default gateway address? Without those, your computer won't be able to resolve DNS names or send/receive traffic outside your local network. Which is what sounds like is happening.

0

Also.....One other thing: I just opened a command line Window and tried the PING command. Although Windows is aware of other IPs on the network (it told me when I had a conflict when manually configuring the nic on the problem computer....as described above)....it cannot PING those IPs. For example, trying to PING 192.168.0.1 (the router) simply returns "destination host unreachable." This does not seem to make sense....why would Windows be aware of that IP when configuring the NIC....but then not be able to PING it? Any ideas Greatly appreciated.

0

Probably because you have no default gateway configured. See my previous post.

0

Quick Update..... The computer can now PING the router and the other PC. I went back and set up the DNS and Default gateway - thanks. However...it is still not pulling any Web pages with either IE or Mozilla. All firewalls, etc. have been disabled. Any advice greatly appreciated.

0

What happens when you try to pull up a web page? Do you get any error message? What are they? What address(es) did you use for DNS servers and default gateway? Are they the same as on your other machines?

0

Yes...same as the other computers. DNS and Defualt Gateway are: 192.168.0.1 Trying to pull Yahoo, or any other page in IE just gets that default "Cannot file web page" then goes on to list suggestions of what to do. It is a pretty common defualt page in IE. You prolly may see the same one if you unplugged the com cable and then opened IE.

0

If you can ping the router and the router is in fact acting as a DNS server/proxy, then I don't see any reason why it's still not working based on what you've said. Why don't you paste your ipconfig /all output again. Maybe I or someone else can spot something there that you haven't thought to mention.

0

Okay..... Here's the IP info for the PC that is NOT working (XP PRO): Ethernet adapter : Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Fast Ethernet Adapter Physical Address. . . . . . . . . : 00-xx-xx-xx-xx-xx Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.3 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 And here is the one for the computer that IS working (WIN98): Ethernet adapter : Description . . . . . . . . : D-LINK ADAPTER Physical Address. . . . . . : 00-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . : Yes IP Address. . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . : 192.168.0.1 They are both connected to the Same router. They can see each other through the work, but the TOP one cannot pull a web page. THANKS P.S. Seeing them side by side, one item does look suspicious.

0

You didn't include the working computer's DNS servers. You say they are the same as on the compter that's not working, but you also say that the non-working computer can't resolve DNS names. A logical conclusion would be that the DNS servers are not the same on both computers. I would recommend checking that again.

0

Well...I checked the DNS spec...they are the same. Also...I observed this. When the IP is Manually configured, with the correct subnet and dns server...the Dlink router CAN see the computer. And the computer can ping the router just fine (PING 192.168.0.1). HOWEVER, if I set the computer IP config to: "obtain IP address automatically" then that PC will completely drop off the network. The router cannot see it...and if I try to PING the router...it gets "no response." In EITHER case, it cannot pull a web page. Even when I've mannually configured it...and the router sees it fine (it shows up in the routers connected list), etc....a web page will not load. It is as if the cable in unplugged (as described above). For some reason....it cannot obtain an IP address automatically...but even manually configuring it...while allowing to ping the router...does not provide access to the internet. BUT...I can plug the same cable into another computer....and things work fine. Any additional help greatly appreciated. THANKS

0

why not try enabling the DHCP on the computer thats not working so that it can automatically give you an ip. i one time gave myself my own ip and as a result i had a few problems. I assume your on a NAT?

0