• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dual-boot system: Win2k can't connect to Net, Win98 does

H

Hamman999

Member
About a week ago, I started having some serious problems with my @Home and my Win2k SP1 half of my dual-boot system (Win98SE is the other OS). For about 7 days, I have been unable to use internet access of any kind on the Win2k partition. I normally use @Home's DHCP to resolve my IP address, but that hasn't worked. I've tried adding my settings statically, reinstalling SP1, reinstalling the protocols for the LAN connection, disabling/enabling the connection, a bunch of different small system changes (diabling services and other small registry edits). Nothing has worked. Everytime I run my system with DHCP (or lack thereof) I get this error in the event log and whenever I try to renew my IP: "The following error occurred when renewing adapter Local Area Connection: An operation was attempted on something that is not a socket." The strange part of this is I can ping outside servers if I use the correct IP (yahoo.com, mail, news, etc.) but i cannot use IE or any similar program to connect to their sites. @Home's help was worthless as they won't support me with my dual-boot setup and whatever adivce they did give was incorrect. Basically, what I'd like to know is what this stupid error message is trying to tell me and how to fix it. If possible, I'd like to avoid reinstalling the OS and opening up the case, but right now I'm desperate. I just reinstalled 3 weeks ago by mistake when I was having a similar problem (which turned out to be a DHCP server outage with @Home). Thanks in advance.

I have been conversing with Slikkster of the Tech Support forum here about this very problem.

David
P.S. Thank God for Windows 98.

 
When I had this problem in setting up @Home in my wife's computer it was because of a default gateway entry in the LAN NIC's tcp/ip configuration - kept the @Home NIC's tcp/ip from accessing the @Home DHCP server by sending the search for it in the wrong direction. If you don't have a second NIC, this would not be your problem. If you can ping internet IP addresses you're getting connected, and the problem is in name resolution. If you want to try manual configuration, connect using your working win98, and use winipcfg.exe to get all the entries, including DNS servers and the domain suffix that is being used.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top