f by some chance you're in a situation in which computer network you are trying to manage is giving you some inconvenience, it is likely that there are different simple collisions or conflicts in it. What should we do?
This section will discuss the easiest way to solve various problems that may arise in networks, making it from command line in MS-DOS.
With the following five steps will achieve our mission:
- 1. Execute the command prompt
At this level we all know how to access the command prompt from Windows. Anyway, for the most misguided: we go to the Start menu, then click the "Run" and type "cmd" and press "Enter."
This is the command prompt, where we can do certain actions from simple or complex command lines, as in MS-DOS operating system.
2. Type "ipconfig / all" and see the information
To already be at the interface of the command prompt type "ipconfig / all", which is a command that displays the information about Windows IP Configuration. What do we need this? Then to see if our connection is a "DHCP", since most of the tips that will present work with these protocols.
3. Renew Windows IP Configuration
If you already feel frustrated and do not know what to do, before restarting the computer and the router (hub, switch, hub or whatever you're using), one option would be to renew the IP configuration of Windows, a viable solution.
Simply just type the following command line:
ipconfig / release followed by
ipconfig / renew
Thus, we first released the IP address of the configuration of our team, and then we have renewed the aforementioned configuration.
4. Emptied cache, renew connections, etc.
If the problem persists after released and renewed the IP settings of Windows, then the problem goes further. To this end, we recommend using the following commands to fix the problem you are having your network:
ipconfig / flushdns: Clear your cache and resets the resolution for a client. This procedure can debug negative entries. ipconfig / registerdns: Just takes care of dynamic renewal of registration has been allocated for DNS connections from the client.
nbtstat-R: Command that is responsible for debugging in the name table cache and reload remote eradicating problems.
5. We tested our connection again
Now that we've done different procedures for debugging in the network, we proceed to testing the connection to see how good or bad has been the same, remember that to do all this does not require rebooting.
With these commands we can check our link:
tracertThis command is used to track or trace the path that leads a specific package, a Christian, your work helps us determine whether the connection of our network is quite right, because if the trace is sent without waiting time exceeded, This is indicating that everything is fine. Simply just type tracert localhost; localhost tracert indicates that we're doing the machine is running.
ping: Pinging involves sending a package to a computer and expect a response the same, if you return a successful response, it means that the server is up, so obviously has no problems.
Similarly to the previous point, you can simply write the command of the form: ping localhost, Which indicate to make a ping to the computer that is running the command, the local host.
For confirmation, the two commands in the fifth point is stated can be run from another computer with Internet access, only instead of "localhost" will be our IP, which can be achieved with the command ipconfig.
