Mr4dmin
07-17-07, 09:46 AM
Hiyas, new to the forum, and have an odd problem. A client brought in an older server, HP Proliant ML350, about 4 years old, which had been spiked (electrically), and some things stopped working. The OS is Windows Server 2003, SP2 (was SP!, just installed SP2), Intel Xeon 2.8/2.8, 1.5Gb RAM, NIC is builtin, HP NC7760 Gigabit Server Adapter.
Connectivity issues are, can't ping anything but 127.0.0.1 and the NIC's physcial address, can't ping it by its own name. Uninstalled NIC, reinstalled NIC, updated drivers, installed SP2. Reset TCP/IP accroding to MS KB Article 317518 - netsh int ip reset C:\resetlog.txt. Diagnostics from the manufacturer on the NIC say it's running fine, Windows says it's running fine, what it looks like its doing is starting, then stopping, and not moving on. will send around 66 packets, receive 2 or 3, and then quit. There is a link light, and activity (mind you not a lot if any at times) light. If you unplug the network cable, it says unplugged, if you unplug from the swtich, it sees no cable, again. DHCP doesn't work, of course, static settings get connectivity, at least to the wire, no internet no nothing, and as I said, won't ping but its own IPs. Short from shooting this machine, I have exauhsted what I know to do.
We put in 5 different NICs in the one PCI slot this machine has - all have had the same problem as stated above. As a side note, IPsec service won't start, says it can't find the file, but that shouldn't affect normal connectivity, as I understand it.
Anyone have any ideas? Really lost now! :confused:
Need this up and running by tomorrow - if it's not a fried motherboard.
Thanks in advance!
Mr4dmin
Connectivity issues are, can't ping anything but 127.0.0.1 and the NIC's physcial address, can't ping it by its own name. Uninstalled NIC, reinstalled NIC, updated drivers, installed SP2. Reset TCP/IP accroding to MS KB Article 317518 - netsh int ip reset C:\resetlog.txt. Diagnostics from the manufacturer on the NIC say it's running fine, Windows says it's running fine, what it looks like its doing is starting, then stopping, and not moving on. will send around 66 packets, receive 2 or 3, and then quit. There is a link light, and activity (mind you not a lot if any at times) light. If you unplug the network cable, it says unplugged, if you unplug from the swtich, it sees no cable, again. DHCP doesn't work, of course, static settings get connectivity, at least to the wire, no internet no nothing, and as I said, won't ping but its own IPs. Short from shooting this machine, I have exauhsted what I know to do.
We put in 5 different NICs in the one PCI slot this machine has - all have had the same problem as stated above. As a side note, IPsec service won't start, says it can't find the file, but that shouldn't affect normal connectivity, as I understand it.
Anyone have any ideas? Really lost now! :confused:
Need this up and running by tomorrow - if it's not a fried motherboard.
Thanks in advance!
Mr4dmin