Jared Heinrichs

You are here: Home / Search for "TEST"

Search Results for: TEST

By Leave a Comment

WordPress Error 500 after upgrading PHP

There are a couple of things I have found that fixes this issue.

Go into php.ini  and search for “cgi.rfc2616_headers” and Uncomment the line and make the value equal to “1”.

It should look like this when you are done:

  • cgi.rfc2616_headers = 1

Make sure that PHP version has been changed at the server level and at the app level within IIS!

One other thing that you will need to do check in on is to make sure that you have the proper version of Microsoft C++ installed. Each version of PHP needs a slightly different version. You can find out what version you need by checking out this website: http://windows.php.net/

At the time of writing, these are the versions you will need. I always recommend that you check out: http://windows.php.net/ for the latest info!

VC9, VC11 & VC14

More recent versions of PHP are built with VC9, VC11 or VC14 (Visual Studio 2008, 2012 or 2015 compiler respectively) and include improvements in performance and stability.

– The VC9 builds require you to have the Visual C++ Redistributable for Visual Studio 2008 SP1 x86 or x64 installed (Make sure 32bit is installed!!!)

– The VC11 builds require having the Visual C++ Redistributable for Visual Studio 2012 x86 or x64 installed

– The VC14 builds require having the Visual C++ Redistributable for Visual Studio 2015 x86 or x64 installed

By Leave a Comment

How to Configure the Windows Time Service in an Active Directory Forest

Original blog post reference:
Configuring the Windows Time Service in an Active Directory Forest – A step by step with a Contingency Plan
http://blogs.msmvps.com/acefekay/2014/04/26/configuring-the-windows-time-service/

Windows Server Time Sync Configuration

The following steps can be used to configure DCs the default Windows time service hierarchy in an AD forest.  The procedure will also remove any errors in the Event Viewer, if any existed.

Do not use if you are using a third party stratum service and refer to the vendor’s documentation for further instructions

Check and Document the Current Time Configuration on the PDC Emulator

  1. First check and document the current configuration:
    1. All Windows Server domain operating systems – run the following on the forest root domain PDC Emulator.
      1. Note: In some cases you must wait a little time for the service to instantiate.
      2. If you do not see expected results immediately, wait 10 min and re-run the following steps
  2. W32tm /query /configuration   
    1. This command confirms the PDC Emulator shows the current source in the [TimeProviders] section, Look for “Type:” You will see one of the following:
      1. Type: NT5DS (Local)   -This means that it’s not synced externally.
      2. Type: NTP (Local)  –This command it is syncing externally.
                 NtpServer: time.windows.com [65.55.56.206] (Local)
    2. For all other DCs, use the command, w32tm /monitor (step 4 below)
  3. w32tm /query /source
    1. On the PDC Emulator, this shows the actual source. One of two possibilities:
      1. CMOS clock                    -Signifies not synced to an external source                                                  (Not what you want to see)
      2. time.windows.com  –The NTP source IPaddress/FQDN  This is correct.
  4. w32tm /monitor or w32tm /monitor /computers:DCNAME
    1. On the PDC Emulator, this command shows the outside time source.
      1. Good example:
        dc01.contoso.com *** PDC ***[10.10.10.200:123]:
        ICMP: 0ms delay
        NTP: +0.0000000s offset from dc02.contoso.com
        RefID: time.windows.com [65.55.56.206]
        Stratum: 4
    2. On all other DCs, this command shows the current time source DC for this DC.
      1. You will see an “offset for the PDC from its configured NTP source.
      2. Good example result showing the DC02 is syncing with dc01.contoso.com:
        dc02.contoso.com 10.10.10.210]:
        ICMP: 0ms delay
        NTP: +0.0000000s offset from dc01.contoso.com
        RefID: dc01.contoso.com [10.10.10.200]
        Stratum: 4
  5. w32tm /tz
    1. This shows the current time zone to make sure it’s correct.
  6. w32tm /stripchart /computer: target /samples: n /dataonly
    1. This command will show you the time difference between the local computer and a target computer and is helpful in determining if there is an offset. The “n” value is the number of time samples that will be returned from the target to test basic NTP communications.
  7. w32tm /dumpreg
    1. This command dumps the current registry settings found in:
      HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
      You can see the current time service configuration entries, such as:
      Type:  NTPNTPServer:

*

Configure time sync to a reliable source on the forest rood domain PDC Emulator ONLY.

