This sounds very very familiar, as being a DHCP dynamic address assignment problem.
The Dlink router (model DIR-625, good router too) will provide LAN local addresses in the 192.168.0.1 range. When your PC boots, the router will assign your PC an address, say 192.168.0.100. Then you connect to the Internet, and the router does it’s stuff in moving packets around.
When your PC boots, and somehow can’t get an address from your router, your PC will create an address for itself, in the 169.254.0.0 range. CFP will see this as a new LAN, and Windows will tell you “limited or no connectivity”
You can check what address your PC has with an “ipconfig /all” command. Click Start → Run, and enter this
cmd /k ipconfig /all
That’s in a quote box, so you can just cut and paste into the Run. Toward the bottom of that report, is the IP Address of your PC.
If you have the 169.254.x.x address, then you will need to add this rule into CFP Global Rules. Click Firewall → Advanced, Network Security Policy, and the Global Rules tab. Then click Add, and enter this rule
Protocol: UDP # choose the protocol from the pull down list
Source Address: any
Destination Address: singleIP: 255.255.255.255
Source Port: any
Destination Port: a port range: start 67 end 68
and then move that new rule to the very top of the CFP Global Rules, so it is the very first rule on the list.
CFP normally handles DHCP address assignment correctly. But sometimes it seems to miss, and it looks like it missed in your case.
Once you have entered this new rule into CFP, you should reboot, and all should work.