this a question in my studies that im not confident with, any info or reading links would be awesome.
i can see the dns records in the host are wrong.
im thinking maybe be a simple reboot could do the trick or could the dns records need updating, so maybe ipconfig /flushdns ??? or or or
im tired
please help !!!! thanks
here is the question
You have just changed the IP address of one of your servers (called "serverx’) from 192.168.0.5 to 192.168.0.26. A user calls and complains that they cannot access any of the shares on serverx. You ask them to type ‘ping serverx’ into a command prompt and they get the following result:
Pinging serverx [192.168.0.5] with 32 bytes of data:
Request timed out.etc.
Ping statistics for 192.168.0.5:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
What is the problem and how do you fix it?
i can see the dns records in the host are wrong.
im thinking maybe be a simple reboot could do the trick or could the dns records need updating, so maybe ipconfig /flushdns ??? or or or
im tired
![Smile :) :)](/data/assets/smilies/smile.gif)
here is the question
You have just changed the IP address of one of your servers (called "serverx’) from 192.168.0.5 to 192.168.0.26. A user calls and complains that they cannot access any of the shares on serverx. You ask them to type ‘ping serverx’ into a command prompt and they get the following result:
Pinging serverx [192.168.0.5] with 32 bytes of data:
Request timed out.etc.
Ping statistics for 192.168.0.5:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
What is the problem and how do you fix it?