W2K Server losing network connection

Hi, I'm new to this forum so thanks in advance for any help.

We have a back office computer on Windows 2000 running our micros POS system. We do not use this computer for anything else. A few months ago, the owner had wifi and some cameras installed that are attached to the shared switch which connected to the cable internet modem. The camera/wifi tech decided to reconfigure the micros network to adapt to his new configuration and brought the POS to a screeching halt. I finally managed to undo all of the changes he made and got micros back up and running. They continued to have intermittent network drop offs so I installed a new network card and separated the micros LAN so that it would stay stable.

The original network card remains and is needed to get online so they can process credit cards. Unfortunately, the internet network connection continues to drop off. It loses connectivity once or twice every day or two and we have to reboot which solves the problem but only temporarily. This connection is set to auto DHCP.

Here are the last handful of messages from the eventlog with the most recent first.

Your computer was unable to automatically configure the IP parameters for the Network Card with the network address 000FFE1D863D. The following error occurred during configuration: The parameter is incorrect. .

The server could not bind to the transport \Device\NetBT_Tcpip_{2234F853-E0CD-4A79-9024-DF5233E185DF}.

The system detected that network adapter Broadcom NetXtreme Gigabit Ethernet was connected to the network, and has initiated normal operation over the network adapter.

Broadcom NetXtreme Gigabit Ethernet: Network controller configured for 100Mb full-duplex link.

Broadcom NetXtreme Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000FFE1D863D. The following error occured:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

Any help is much appreciated. Thanks.

Additional EventLog info from yesterday:

The DNS Client service could not contact any DNS servers for a repeated number of attempts. For the next 30 seconds the DNS Client service will not use the network to avoid further network performance problems. It will resume its normal behavior after that. If this problem persists, verify your TCP/IP configuration, specifically check that you have a preferred (and possibly an alternate) DNS server configured. If the problem continues, verify network conditions to these DNS servers or contact your network administrator.

The ntidn service failed to start due to the following error:
The parameter is incorrect.

The IP address lease 192.168.10.101 for the Network Card with network address 000FFE1D863D has been denied by the DHCP server 192.168.10.1 (The DHCP Server sent a DHCPNACK message).

Being that this computer is basically being used as a server for say to run this POS system, first thing I would do is take it off of dhcp and put a static ip on that network card.

Second thing I would check is the equipment that is issuing the ip address (the dhcp server/router).

After putting a static IP on it see it it still looses connection.

We had it on a static ip for a couple of weeks but it created more network drop offs with ip conflict errors. The wifi router was configured to dole out ip addresses outside of the static ip but we kept getting the conflicts. Switching the internet nic to dhcp eliminated that error and has given us 2-3 day stretches of stability. The LAN for the POS workstations is static and on a separate nic. That portion of our network is stable.
I am wondering if this could be a coincidental nic failure which seems unlikely as it is not a perpetual problem.

If your getting IP conflicts you need to choose a different IP that is not in the range that is being dished out by the dhcp server.

The static ip was outside of the range being handed out by the dhcp. Based on the configuration, the ip conflict errors did not make any sense which is why we went to auto dhcp. The conflict errors have stopped. Currently we have had four days of stability. The longest we have gone without an error is seven days.

Thats great news, hope it continues to work for you.