Win98se Machine not Accepting DHCP

I have a small home network with a Linksys router acting as a DHCP server. I have a total of 4 machines - 3 Win 98se and 1 Win 2k. All except one Win98 machine can ping the router and access the Internet.

The machine in question can ping itself (127.0.0.1) which tells me that TCP/IP is installed. This machine can also see the shared folders and printers on the network via NetBEUI. So the network card and cabling are working.

The machine is set for DHCP but is not accepting any information from the router.

Any and all help will be appreciated.

Tony
beyenhoftAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jvuzCommented:
td_milesCommented:
try running the command "winipcfg" and renewing the address. If that fails, can you give the machine a static address and it works ?

I've often found with win98 the easiest way is to just remove TCP/IP and install it again. If this fails, remove networking entirely. Sometime there is no easy way to fix, except reinstall.
Luc FrankenEMEA Server EngineerCommented:
Have you checked the cables?

If everything fails, try reïnstalling your TCP/IP stack and winsock.
Open Network settings
1.) Remove all protocols except the Network Interface card.
2.) Click Apply & Close the Properties box, but on reboot notice, hit Cancel. Do not reboot!
3.) Open Regedit and delete these keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\Dhcp
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\Dhcpoptions
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\MSTCP
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\Winsock2
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2

Close Registry Editor.

4.) Open Network Properties again, and Click ADD - PROTOCOL - Microsoft/TCPIP (should Add Client for MS Networks Automatically)

Have your windows CD ready or the CAB files,
Reboot and you should be good.

LucF
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

svenkarlsenCommented:
The fact that you are able to ping 127.0.0.1 is not sufficient proof for local functionality, - you must be able to ping the 'local' outside IP as well, e.g. 192.168.1.10.

reply from 127.0.0.1 just tells you that the TCP/IP protocol is installed, - from there and till BIND is established to the NIC, is still some way to go.

As td says: remove and re-install. I seem to remember that you can see the binding between protocols and adapters somewhere, but my memory is getting week....
saeid_nCommented:
Hello
which range of ip your nic get when you set "obtain an ip automatically" if it is something like 192.168.x.x it means that your tcp/ip not working properly and the easiest way in this condition is to set a static ip and if the problem solved you can set "obtain ...." again if it is not working again the finall way is to reinstall tcp/ip again.

good luck

beyenhoftAuthor Commented:
I tried uninstalling and reinstalling TCP/IP using the method recommended by LucF. No luck there.

Setting the IP and other settings manually does not work either.

I rebotted to a command prompt and ran the Windows setup program from the directory where I have the CAB files. After reinstalling Windows, the "Connect to the Internet" icon appeared on the desktop. But, when I click the icon I get the following error message: "Failed to load the Internet Connection wizard helper component.

I don't know if that helps anyone as to what could be wrong.

I am contemplating the wiping the drive and starting fresh. But, I would rather not have to resort to that.

Thanks for any help possible.

Luc FrankenEMEA Server EngineerCommented:
Strange...
Have you tried virusscanning that computer?
Have you checked for ad-/spyware? Try Adaware from http://www.lavasoftusa.com/support/download

LucF
Casca1Commented:
Sounds as if the either the TCP/IP stack is corrupt, or the SOCKS is hosed. You have tried removing TCP/IP. Next, verify all configuration in the networking cpl, make sure you have the latest and correct drivers, and remove it all, reboot, and let it get re-detected.
That should straighten you out.
Luc FrankenEMEA Server EngineerCommented:
You might want to try a repair installation of windows, just boot of the win98 cd-rom and let it install on top of the current installation (probably c:\windows) You won't loose your programs or data, but you might have todo some updates from http://windowsupdate.microsoft.com again.

LucF
Luc FrankenEMEA Server EngineerCommented:
I would like to know if a repair installation helped.
Casca1Commented:
Yeah, a detail of what resolved the issue here.
Luc FrankenEMEA Server EngineerCommented:
Then why do you want to delete this question?
Casca1Commented:
I don't, unless it's resolved. And, of course, any points that might be forth coming... 8-)
Luc FrankenEMEA Server EngineerCommented:
Nevermind, I misread your comment.
Casca1Commented:
8-) Of all the things I've been called, nevermind is probably the cleanest... Hehehe
Luc FrankenEMEA Server EngineerCommented:
;-)
beyenhoftAuthor Commented:
All suggestions were attempted, except wipe the drive and start over. In a last ditch effort, I swapped out the network card for another of the same brand. Everything is running fine now. It was a 3Com card. Called 3Com and explained what happened. They replaced the card.

Sorry for not posting the solution sooner. Got so backed up on stuff to do, I forgot about this questions.

Thanks for all of the suggestions.
Luc FrankenEMEA Server EngineerCommented:
Ok, now I understand, glad you got it working, C101, I think this Q might have value as a PAQ, so please don't delete it but save it as a PAQ.
Casca1Commented:
Well, we'ld have gotten around to hardware sooner or later... 8-)
Luc FrankenEMEA Server EngineerCommented:
Yep Casca1, I agree with you.

beyenhoft, next time try to respond earlier so we can give you more information if you have more questions.
Computer101Commented:
PAQed, with points refunded (250)

Computer101
E-E Admin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.