Problem with WiFi on one netbook but not the other

[silowe2012]

I have a curious problem in that I am able to connect and browse via the wireless network on one netbook using the home hub no problem, but another netbook connects the wireless network but does not allow me to browse. Curiously it works no problem on ethernet. The netbook with the problem is running Windows 7 Home Pro with Microsoft Essentials as the AV protection. The netbook without the problem is running Windows XP Home Pro with AVG.

I have tried all sorts from rolling back Windows updates, reinstalling the wireless device drivers, refreshing/flushing dns and various command prompts but nothing seems to work.

I took the netbook away and tried connecting to another wireless network and it worked straight away no problem which leads me to believe it is a dns issue with the BT connection on my netbook.

I have enclosed the IPCONFIG for both the wireless and ethernet connection in case anyone can spot anything and make suggestions...

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Samsung>ipconfig /all

Windows IP Configuration

  Host Name . . . . . . . . . . . . : Samsung-PC
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Mixed
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Realtek RTL8192E Wireless LAN
802.11n PCI
-E NIC
  Physical Address. . . . . . . . . : 00-26-B6-86-AA-8C
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . :   fe80::d578:aa58:5b09:e6a5%16(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : 03 November 2012 09:18:19
  Lease Expires . . . . . . . . . . : 04 November 2012 09:18:19
  Default Gateway . . . . . . . . . : 192.168.1.254
  DHCP Server . . . . . . . . . . . : 192.168.1.254
  DHCPv6 IAID . . . . . . . . . . . : 285222582
  DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-17-E0-DE-2A-00-24-54-3B-6C-E9

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

Ethernet adapter Bluetooth Network Connection:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Bluetooth Device (Personal Area
Network)
  Physical Address. . . . . . . . . : 0C-60-76-FF-A0-3B
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
  Physical Address. . . . . . . . . : 00-24-54-3B-6C-E9
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::5964:d9f5:c44:93d7%11(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.1.71(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : 03 November 2012 09:19:31
  Lease Expires . . . . . . . . . . : 04 November 2012 09:19:31
  Default Gateway . . . . . . . . . : 192.168.1.254
  DHCP Server . . . . . . . . . . . : 192.168.1.254
  DHCPv6 IAID . . . . . . . . . . . : 234890324
  DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-17-E0-DE-2A-00-24-54-3B-6C-E9

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

Tunnel adapter isatap.{7C28E484-E7CB-44B8-A9E7-1F985D74D99A}:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  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

[Keith_Beddoe]

Wireless connections are classed as public by default, so file sharing and network discovery is disabled.

You have to change your wireless connection so that it is in the Private network classification.

I cannot remember how to do this, as its a while since I played around with a Win 7 or Vista laptop.

Any settings only affect the actual wireless connection you change, so if you access public wifi, then that will be classed as a public network, and file sharing will be disabled.

Ethernet connections are usually assumed private.

I am sure a Google search will tell you more, if its not in Windows help.

[silowe2012]

Hi Keith,

Thanks for the post. I have this listed as my 'Home' network but I cannot see anything about it being Public or Private. I will have to do some digging to see if it can be confirmed anywhere...

Simon

[silowe2012]

Just found this...

"For Windows 7 network types, the secret lies in the GATEWAY entry. Any network you connect on that doesn't have a DEFAULT GATEWAY provided with, becomes PUBLIC and you cannot change it's type.

The solution is simple, specify the DEFAULT GATEWAY IP in the network properties and you are done."

So the question is, what is the DEFAULT GATEWAY IP for HH3 ?

[silowe2012]

Silly me, it is in the config file! (192.168.1.254)

[davem44]

I noticed in your earlier reply your router is using 802.11n to access broadband can I suggest you check the router is available on 802.11g or b as a computer  running XP is likely to have a network card with the n proticol for wifi

[davem44]

sorry just noticed that the one running is the xp but the same solution could well apply as  some later computers only have g proticol for wireless this could well explain why it connects to another network