Hi There,
I have a wireless network comprising of a PlusNet router, a pair of Belkin Powerline HD Gigabit mains Ethernet adaptors and a Samsung BD-E8500M (set up as an access point).
I have a HP Laptop (Windows XP), several mobile phones, Kindle etc etc etc that can all connect to either the Plusnet wireless OR the Samsug Wirless networks.
I also have a NEW Compaq laptop (called FIDGE) that connects fine to the Plusnet network BUT WILL NOT CONNECT reliably to the the Samsung network. Reliably needs some more explanation! The Compaq has sometimes connected successfully and worked (but not since Sunday last week (8 days ago)).
It did have a trial Norton installed which has expired (maybe last Sunday). I have since uninstalled Norton and run the Norton removal tool.

When clickingon the network signal strength icon, it shows the Plunsnet network (but at a strength too low to be usefull (hence the second access point) - we have very thick walls- and sometimes Samsung. If you try to connect to this network it "CHECKS THE NETWORK REQUIREMENTS" and comes back with "the connection is limited". I have been round and round in cirles with the Windoms * help system without any success.

After the above the compaq aprears to be connected to the access point, but it says "No Internect access".
IPCONFIG/ALL now shows:-

C:\Users\BB>ipconfig/all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : fidge
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : local

Wireless LAN adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 68-94-23-17-55-B2
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi:

   Connection-specific DNS Suffix  . : local
   Description . . . . . . . . . . . : Ralink RT5390R 802.11bgn Wi-Fi Adapter
   Physical Address. . . . . . . . . : 68-94-23-17-55-B0
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3947:1535:69a7:b82d%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.12.129(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 02 April 2013 10:42:44
   Lease Expires . . . . . . . . . . : 03 April 2013 21:37:35
   Default Gateway . . . . . . . . . : 192.168.12.1
   DHCP Server . . . . . . . . . . . : 255.255.255.255
   DHCPv6 IAID . . . . . . . . . . . : 342397987
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-10-74-89-10-60-4B-4A-C5-85

   DNS Servers . . . . . . . . . . . : 0.0.0.0
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physical Address. . . . . . . . . : 10-60-4B-4A-C5-85
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.local:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : local
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


Any help would be greatfully received, as this is driving me potty!!!

Thanks in anticipation.
Rob

Very often this is caused by optional update. Reinstall driver from computer vendor.

Regards

Milos

• Marked as answer by Juke ChouMicrosoft contingent staff, Moderator Sunday, April 28, 2013 3:40 PM

Check if the WiFI Native Filter Service is installed:

Add the Native WiFi Filter SERVICE in the properties of the wireless adapter

http://cloudtidings.com/2015/05/19/solved-wireless-not-connecting-after-installing-windows-server-tp2/