In Windows Server 2012 R1/2, 2008 R1/2, 7, Vista, and 2003 SP2 and later, it’s good to run the following two commands in an administrative command prompt (an ordinary command prompt for 2003):
w32tm /config /manualpeerlist:pool.ntp.org,0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org /syncfromflags:MANUAL /reliable:YES /update
In Server 2003 SP1 and before, and XP, we use this, because /reliable doesn’t exist:
w32tm /config /manualpeerlist:pool.ntp.org,0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org /syncfromflags:MANUAL /update
Sometimes w32tm doesn’t exist as a service, and has to be registered:
Under Windows 2000, we need to go a bit more archaic:
net time /setsntp:pool.ntp.org
net time /querysntp
If you are using Windows DHCP services, the above is best for the server, but for all of the workstations under its control, place the server’s IP in the Time Server option. This is probably best for a domain. When you have standalone or mobile-capable machines, best to just use the w32tm configuration above.
If you’re working remotely, you don’t want your connection to go down, so we need to do it all in one command. So:
netsh interface ip set address "Local Area Connection" static <PC-IP> <Subnet-Mask> <Default-Gateway> & netsh interface ip set dns name="Local Area Connection" static <Primary-DNS> primary & netsh interface ip add dns "Local Area Connection" <Secondary-DNS> index=2
Be sure not to include the
<> characters when replacing!
Here’s a great new one, HTML5 only, no Flash or Java:
Here’s a commonly used one which requires Flash:
And another which uses java:
For CIDR to IP range (IP range extraction):
For IP range to CIDR:
For lots and lots more:
A few notes:
- In the original shipping version of Windows 7, NET USE commands in login scripts and command shells did not work. After about two months, however, if all updates were installed, they began working. This method still works well, and is not disrecommended.
- Windows 7 libraries are the way to do the equivalent of “My Documents” redirection. They can be set manually. Just right-click on a library and go to Properties, and you can direct it wherever you want.
- But if the server does not have Windows Search 4 or higher, you will not be able to do your redirections as in #4. For this, you have two options. First, you can set Offline Files for the folder in question. Or second, you can use a wonderful third-party utility at the following location:
Sometimes IPv6 is installed on XP in a hidden form — sometimes IPv6 may be installed, but not visible in any Windows GUI. To find out, go to command prompt and enter:
netsh show helper
If IPv6 is installed, in that list will be “ipv6”. To uninstall on XP, run this:
The ipv6 command does not exist on Server 2003. The following does:
netsh delete ipv6mon.dll
Hidden IPv6 has been shown to cause problems in some Oracle environments.
First get a list of interfaces:
wmic nicconfig get caption,index,TcpipNetbiosOptions
Make note of the number of the interface you want to change. Once you have it (for example, number 0000009), do this to enable:
wmic nicconfig where index=9 call SetTcpipNetbios 1
List of options:
0 – Use NetBIOS setting from the DHCP server
1 – Enable NetBIOS over TCP/IP
2 – Disable NetBIOS over TCP/IP
If you find that mapped drives disconnect without rhyme or reason, go here and do what Liz found for all of us:
Go to the Start ball, enter “Folder Options” in the search box. Under “View”, far down in the checkbox options, you’ll see “Sharing Wizard”. Turn that off, to turn off simple file sharing in 7.
Saw this for the first time; on a Windows 7 laptop, all network devices except two, were yellow-flagged, and in their properties it said code 31, which means not able to load the driver files. In this condition, I found that I could not uninstall any network objects in Device Manager: it permitted me to do so, but immediately after the deletion was done, the objects remained.
I googled it a lot, found zero of real use, except the underlying pattern that apparently one very badly-behaved network driver or virtual device, can hose the whole Windows 7 networking stack in this very way.
In this case, there was a certain high-profile vendor’s VPN client installed, and it was this vendor’s items which were not yellow-flagged, but instead, were marked disabled. So I focussed on that, deleted the .sys file involved, and deleted every registry entry for them also, in safe mode, excepting only the LEGACY entries which I could not get permission to delete, even running regedit as administrator. No change: the objects remained after reboot.
I then tried System Restore, and took the OS back to the point before the issue began to occur. This had a very positive result; networking came back. The VPN client will need reinstalling, but I will update the machine all the way as next step, and then install the latest version of the VPN client.