Do not perform on any other DC in any domain in the forest. PDC in the forest root only.

  1. Windows 2003 and all newer:
    1. Open an Administrator Command Prompt.
      1. Note that the examples below use either time.windows.com or the pool.ntp.org servers. You can get a full list of reliable time services at:
        A list of the Simple Network Time Protocol (SNTP) time servers that are available on the Internet: http://support.microsoft.com/kb/262680
    2. w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update
      OR – if you want to use the pool.ntp.org time source servers:
    3. W32tm /config /manualpeerlist:0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,0x1 /syncfromflags:manual /reliable:yes /update
    4. w32tm /resync /rediscover
    5. net stop w32time && net start w32time
    6. Check it with W32tm /query /configuration   
      1. You may have to repeatedly run it a few times until you see it change from the CMOS clock to the time server you set it to. If it doesn’t change after a few minutes, you may have to reset the time service in theContingency section below.
  2. Windows 2000:
    Generally speaking, the w32tm command is similar to Windows 2003 and newer operating systems.  However, Windows 2000 uses the net time /setsntp method, which was removed in later versions.  There are also some differences between Windows 2000 RTM and various service packs. Therefore, if any issues arise from the commands not setting, it’s recommended to follow the instructions using the registry to configure the time service in Windows 2000:
    How to configure an authoritative time server in Windows 2000:
    http://support.microsoft.com/kb/216734

    1. Open an Administrator Command Prompt.
    2. net time /setsntp:174.140.19.7    – Windows 2000 uses this command to configure an outside source.
    3. net stop w32time
    4. w32tm -once      W32tm performs numerous commands. Their results are displayed on the screen.
    5. net start w32time
    6. Check it with W32tm /query /configuration   
      1. You may have to repeatedly run it a few times until you see it change from the CMOS clock to the time server you set it to. If it doesn’t change after a few minutes, you may have to reset the time service in theContingency section below
  3. Use the procedure in Step #1 to check and document the new configuration.
  4. Contingency: Perform the steps in the Corrupted Time Service Resolution Section to return the settings back to Windows defaults.

*

Configure all other DCs to sync using the forest time hierarchy

This includes all other DCs in the forest root domain that are not holding the PDC Emulator role, and any DC in any other domains and trees, including the PDC in those domains.

Do NOT run the following on the PDC Emulator in the forest root domain.

  1. First check and document the current configuration: See Section #3 above.
  2. Windows Server 2003 and all newer server operating systems:
    1. Open an Administrator Command Prompt
    2. w32tm /config /syncfromflags:domhier /update /reliable:no
    3. w32tm /resync /rediscover
    4. net stop w32time && net start w32time
    5. Check it with W32tm /query /configuration   
      1. You may have to repeatedly run it a few times until you see it change from the CMOS clock to the time server you set it to. If it doesn’t change after a few minutes, you may have to reset the time service in theContingency section below
  3. Windows 2000:
    For reference with Windows 2000, see the following link for more info:
    How to configure an authoritative time server in Windows 2000
    http://support.microsoft.com/kb/216734

    1. Open an Administrator Command Prompt.
    2. w32tm –s
    3. Net stop w32time && net start w32time
    4. Check it with W32tm /query /configuration   
      1. You may have to repeatedly run it a few times until you see it change from the CMOS clock to the time server you set it to. If it doesn’t change after a few minutes, you may have to reset the time service in theContingency section below
  4. Use the procedure in Step #1 to check and DOCUMENT the new configuration.
  5. Contingency: Perform the steps in the Corrupted Time Service Resolution Section to return the settings back to Windows defaults.

*

Time configuration on FSMO transferred or seized DCs

  1. On the new forest root domain PDC Emulator, run the following:
    1. Open an Administrator command prompt:
    2. W32tm /config /manualpeerlist:0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org /syncfromflags:manual /reliable:yes /update
      1. Note: time.windows.com is a working time source, however you choose any reliable time services in your locale.
    3. W32tm /resync /rediscover
    4. net stop w32time && net start w32time
    5. Check it with W32tm /query /configuration   
      1. You may have to repeatedly run it a few times until you see it change from the CMOS clock to the time server you set it to. If it doesn’t change after a few minutes, you may have to reset the time service in theContingency section below
  2. On the server formerly holding the PDC Emulator role, run the following:
    1. Open an Administrator command prompt.
    2. w32tm /config /syncfromflags:domhier /update
    3. w32tm /resync /rediscover
    4. net stop w32time && net start w32time
    5. Check it with W32tm /query /configuration   
      1. You may have to repeatedly run it a few times until you see it change from the CMOS clock to the time server you set it to. If it doesn’t change after a few minutes, you may have to reset the time service in theContingency section below
  3. Follow the procedure in Step #1 to check and DOCUMENT the new configuration.
  4. Contingency: Perform the steps in the Corrupted Time Service Resolution Section to return the settings back to Windows defaults.

