Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 424
  • Last Modified:

Server cannot access network anymore


The server we are using for a retail store went down today and i cannot figure out what the issue is.  The latest thing that occured before the issue begame was a Virus Definition Update.

I have a server running WinXP Pro SP3 and the icon shows that the network is connected and it is running on the same workgroup as all the other computers and has an internal static IP.  All the other computers have the same set up and they are working just fine and can surf the internet.

The server cannot connect to the network nor the internet, which means that my computers cannot access the database and run transactions.

- The Antivirus software DOES not have a firewall, and the windows firewall is turned off.
- I have tried the WinSock Fixer tool and have had no luck.
- I have reconfigured the network settings on the server.
- I have reset the router

Please help, manual handwritten transactions suck!

We are using POSIM as our POS software with a Sybase Database
1 Solution
Some things to try:

Check the IP stack by pinging yourself (
Try uninstalling the antivirus. Not sure why this would have broken it but perhaps a red herring.
Try installing another NIC if you have one handy.
Try a different port/switch if possible. Sometimes they show connected yet still aren't working as they should.
See if you can see yourself in My Network Places.
Try changing IP address, then switching back to original to force it to rewrite config.
It's also possible that another user on the network has the same IP and the IP conflict is causing the problems you mentioned.
Try powering down that server and see if you can ping that IP, if you can then there's a conflict, if you can't then it rules out that as the solution.
Hi khaji00

Start with the basics, is this a cable based or wireless based environment.  I am assuming it is cable based.

1) Check your physical connection (Ethernet cable from the Server to the Router). Make sure you have a known good working cable connecting to your network hardware.
2) Check the light on the router or switch port where it is plugged into
3) Ping the loopback to make sure the actual network card itself can function properly as Michael42 suggested.
4) Go to Start | Control Panel | Network Connections | Local Area Connection and right click on it and select properties, go to the TCP/IP (Doubleclick it) and make sure the static ip address settings are correct.  Make you have the right ip address and subnet mask and gateway (Usually the Router in this case) and make sure DNS is working set correctly (usually you can use the gateway ip/ router ip as the DNS.
5) Try pinging your static ip address that from the command prompt. Click Start | Run | and type cmd <enter>.  Type ping <your static ip address here>

6) If you can at least ping the static ip address, it tells us that you can at least talk to your own system.
7) At the command prompt try pinging the router (ping <insert ip of router>) If you can't even get your router then there is definately a communication problem. If you can ping your routers ip address then try also pinging your dns.  If you cannot ping your dns, your internet / name resolution will never ever work.

Try these steps and let me know the results

khaji00Author Commented:
the NIC card died on us!

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now