Windows Server 2008R2/2012 Time Sync

I did a post HERE last year regarding verifying NTP settings on a Windows Server.  Now, I recently needed to go a step farther and force a server to time sync with a DC.  Here are the relevant commands:

To find out what server is the time server on your domain, run:
C:\> nltest /dsgetdc:DomainName /timeserv

To verify the domain time server (displayed in the previous output) is reachable, run:
C:\> nltest /server:ServerName /query

Finally, to force a time sync, run:
C:\> w32tm /resync /computer:LocalServerName /rediscover

You can also use the shorter version: w32tm /resync

The LocalServerName is the server/pc you would like to force the time sync on.

**If you are having time sync issues and you are running in a VMware environment, check the ntp status of the VMware host and verify that time is correct**

Advertisements

Cisco vs HP vs Dell CLI – VLAN Configuration

This post continues my series on the differences between these three manufacturers and how they implement L2 and L3 VLANs.

Scenario 1: Create a Layer 2 VLAN

Cisco:
vlan 10

HP:
vlan 10

Dell:
vlan database
vlan 10

Scenario 2: Create a Layer 3 VLAN (that’s routable)

Cisco:
interface vlan 10
ip address 192.168.1.1 255.255.255.0

HP:
vlan 10
ip address 192.168.1.1 255.255.255.0

Dell:
interface vlan 10
ip address 192.168.1.1 255.255.255.0
routing

The biggest difference between all three manufacturers is that HP does not implement a separate VLAN interface for L3 configuration.  Cisco and Dell both require you to go into interface vlan mode before configuring L3 information (IP addressing).  Dell also requires the routing keyword to actually route that VLAN.

**All three manufacturers do require you to input the command IP Routing if you want the switch to route packets**