Can't connect to the internet after Win2k re-install

I recently re-installed Windows 2000 Professional on my computer and things seemed to go smooth at first. But when I tried to connect to the internet (via cable modem), I could not get a connection. I have tried repairing the installation, switching ports on the hub, switching network cable, replacing NIC card, and using a different PCI slot. I know my cable modem is still working becuase my other PC works fine. I also know the NIC card works fine because I can pull up the "bad" computer from the "good" computer over the network. However, when i do an IPconfig from the command window I have no settings.

Anyone got any ideas on what is happening and how I can fix it?
Who is Participating?
omkConnect With a Mentor Commented:
Write down Ip address and other information from the pc which can see internet, unplug it from switch, type in these numbers in your test pc. If it works it means that your ISP releases only one IP address, and you need the second nic to be installed and internet sharing turned on.
More info please:

- have you got a router?
- does the cable modem provide dhcp ?
Check if your NIC is disabled.
If you have nothing in ipconfig you did not install TCP/IP,
if it is then you have problems with your NIC (hardware or configuration.
Click Start->Settings-> Network and Dial up connections.
Do you have local area conection icon there?
If NO then system can not foind your NIC, check device manager.
If yes, right click on the icons (it should be enabled (disable on pop-up window), goto the properties. check show icon box, verify that you have tcp/ip istalled, checked its configuration.
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Verify if your host file is correct.
simply try ipconfig/release and ipconfig/renew.
Is your PC correctly add to the domain ?
emeysenburgAuthor Commented:
more info....
I do not have a router. I have two standalone computers that are connected to a switch (i had said hub earlier... sorry). The switch is then connected to the cable modem. The ISP provides DHCP.

TCP/IP is installed. When pulling up Network and Dialup Connections from the start menu and selecting Status, the dialog box confirms that I am connected. If I select properties from the same place, I have 4 components listed (and checked)... Client for Microsoft Networks, File and Print Sharing, NetBEUI, and Internet Protocal (TCP/IP). When I select properties from TCP/IP, I have 'Obtain an IP address automatically' and 'Obtain DNS server address automatically' selected.

When I do a ipconfig from the command line, here is what i get.

Connection-specific DNS Suffix  . :
AutoconfigurationIP Address . . . :
Subnet Mask . . . . . . . . . . . :
Default Gateway . . . . . . . . . :

It should be this (or similar):

Connection-specific DNS Suffix  . :
IP Address. . . . . . . . . . . . : 65.28.xx.xx
Subnet Mask . . . . . . . . . . . :
Default Gateway . . . . . . . . . : 65.28.xx.xx

Hope this helps with diagnosis.

This is an APIA address.
Quick fix is to assign temporary static IP address, reboot PC and then check "obtain IP address automatically" again.
You can not release APIA address with ipconfig.
You need to edit registry to disable APIA permanently.
emeysenburgAuthor Commented:
omk: can you be more specific.

What is a APIA address and what is it for?
How does this prevent my system from obtaining an IP from the DHCP server?
How do I edit the registry to disable APIA permanently?
They call this APIPA as well:
this is the link with short explanation:;EN-US;q255836
To disable it completely you need to create a new key IPAutoconfigurationEnabled of type REG_DWORD within the subkey:
Assign 0 to this key,
to enable change the value to 1.
And you need to reboot PC.
The worst case you need to do it up to 5 times,
but already mentioned trick with a temporary address can save you some time.
The problem is that the machine can't find a DHCP server to get an IP address from, or it isn't setup to use DHCP.  How many machines do you have, and do you have a dedicated DHCP server?

emeysenburgAuthor Commented:
you were correct about the APIPA. I have since setup an IPAutoconfigurationEnabled key in the registry. This corrected the problem of getting an AutoconfigurationIP Address of Now when I do ipconfig, I just get

While playing with the registry, I compared the settings between my 2 computers. The computer that works had a lot more settings than the other so I added a few registry keys to see if I could force it to find the DHCP server. Here is what I added: DhcpDomain, DhcpDefaultGateway, DhcpServer, DhcpNameServer, DhcpSubnetMask, DhcpSubnetMaskOpt..... I added all those and still nothing. However now the ipconfig displays Connection-specific DNS Suffix  . :  like it should.

I am raising the point value since this seems to be a pretty difficult question.

ssr: please see my second response.

Thanks for the help
emeysenburgAuthor Commented:
forgot to update point value
emeysenburgAuthor Commented:
I pulled up Microsoft Management Console to look at the errors being generated and here is the DHCP error:

Your computer was not assigned an address from the network (by the DHCP server) for the Network Card with the address 0040xxxxxx. The following error occurred: The semaphore timeout period has expired. Your computer will continue to obtain an address on its own from the network address(DHCP) server.

BTW, I do not like this semaphor message.
Do you have scsi devices on this computer?
On the switch, does the status led for the network connection where you plugged in the Win2K computer show a connection? Does also the Win2K NIC show a connection (if the NIC has a connected led)?

If this is OK, go to Network connections and open the NIC's properties. You may want to enable the "Show connection in taskbar" option since it will allow you to see when data is sent or received by blinking. Open the NIC's status window, if the "Sent Packets" or "Send Bytes" (depends on the NIC driver) greater than zero? I assume that receive is 0.

If send is greater than 0, could it be that your ISP only allows a limited numer on machines to be connected? Som ISPs have a limitation of 1, or 2, computers. If the DHCP server encounters a new computer (MAC address), it just doesn't give a DHCP address. In this case, ask your ISP to reset the registeres MAC addresses of your computer.

omk, a semaphore (in computer programming) is a structure used for thread synchronization. It's not related to SCSI at all. When DHCP tries to get an address, it uses auch a semaphore to lock the NIC until the DHCP answer packet has arrived. If it does not arrive, the semaphore timeout expires, and the DHCP client knows that there was a problem.
emeysenburgAuthor Commented:
Turns out the error WAS with ISP. They recently upgraded their servers to only allow one IP address per MAC address.

Thanks for the help.

You know that if you turn on ICS, you still can enjoy internet sharing.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.