*

Corrupted Time Service Resolution Section (Contingency)

If any of the procedures did not work or event log errors indicate any issues, you can reset the time service registry entries back to default. The procedure should be done on the DC that you are experiencing issues with and not necessarily on each DC.  Note: This procedure can also be used as a contingency to return a DC (PDC and non-PDCs) back to local CMOS time sync.

  1. On the DC that you’re experiencing issues with, run the following:
    1. Open an Administrator command prompt.
    2. net stop w32time
    3. w32tm /unregister
    4. w32tm /register
    5. net start w32time
    6. Configure the DC according to the configuration sections above depending on if it’s a PDC Emulator or non-PDC Emulator.
  2. The next command is ONLY for Windows 2000 to 2008 DCs. It does not apply to 2008 R2 or newer and will be ignored if you try it.
    1. “net time /setsntp: ”      – Do not use the quotes. Note that there’s a blank space prior to the closing quote.
      This command tells the client (whether a DC or workstation) to delete the current registry settings for time and use default settings.
    2. net stop w32time && net start w32time
    3. Configure the DC according to the configuration sections above depending on if it’s a PDC Emulator or non-PDC Emulator.

*

W32Time Service Accuracy

Please bear in mind that the Windows W32Time service is not a full featured, accurate service for time sensitive application requirements, nor will Microsoft support it as such. You must use a third party time service that will support this requirement.

For more information, please visit the following link:

Support boundary to configure the Windows Time service for high-accuracy environments
http://support.microsoft.com/kb/939322

==================================================================

References

How the Windows Time Service Works
http://technet.microsoft.com/en-us/library/71e76587-28f4-4272-a3d7-7f44ca50c018

Windows Time Service Technical Reference
http://technet.microsoft.com/en-us/library/a0fcd250-e5f7-41b3-b0e8-240f8236e210

Windows Time Service Tools and Settings
Includes specific w32tm command switches and registry entries.
http://technet.microsoft.com/en-us/library/cc773263

=================================================================

Summary

I hope this helped you to easily configure your time service and what to do if it didn’t work.

Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP – Directory Services

By 1 Comment

GNS3 – Can’t connect to the external hypervisor on 127.0.0.1:7200

Are you running GNS3 or GNS3 Workbench and getting the error:

Can’t connect to the external hypervisor on 127.0.0.1:7200

Cant connect to the external hypervisor on 127-0-0-1-7200

After correctly setting up GNS3 Workbench I was getting that error when putting the router into work area.

To fix the error: Can’t connect to the external hypervisor on 127.0.0.1:7200 you must follow these steps:

Edit – IOS Images and Hypervisors [CTRL+SHIFT+I]

IOS images and Hypervisors

Make sure under “External Hypervisors” these settings. The default “blank” working directory doesn’t have enough permissions.

 

Go to “Edit – Preferences”

preferences

Make sure the binding is set to 127.0.0.1

Hypervisor 127-0-0-1

Move back to the Dynamips tab and make sure that the executable in the root path and that the working directory has enough permission to be written to. Click the “Test Settings” button last to make sure “Dynamips” can run.

Dynamips

You should see this:

successful

Go Back to IOS Images. We need to test AutoCalculation and Test the IOS settings.

Test IDLE PC and Test Settings

By Leave a Comment

Multi-Area OSPF network Lab

image

Here’s a Packet Tracer 6 lab I created that tests a bunch of things outside just OSPF. Keep in mind that all the 1941 routers use the HWIC-4ESW to provide four switching ports. It’s important to remember that this is really just a switch attached to the router. You will have to find a way of routing traffic off the switch to the rest of the network.

You will need to be able to ping the router’s “router-id” from anywhere on the network.

I’ve included a picture what the 1941 routers physically look like:

image

Just for good measure here is the backbone router. I needed to add a NM-2FE2W Module. It provided me with two Fast-Ethernet interfaces which allowed me to have up to 4 connections on each backbone router.

image

Here’s the OSPF-Multi-area lab with Before and After Example. I’ve also included all the commands I put into the routers.

By 2 Comments

How to setup GNS3 Guide

Thank you Navneet! This post was made from the info he detailed on the Cisco Learning network and I took it from here: https://learningnetwork.cisco.com/docs/DOC-22414.

1. This document describes in detail, stable configuration details for GNS3 emulator. This is the configuration that works for me.

2. I faced several problems with GNS3 initially.

3. It turns out, once GNS3 is configured to work in a stable state, it is exceptionally wonderful and requires reasonably low system resources.

