steelcaress
Beta member
- Messages
- 4
I have an interesting problem with my wife's computer that I hope you can help with. She's running Windows 2000 Pro, SP4.
She recently lost internet access (most likely due to a tech at Mediacom, our internet company) and when I type in "ipconfig" in the Administrator Account it gives me no IP addresses whatsoever.
When I type in a "release" or "renew" switch along with it, I get this error: "No adapters bound to TCP/IP are enabled for DHCP."
Okay, fair enough. I Googled the error message, as I do whenever I get a message I don't quite know how to troubleshoot, and found this page: http://www.jsifaq.com/subR/tip8700/rh8740.htm. I follow the instructions on the page, and am stopped when I find the command it asked me to run opens Device Manager. Device Manager doesn't show a network adapter tab. It never has. Even while the machine was online.
The card works fine. There is no problem with it, as near as I can tell. And I have the same card in my machine, working fine. The card lights up when you plug the router in, the router shows that the port is in use and that there's an active link there. I've even swapped out cables to make sure that things are running smoothly, and plugged it directly into the cable modem. Still nothing.
Strangely enough there's also no "Local Area Connection" or whatever under her Network information (GUI, not command line). And when I make a new connection, it doesn't stick. It doesn't show anything new.
I have something gleaned from Microsoft's Help and Support site. It's a scripting command to force an adapter back to DCHP:
netsh interface ip set address "Local Area Connection" dhcp
Will that screw things up royally, or have no effect, or have any effect at all? I'm thinking it won't be able to do anything, since there is no "Local Area Connection" to bind back to DHCP.
It's almost like this computer was on the internet "just because" and no other trace can be found. I know in Win98 you can uninstall and reinstall the TCP/IP stack. You can reset it in Windows XP. I'm not sure what to do in Windows 2000, or whether that drastic a step is appropriate. Any suggestions would be greatly appreciated.
She recently lost internet access (most likely due to a tech at Mediacom, our internet company) and when I type in "ipconfig" in the Administrator Account it gives me no IP addresses whatsoever.
When I type in a "release" or "renew" switch along with it, I get this error: "No adapters bound to TCP/IP are enabled for DHCP."
Okay, fair enough. I Googled the error message, as I do whenever I get a message I don't quite know how to troubleshoot, and found this page: http://www.jsifaq.com/subR/tip8700/rh8740.htm. I follow the instructions on the page, and am stopped when I find the command it asked me to run opens Device Manager. Device Manager doesn't show a network adapter tab. It never has. Even while the machine was online.
The card works fine. There is no problem with it, as near as I can tell. And I have the same card in my machine, working fine. The card lights up when you plug the router in, the router shows that the port is in use and that there's an active link there. I've even swapped out cables to make sure that things are running smoothly, and plugged it directly into the cable modem. Still nothing.
Strangely enough there's also no "Local Area Connection" or whatever under her Network information (GUI, not command line). And when I make a new connection, it doesn't stick. It doesn't show anything new.
I have something gleaned from Microsoft's Help and Support site. It's a scripting command to force an adapter back to DCHP:
netsh interface ip set address "Local Area Connection" dhcp
Will that screw things up royally, or have no effect, or have any effect at all? I'm thinking it won't be able to do anything, since there is no "Local Area Connection" to bind back to DHCP.
It's almost like this computer was on the internet "just because" and no other trace can be found. I know in Win98 you can uninstall and reinstall the TCP/IP stack. You can reset it in Windows XP. I'm not sure what to do in Windows 2000, or whether that drastic a step is appropriate. Any suggestions would be greatly appreciated.
