Troubleshooting and Resolution Strategies

The provided content discusses common troubleshooting issues in various areas, including operating system installation, DNS, TCP/IP connectivity, backups and restores, and iSCSI storage. The article suggests solutions to these problems, such as removing secondary hard drives during OS installation, verifying IP configuration settings for DNS resolution, using IPCONFIG commands to check configurations, and testing connectivity between hosts and storage nodes.

1
Running head: TROUBLESHOOTING
Troubleshooting Document
Name
Institution

2
TROUBLESHOOTING
Common Operating System (OS) installation issues
Common OS installation issue includes reaching at a specific percentage at setup and not
proceeding further due to issues. In such situations, one should remove all secondary hard drives
attached with the computer including USB, Hard disk or memory cards to let system price (King,
2009). Another possible issue can be overloading of RAM. Hence, it can be fixed removing any
bad media installation by burning a new DVD. One of the common problems is not recognising
the computer hard drive during installation. In such cases, booting from installation disc and
reprocessing the installation rule out the problem. This ensures that hard drive detects the BIOS.
DNS issues on the server and the client
Keeping TCP/IP valid configuration ensures that system will not encounter Name not
found error, which is usually the case (Davis, 2009). Another problem that comes into picture is
DNS name resolution settings problems. One can run ipconfig command to check and verify IP
configuration settings for the network. Furthermore, verification of valid subnet mask, IP address
is a must for DNS issue resolution.
The DNS server sometimes doesn’t respond to the client request due to network failure.
If the DNS server is not responding, it means DNS network provider should be contacted to
check the background processes. Moreover, on the client side network adapter can be checked to
ensure that they are working fine. A ping command on the dos can help you identify whether the
server is sending data packets or not.
Common TCP/IP connectivity issues

3
TROUBLESHOOTING
The first troubleshooting step in TCP/IP connectivity is invalid configuration settings and
it can be ruled out by checking the correct configurations as provided by the provider. This can
be done manually as well by using the command prompt and running IPCONFIG/ALL
command. This command displays the configuration settings and results. Furthermore, it is quite
likely that PC computers may use network interface cards (NIC) and operating system consider
ports as network adapters (Cisco, 2017), hence, one has to ensure that they are checking the
correct configuration linked to NIC connected to the network. A blank TCP/IP configuration
indicates that the interface doesn’t have an IP address. In case a DHCP server there are several
commands to obtain IP address and do a manual configuration. Commands can be IPCONFIG
/RELEASE, IPCONFIG /RENEW, or IPCONFIG /ALL for use.
Common backup and restore issues
Combination of differential and incremental backups is one of the common issues that
users encounter. This issue can be resolved by incorporating one or other types of backups
together. Modified data filter are set at the time of taking a backup, in case these are not set
correctly, backup may encounter an issue. Addressing this issue, one can set the modified data
filter to the last differential backup. Furthermore, clearance of modified bit can render files
unrecognized. Hence, the application hosted on server that might be responsible for the clearance
of modify bit should be removed. Once the backup process is done, restored files may show an
error that namespace formats of the files were not restored. Possible reasons is the failure to
configure file attributes and namespace formats on the restoration volume. Additionally, File
restoration process may be slower than what you anticipate and the possible reason is
simultaneous working of file compression and restoration. Hence, end user must ensure that the
two processes are not done at the same time.

4
TROUBLESHOOTING
Connectivity issues with iSCSI storage
The first issue with ISCSI is connectivity issue. Resolution steps include, testing
connectivity between host and the storage node hosts. The second step includes, sending a ping
to the storage host system from the host to ensure there a connection. If the ping command shows
the connectivity is fine, firewall settings must be addressed so that they do not block the
connection. Finally, the verification of the gateway and subnet mast setting can help in resolving
the connectivity issues with iSCSI storage.
References
Cisco. (2017, January 14). Troubleshooting TCP/IP. Retrieved from Cisco:
http://www.cisco.com/en/US/docs/internetworking/troubleshooting/guide/tr1907.html

5
TROUBLESHOOTING
Davis, D. (2009, June 17). 10 Ways to Troubleshoot DNS Resolution Issues. Retrieved from
Windows Networking: http://www.windowsnetworking.com/articles-tutorials/trouble/10-Ways-
Troubleshoot-DNS-Resolution-Issues.html
King, J. (2009, November 2). Windows 7: Common Installation Problems and Their Solutions.
Retrieved from Seven Forums: http://www.sevenforums.com/installation-setup/34853-common-
installation-problems-their-solutions.html