4. This documentation applies to GNS3 version 0.8.5 as on October 2013

Modifications:

Date – 07 Nov 2013

1. Added a section that describes a workaround to get the NW16ESW switch module to work with relevant routers

First:

The conclusion

1. Use the correct IOS images – It is a known fact that 2600 series images are not stable with GNS3

2. I can not provide the IOS images

3. Delay between routers boot – around 20 to 40 seconds

4. Malfunctioning module, as explained in point numbered 7: “slot 0: GT96100-FE”

Second:

Detailed configuration steps

  • Table of contents:
  • 1. Very important – IOS images
  • 2. GNS3 Installation
  • 3. Custom Directories – This stage can be skipped
  • 4. Configuration of GNS3 – Preferences
  • 5. Configure default IOS images and hypervisors
  • 6. Configure “idle PC” value for router on first boot
  • 7. Malfunctioning module
  • 8. My computers configuration
  • 9. baseconfig.txt
  • 10. NM16ESW Workaround

 1. Very important – IOS images

These are the stable working IOS images for GNS 3. I have some of them as I own the routers.

i. Cisco 2691 Router | 2600 Series – Extremely stable

  • c2691-adventerprisek9_ivs-mz.124-9.T7.bin

ii. Cisco 3640 Router | 3600 Series

  • c3640-ik9o3s-mz.124-25.bin

iii. Cisco 3725 Router | 3700 Series – For MPLS

  • c3725-adventerprisek9-mz.124-15.T5.bin

iv. Cisco 7200 Router – Extremely stable

  • c7200-advipservicesk9-mz.124-2.T.bin
  • c7200-advipservicesk9-mz.150-1.M.bin – For SLA

Note 1:

GNS3 crashes if the IOS image used is not compatible. One of the most incompatible and crash prone IOS image is of 2611XM series router. It is a known fact that 2600 series images are not stable with GNS3.

Note 2:

Once the IOS files have been procured, open them in WinRAR and extract the file. Use this expanded file with GNS3.

2. GNS3 Installation

Download the complete installer from the web site.  http://www.gns3.net/

Very useful: – After installation, locate the file named “baseconfig.txt”

  • a. Normally it is located in the parent GNS3 installation folder.
  • b. This is the default configuration that is applied to each router as it boots initially.
  • c. This file path and name will be specified in “GNS3 – Edit – IOS images and hypervisors – base config: ………….” in step 5.
  • d. Copy this file to the directory “C:\GNS3-Folders\IOS\” that is created in the next step.

I have also pasted the default baseconfig.txt that I use, at the end of this document. It can be used as is or with modifications.

3. Custom Directories – This stage can be skipped

The following steps describe how to create a custom directory, with minimized security settings, for storing GNS3 files.

  • a. Create a “directory | folder” and name it “GNS3-Folders”.
  •  b. Right click on this folder and select “Properties”. On the window that opens, point and click on “Security” tab
  •  c. On this page, at the lower right, click on: – “Advanced” (For special permissions or advanced settings, click Advanced)
  • d. Now “Permissions” tab must be open by default.  On this window, point and click on “Change Permissions…”  Uncheck – “Include inheritable permissions from this object’s parent”. On the warning that appears, select “Remove”.  Check – “Replace all child object permissions with inheritable permissions from this object”
  • e. Click on “Add” – “Advanced” – “Find Now”. Click and select “Everyone”. Click “Ok” – “Ok”
  • f. On the window that appears, confirm that:
    • i. Apply to:  “This folder, subfolders and files”, is selected from drop down list.
    • ii. Now, in the lower window, in front of “Full control”, check – “Allow” Click “Ok” – “Ok” – “Yes” – “Ok” – “Ok”
  • g. Within this “GNS3-Folders” folder create the following four directories:
    • Capture
    • IOS
    • Projects
    • Temp
  • h. Place the IOS files within the “GNS3-Folders\IOS” directory.
  • i. Place the ‘baseconfig.txt’ file within the “GNS3-Folders\IOS” directory too.

4. Configuration of GNS3 – Preferences

From the menu bar, go to:

i. Edit – Preferences – General – (General settings)

Delay between each device start when starting all devices – 30 seconds

Autosave – 0 seconds

Paths:

  • Projects directory: – “C:\GNS3-Folders\Projects – specify the path where you want the projects to be saved. I have configured the path to my thumb drive”
  • OS Images (IOS, Qemu, PIX etc.) directory: – “C:\GNS3-Folders\IOS – specify the path where you have placed IOS images.”
  • Configuration file: – Important.
  • The path cannot be configured. However, note down the specified directory and after you have completely configured and checked GNS3, including ‘idle PC’ values, copy the gns3.ini to a different location.
  • The complete configuration as well as specific idle PC values are retained in the gns3.ini file. Each time GNS3 is installed, only this file needs to be ‘imported’ and all the configuration is reinstated.

