No network connection after using Stealth Ports Wizard (DHCP Broken)

Q:
After using Stealth Ports Wizard i lost my network connection, how is that possible ?
CIS also detected a new private network in the range 169.254.x.y

A:
Most common cause is that you blocked DHCP traffic from functioning.
DHCP is a mechanism that allows Routers to provide PC's with an IP Address and other details on how to connect to the network.

More information about DHCP can be found here

How to fix this ?

1)
Determine if your configuration is using DHCP.
Open a command-box (Start, Run, cmd) and type ipconfig /all
Output should look like this:

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : <YOUR COMPUTER NAME>
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : <your domainname>

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : <your domainname>
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : AA-BB-CC-XX-YY-ZZ
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : a.b.c.d
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : a.b.c.e
DHCP Server . . . . . . . . . . . : a.b.c.d
DNS Servers . . . . . . . . . . . : a.b.c.d
Primary WINS Server . . . . . . . :
Lease Obtained. . . . . . . . . . : Friday, June 01, 2009 0:00:00 PM
Lease Expires . . . . . . . . . . : Friday, July 02, 2009 0:00:00 PM

Check to see if DHCP Enabled = YES then your using DHCP to get an IP Address.

2)
Check the Firewall logging to see if the traffic was blocked.
Go to Firewall, View Firewall Events, and check if there is traffic blocked:

Action: Blocked
Protocol: UDP
Source Port: 67
Destination: 255.255.255.255
Destination Port: 68

3)
Create a global rule to fix the problem.
Go to Firewall, Advanced, Network Security Policy, Global Rules and click on [Add..]

Action: Allow
Protocol: UDP
Direction: In
Description: <leave empty>

Source Address: Any
Destination Address: 255.255.255.255
Source Port: A Single Port 67
Destination Port: A Single Port 68

Then press [Apply] and [Move Up] to set this as the first rule, press [OK] and go back to the command-box, now type ipconfig /renew, and DHCP should be fully functioning again.

Screen shots attached