Strange Networking Issue

This is only occuring on one computer, and it just started recently (until this week, I've had no such problems from it):

It has two NICs (tried running both one and then both, no difference), and neither one will connect to either WAN or LAN. I can't even ping computers on the same LAN, as I get "Destination host unreachable" or "Unknown host [computer name]."

So I ran an ipconfig, and got nothinge more back than "Windows 2000 IP Configuration". Nothing else.

Ran an ipconfig all, and got:

Host Name.......................: [my computer's name]
Primary DNS Suffix............: [our domain]
Node Type........................: Broadcast
IP Routing Enabled...........: No
WINS Proxy Enabled.........: No

And if I try an ipconfig /renew:

"Error: No adapters bound to TCP/IP are enabled for DHCP."

Now here's the kicker -- There is no static IP address configured, it's ALL dynamic. The latter message usually indiciates a preset static IP. So now what do I do? It can't communicate with any computer within or beyond the LAN.

You could try and remove the NICS...reboot-then reinstall.
Reset your preferences??

Did you try a hard boot...total powerdown?

MLF

try to remove one NIC
try again
swap the NIC's around
Try again

I assume XP ?
is it joined to your domain?

try and plug it into a known good network point
use the known good cable in the suspect network point

have you had any 'problems' recently ? power outs / surges / PC rage :D

have you checked that it still is getting IP addy's dynamically ?
that the use this IP addy box hasn't been checked

Windows 2000...

Tried all above suggestions, nothing worked.

it sounds like your TCP stack is corrupted. Have you done a repair installation of the OS?

Remove TCP\IP and then reinstall....

What changed from last week to this week??

Try new cards...or a card from a machine that is working??

MLF

Hey Hey,

Try netsh int ip reset reset.log you may need to grab netsh from the res kit in 2000.. not sure about that.. but it will work with 2000.

Another option would be to grab winsock fix - http://www.itc.virginia.edu/central/...D=67&nav=title

Peace,
HT

Nothing changed from last week to this week (in fact, I wasn't even here, it's been sitting idle!).

Swapped various NICs.

Reinstalled the OS.

And STILL nothing.

Argh.

Quote:

---

Reinstalled the OS.

---

Doesnt make sense...when you set it up..it asks you about your network settings???

It didnt do that???

MLF

It did, only it failed to find the network in order to connect to it.

Try it with one card first...

after the OS install (and updates) add the second card...I seem to remember this as an issue with 2 NICs... 2000 server.....during an install.


or you have a cable\connectivity issue

MLF

When you say, "reinstalled OS", did you do a fresh install, or just rerun setup?

Initially I was going to say, make sure the DHCP service was running on the client, but after the rest of the ts you've done I doubt its that. Still worth a look though.

Actually, Morgan, I've tried it with both cards alone (I suspected too that it could be a problem with both running simultaneously), and then with a third card by itself.

zENGER, The setup was a Windows repair installation. I didn't want to wipe the drive with a fresh install.

However, if you'll notice from my other thread, I'm getting "memory cannot be written" errors during the repair. I believe it's occuring when COM components are being installed. I've tried it with three different memory sticks, and it still persists.

Did you try HTRegz winsock fix

I had a machine where this was the issue...and a repair did not work!!!

Caused by malware and antispyware removal

The networking was so fu$%ed up...it was unrepairable

More Info

http://compnetworking.about.com/od/w...winsockfix.htm

http://www.google.ca/search?hl=en&q=Winsock+fix&meta=

Try the fix or a format reinstall

Probably fix your memory read errors too ;)

I think it may be all tied together

MLF

If you're ready to fdisk and re install, try this first

Go to Run > regedit > and delete the following

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

Restart the computer
Go to Network Connections
Right click and select Properties
Click on the Install button
Select Protocol
Click on the Add button
Click on the Have Disk button
Go to the \Windows\inf directory
Select anything there and click Open
Highlight Internet Protocol (TCP/IP)
Click on the OK button
Check to see if your network adapter obtained a new IP lease and if not...
Reboot

WinsockFix didn't fix the problem unfortunatley.

Quote:

---

\Windows\inf

---

Where is this located? Either I'm blind (likely) or I don't have a folder by this name in plain view...

Not sure why, but is your LSP stack OK?

http://www.cexx.org/lspfix.htm

I have certainly encountered it as a problem with internet connections.

:)

Quote:

---

Originally posted here by AngelicKnight
WinsockFix didn't fix the problem unfortunatley.



Where is this located? Either I'm blind (likely) or I don't have a folder by this name in plain view...

---

It's a system folder, you need to select show system files and folders under the tools - folder options- view tab - In explorer

Hey Nihil,

The LSPFix program didn't discover any problems.


Dinowuff,

Tried your trick as recommended, but no luck.


Now is this just wierd as heck or what? I'm about to move the HDD over to another box and see what happens booting up from that one.

You know I was on a machine last night...receiving read memory errors....

And I noticed the machine was running extremely low disk space on the system partition...

>by the way>User is a computer *spurt*...machine has 3 partitions...with everything possible residing on C:\ :rolleyes:

Could be the part of the problem??? lack of disk space

You know how windows loves memory...needs memory...and really starts to actup when it cant get any....it appears you have many issues on this box

As for moving to another box...you are slaving in the hard drive...cause if the board and other hardware are not the same...it wont boot! as a boot drive.


Slave it in..remove the data...and format reinstall from scratch....should solve your issues...


MLF

Just a suggestion, but is the hub/switch/cabling in use fried?

Steve