Caution – Paths are also reinstated along with rest of the configuration.

ii. Edit – Preferences – General – (Terminal settings)

Preconfigurated terminal commands:

  • Select “Telnet (Windows)” from drop down list and then click on “Use” button
  • Checked – “Close associated terminal programs when deleting a node”
  • Unchecked – All the rest
  • Delay between each consol when consoling to all devices: – 4 seconds

iii. Edit – Preferences – Dynamips – (Dynamips)

Executable path to Dynamips: – “Browse and specify the directory where dynamips.exe is located. By default it is within the GNS3 installation folder”

Working directory for Dynamips: – “Modify the path to point to the temp directory that was created within the GNS3-Folders folder”

Checked – “Automatically clean the working directory”

Unchecked – All the rest

Click on “Test settings” button and “Dynamips 0.2.xx-xxxx/Windows stable) successfully started” will be displayed in green.

iv. Edit – Preferences – Dynamips – (Hypervisor Manager)

Memory usage limit per hypervisor: – 512 MB

Checked – Allocate a new hypervisor per IOS image

Checked – Use Hypervisor Manager when importing

v. Edit – Preferences – Capture

Default Presets: – “Wireshark Live Pipe Traffic Capture (experimental) (Windows)”

Working directory for capture files: – “C:\GNS3-Folders\Capture”

Unchecked – Automatically start the command when capturing

5. Configure default IOS images and hypervisors:

From the menu bar, go to – “Edit – IOS images and hypervisors – (IOS Images)“

Common configuration for each IOS Image:

Image File: – “Browse and specify the path to IOS file”

i.

Base config:- “C:\GNS3-Folders\IOS\baseconfig.txt” – as explained in point 2.

Platform: c2691

Model: 2691

Default Ram: 256 MB

ii.

Base config:- “C:\GNS3-Folders\IOS\baseconfig.txt” – as explained in point 2.

Platform: c3600

Model: 3640

Default Ram: 256 MB

iii.

Base config:- “C:\GNS3-Folders\IOS\baseconfig.txt” – as explained in point 2.

Platform: c3700

Model: 3725

Default Ram: 256 MB

iv.

Base config:- “C:\GNS3-Folders\IOS\baseconfig.txt” – as explained in point 2.

Platform: c7200

Model: 7200

Default Ram: 256 MB

6. Configure “idle PC” value for router on first boot – this needs to be done only once for each router model

I have attached a video to this effect along with this document

  • Drag and drop the router model into the workspace.

Right click – click “Start”

Right click – click “Console”

  • Select the consol window that opens.

Press enter twice.

Wait till all on screen activity is over.

Close the console window.

  • Right click on empty space on the windows taskbar at the bottom of the screen.

Select and click on “Start Task Manager”.

Point and click on the “Performance” tab.

Take a note of the CPU Usage – percent.

  • Now in GNS3 workspace, where router is open, right click on the router.

Select and click on “Idle PC”

From the drop down list that will appear, select the value that has a  *  next to it.

If none of the values have a star, then select an average value.

Click – “Apply”

  • Take a note of CPU Usage. If it has dropped down significantly, click on “Ok”.

Otherwise repeat with other values till an acceptable CPU Usage is attained.

Shut down the router and repeat for rest of the models.

7. Malfunctioning module

I have found that the following default FastEthernet module, which is pre-configured on slot 0: on some routers, is dis-functional.

I add another FastEthernet module for connectivity and do not use the default module at all.

This module does not work properly

slot 0: GT96100-FE

8. My computers configuration:

Processor: AMD Athlone X3

Motherboard: Asus

Ram: G-Skill 12 GB

9. baseconfig.txt

!

hostname %h

!

no ip domain lookup

ip domain-name lab.local

!

parser config cache interface

!

line con 0

exec-timeout 0 0

logging synchronous

privilege level 15

length 0

no login

line aux 0

exec-timeout 0 0

logging synchronous

privilege level 15

no login

!

!

10. NM16ESW Workaround

  • I have not been able to use the NM16ESW switch module with its default settings to work as a switch
  • However, I have discovered that if the port settings at both the ends – the module and the connected device – are modified to work at half duplex and speed of 10 Mbps, the module is functional.
  • I have modified both the speed and duplex settings at the same time. However, it is very much possible that the module will work with just the modification of either one of them.

Try searching this site!