Fortunately the client and the server I was debugging used a connectionless protocol (not TCP) and so the interface coming down did not prevent them from communicating further. This means we lose all connections to network drives, any existing telnet sessions, VNC sessions etc. Every time we toggle from static to DHCP or vice versa, the network interface goes down and back up again. However, this method has a significant drawback. Once I'd figured out the commands to use and put them together into two batch files (static.bat and dhcp.bat) I had a method that was sufficiently quick and easy to reproduce the bug I'd started out investigating. Netsh interface ip set dns "Local Area Connection" dhcp To change the interface back to using DHCP and so have it allocated a different IP address netsh interface ip set address "Local Area Connection" dhcp Netsh interface ip set dns "Local Area Connection" static 192.168.1.200 primary
#Dos commands windows 10 change ip address keygen
The second command explicitly sets the DNS server to use for name resolution - normally this is done for us by the DHCP server. The "interface ip set address" command changes the IP to 192.168.1.101 (this address is outside the range allocated by our DHCP server, therefore it will be different to what we had before) and I also had to provide the subnet mask (255.255.255.0), default gateway (192.168.1.5) and a gateway metric.
After some experimentation, I found that the following two commands were sufficient to give my machine a static IP address and have everything still work ok.
0 kommentar(er)
