BleepingComputer.com: Ethernet connection/No connectivity

Thanks for the ipconfig /all reports! That helps.

As suggested earlier, enter the NIC settings manually until this is fixed. Then report the ipconfig /all again please.
It really is a good idea to remove variables from the problem space - and this removes DHCP from the picture (for now).

@MrBruce1959

I have the drive split into a 100GB portion for the boot/system (Windows XP Home) files along with any program files (antivirus, office, etc.). I use the other partition as file storage only. It is more of a cosmetic thing for me, I tend to be the type that puts everything in a place and neatly organizes it. (My desktop only has the recycle bin!)

I also apologize for my denote of the "C:" drive turning into ©


I have no other Operating Systems on the drive.

Kurt

This post has been edited by kkremer212: 22 February 2011 - 04:27 PM

@fred3

Here is a second listing of my ipconfig /all.

I still go back to one of the differences in the "Node Type." When it is trying to acquire an IP, it is reflecting Broadcast, when it gives up on dynamic or in this case with static it is sitting at Unknown. On my working machine it is listed as Hybrid (I assume both broadcast and receive) Possible issue?

Thank you to all for the help and suggestions!

Kurt



Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.


Windows IP Configuration

Host Name . . . . . . . . . . . . : XPComp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel® PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-0C-F1-EB-0C-XX
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.17
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 24.159.193.40
68.115.71.53

Pinging 192.168.0.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.


Windows IP Configuration

Host Name . . . . . . . . . . . . : XPComp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dynex Gigabit PCI Adapter
Physical Address. . . . . . . . . : 74-EA-3A-AA-77-XX
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 24.159.193.40
68.115.71.53

Pinging 192.168.0.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

When trying to aquire a DHCP address it is always done as a broadcast request using 255.255.255.255 for an IP. The Hybrid designation is the standard for a correctly operating DHCP aquired device. Hybrid basically means the setup is capable of standard IP based transmissions like multicast, and broadcast.

Quote

Yep, that's what I figured, now the question is....Why is the node unknown on the non working machine, and is that the issues? What would cause that, and what setting is possible not correct? Or is this an non-issue and when the true issue is resolved, this will be resolved?

Kurt

It is not an issue. The hybrid designatiin is only recieved after aquiring an address via dhcp. Since you cannot do that right now you will not see it. Static applied ip addresses do not recieve the hybrid designation.

In addition to pinging 127.0.0.1 you should also ping the local NIC IP address - now that it's set up static. Presumably there are now 2 machines that don't work and one that does. Lots of messages here to figure that out.....

Are these machines "pingable" re: firewall and ICMP permission incoming? If so, can they ping each other?

Have you repaired the tCP/IP stack on these computers yet?

Typical method to fix:
Go to Control Panel / System / Device Manager and remove the NIC altogether.
Reboot
The NIC will reinstall without any help at this point.

Of course you'll have to reconfigure the IP settings manually unless it starts working via DHCP (the default).

After that, what happens?

Are there any possible interfacing commonalities - like a switch or hub or common cable after the switch/hub?
Can the working machine ping either of them?

Quote

Only two wired devices. One that works, and one that does not. I have two NIC cards in the non working one, It was thought that the mobo device was bad, but I get the same results with the new PCI card. I try them independently on each run with the other disabled to try to reduce any possibility of interference.

Quote

Quote

I can ping the local host, but nothing else. The working machine can ping my laptop and my wifi enabled handheld device(iPhone) but not the problem computer. I tried both NIC's independently from each other with same destination host unreachable mesage on each one. I tried pining from my desktop and my laptop for the process.

Quote

Yes. I also tried the winsock suggestion as well.

Quote

Same results as before. No connections.

Just for information, the NIC re-installed but did not recognize the drivers, I ran the driver repair tool off a flash drive that came with the driver download and it recognized them at that point.

Quote

All of my devices are run through he same Motorola cable modem gateway. I have my one working machine hooked via wired connection, one laptop wireless, two handhelds wireless. The problem computer is a wired device.
So as far as common parts, yes, the modem/gateway and beyond is shared.

This post has been edited by kkremer212: 23 February 2011 - 03:21 PM

I just want to thank everyone who has been thinking about this. My type A+++ personality really kicks in when I encounter these puzzles. Real world I would have just re-installed OS and gone from there, but to me there is an answer. I actually am finishing up my degree in IS (career change) and this is really educational for me, better than a classroom for sure! Everyone has offered additional things that I have devoured for knowledge, so for that, I want to thank you as well.

At this point, is the re-install of the OS probably the best bet? It seems like we may be running out of ideas.



Kurt

At this point I`m afraid we may just be

Shy of any fresh input I`m afraid a nuke and repave is the last viable solution.

I will agree.

I think at this point we are running in circles and have to chalk it up to "Windows!"

Thanks again to all that have helped out and offered suggestions. Your time and input has been invaluable.

Kurt

That`s what BC is here for.

Just never feel right when a Member walks away with an unresolved problem.

All - after clean install of XP, all works smooth. Both NIC card and MOBO Ethernet connection work without issue.

Thanks again!

Glad to hear you have resolved your issue.

I think what your problem was you had a driver in your OS data base for your device that just wouldn't quit and it was causing you to have the problems you were experiencing.

The clean install removed that driver and now things are functioning as they should be.

Although we remove a driver package from a system by removing the software, sometimes a driver remains behind in the system32\drivers folder that can still cause problems.

No one said that all uninstall programs remove everything that the associated program created when it was installed.

Drivers are one such file type that gets left behind.

Bruce.