Networking

How to add a static route

Posted on by Imran Rashid
Reading Time: < 1 minute

To add a static route, open command prompt and type the below (Amend the ip details as required). The below command is just an example.

route add 10.0.0.0 mask 255.0.0.0 192.168.0.1

You could also add the costmetric command. Assigns an integer cost metric ranging from 1 to 9,999 to be used in calculating the fastest, most reliable, and least expensive routes. If costmetric is not specified 1 is used as default.

Example of command with costmetric:

route add 10.0.0.0 mask 255.0.0.0 192.168.0.1 metric 2

DHCP client service won’t start – access denied

Posted on by Imran Rashid
Reading Time: < 1 minute

If you are unable to start the dhcp client service and receive an access denied message, it’s due to the network service account not having the permissions. Follow the below instructions to resolve:

1) Click start
2) Click run
3) Type regedit (please be careful when editing the registry – Always take a backup)
4) Navigate to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dhcp\Paramaters
5) Right click the parameters folder/key and click permissions
6) Check that the network service is visible and has full control permissions
7) If the network service account does not exisit, add and grant full control
8.) Start the dhcp client service

How to check if teamed network cards are conflicting

Posted on by Imran Rashid
Reading Time: < 1 minute

If you are receiving the below error within your event log and want to know if teamed up network cards are causing the problem, follow the instructions below:

Error: The name “DC name       :1d” could not be registered on the Interface with IP address

1) Click start
2) Click run
3) Type cmd and click ok
4) Type nbtstat -n and press enter

Check the server name status. If it shows conflict, access the WINS server and under active sessions > display records, locate the server name and delete the server record.
Next go back to the server and within the command prompt type nbtstat -R. Next restart the server and follow steps 1 to 4 again. The state should now be showing as registered and the above error should no longer appear.

The name “MYDOMAIN :1d” could not be registered

Posted on by Imran Rashid
Reading Time: < 1 minute

If you are continuosly receiving the alert below, i would recommend you click here to find a list of solutions.

One solution is to disable lmhostlookup within WINS located under Network connections – TCP/IP settings.

Error:
The name “MYDOMAIN :1d” could not be registered on the Interface with IP
address ***.***.***.***. The machine with the IP address ***.***.***.*** did not
allow the name to be claimed by this machine.