Seven steps to troubleshoot server access problems
72-Page PDF: Windows 10 Frequently Asked Questions
In this comprehensive guide, our experts answer the most frequently asked Windows 10 questions ranging from the OS itself, to migration, to user-adoption, and everything in between.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.
1. Verify that the system is indeed running TCP/IP and has an IP address. If it doesn't, add one.
2. If it is running any other protocols (IPX/SPX, NetBEUI, etc.), remove them at least for testing -- you can add them back later.
3. Verify if you can ping the system on its IP address. If you can't, verify that you can ping 127.0.0.1 from the server itself. This could be sign that the NIC is bad.
4. Verify that you can ping the system by its fully qualified domain name. If you can't, verify that the name is entered in DNS and WINS.
5. Verify that the server is a member of the same domain that all the rest of the servers and clients are. If it is not, either add it or verify that trust relationships are working properly.
6. Ensure that the server service is running.
7. Finally, make sure that you are logging on to the client system using a network account.
Also, Microsoft has a Q article detailing a more obscure issue related to a corrupted MUP that you may want to review.
Dig Deeper on Windows legacy operating systems
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our Enterprise Desktop experts
Start the conversation
0 comments