Solutions: Windows 8 WiFi Limited / Windows can't communicate with the device or resource (Primary DNS Server)

(To check only solutions quickly, then see last two lines.

There are two wireless routers on 1st and 2nd floor of my company.

One coworker who used 2nd fl. router so far moved down to 1st fl. and a disaster began...
with his saying internet doesn't work in his laptop.

When I tried to connect to 1st fl. router, I met the next.

Msg of horror and terror:
"Windows can't communicate with the device or resource (Primary DNS Server)"

"Limited" & "No Internet"
on Network and Sharing Center dialog of Windows 8


Okay, it's not the first time of my computing history. It happened before with Windows 7 and Windows XP too, and I have figured it with resetting Profiles of Wireless Connections in Windows.

How to do it in Windows 8, let's search after I connect to 2nd fl router...

Same msg! What?! Kidding me?
I could use it before without any problem and now it spits the same msg?


Easy, easy...
of course there should be some way to flush Windows' wireless profiles in 8 too.

Tried this solution (#2) and I could successfully connect to 2nd fl. router.

Yup! Good, good. Now I connect to 1st fl. and, the, same, m,s,g......

"Windows can't communicate with the device or resource (Primary DNS Server)"
"Limited" & "No Internet"
on Network and Sharing Center dialog of Windows 8

Hell.... well, all is well, all is well...

I disconnected from 2nd fl router, and repeated #2 solution again, and...
same msg!!


Okay! I will just fix it by myself,
with a very direct way.

I opened Wireless Connection Properties of 1st fl router, and
I opened Internet Protocol Version 4 (TCP/IPv4) Properties, and
clicked Advanced... button, and
moved to DNS tab, and
typed the proper IP address (i.e., 192.168.0.1) in Primary DNS IP address blank, and
left the secondary DNS blank empty,
OK, Apply, OK, OK, ...


Tada~!!
It works super fine now.



Solutions:
#1 Typing a proper IP address of wireless router in Primary DNS's IP address blank. (usually it is 192.168.0.1 without the network administrators customizing)
#2 http://www.fixedbyvonnie.com/2013/10/how-to-fix-limited-or-no-connectivity-wi-fi-issues-in-windows-8/#.V5Co6fmrhBc


Thanks a lot, Vonnie.

Apache Issues of upgrading Ubuntu Server 12.04 LTS to 14.04 LTS

After '# do-release-upgrade' from Ubuntu Server 12.04 LTS to 14.04 LTS

On the dialog of grub setting, I just typed Enter with the default selection of hdd choice.

And, it failed to boot after the dist upgrade and went into its rescue mode.

I googled but couldn't find an exact same case, but it's... grub. Yes, GRUB. ... 2 actually.

I have RAID0 (mirroring) arrayed by mdadm with two of 500GB WD hard drives. So I did it with sdb too.

$ sudo grub-install /dev/sda
$ sudo grub-install /dev/sdb
$ sudo update-grub 

Reboot, and problem solved.


Apache2 couldn't run itself after the upgrade.

    $ sudo service apache2 status

So it was not running.

    $ sudo service apache2 start


It showed me some error msg about the reason, but definitely it's caused by the upgrade. Yes, I chose 'Keep current settings' when the new apache2 installation process asked me what to do.

    $ cd /etc/apache2
    $ mv apache2.conf apache2.conf.old

apache2.conf is my old setting and wasn't compatible perfectly to run new apache2. Of course there was a kind skeleton file for that, 'apache2.conf.dpkg-dist'.

    $ mv apache2.conf.dpkg-dist apache2.conf
    $ sudo vi apache2.conf

I added a line for phpmyadmin, one more for the ServerName at the end of the conf file.

    Include /etc/phpmyadmin/apache.conf
    ServerName www.mywebsite.com

When I started apache2 service again, it worked the same as before.