up vote 4 down vote favorite
2
share [g+] share [fb]

I use a wired connection at home and BTFON (unsecured wireless) when out and about. Unfortunately one wireless network has become inextricably linked to my wired network and does not come up as a seperate connection so I cannot change it's location from "Home" to "Public" without also changing the location of my wired connection. Other wireless networks can be treated as separate connections/locations so it is most likely something I've clicked on or changed.

I have tried the following:

  • Renaming the connections
  • Removing the Wireless network
  • Clicking on the icon in active networks and deleting all network locations
  • All the above as an administrator
  • System Restore
  • @Revolter's answer
  • Removal/reinstall of drivers
  • Route delete 0.0.0.0

How it looks now:

 enter image description here

How it should look:

enter image description here

How can I split these two networks?
Edit1: Don't know if this is relevant but when I connect to BTFON, it renames the wired connection to BTFON.
Edit2: Some more info; As I understand it, Windows stores wireless profiles here:- c:\ProgramData\Microsoft\Wlansvc\Profiles\Interfaces\ but it has not created an entry for the BTFON connection.
N.B. The route delete command seemed to work but I had forgotten to reboot, once I rebooted, the networks rejoined under one connection.

ipconfig /all (wired and normal wireless showing as 2 separate connections) 

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

C:\Windows\system32>ipconfig /all   

Windows IP Configuration   

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

Wireless LAN adapter Wireless Network Connection:   

Connection-specific DNS Suffix  . : home   
Description . . . . . . . . . . . : 802.11n Wireless LAN Card   
Physical Address. . . . . . . . . : 00-FF-4F-9A-FF-FE   
DHCP Enabled. . . . . . . . . . . : Yes   
Autoconfiguration Enabled . . . . : Yes   
Link-local IPv6 Address . . . . . : fe80::7d21:d660:9f2b:b507%19(Preferred)   
IPv4 Address. . . . . . . . . . . : 192.168.1.71(Preferred)   
Subnet Mask . . . . . . . . . . . : 255.255.255.0   
Lease Obtained. . . . . . . . . . : 09 September 2011 16:11:55   
Lease Expires . . . . . . . . . . : 10 September 2011 16:15:38   
Default Gateway . . . . . . . . . : 192.168.1.254   
DHCP Server . . . . . . . . . . . : 192.168.1.254   
DHCPv6 IAID . . . . . . . . . . . : 520095311   
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-AF-2E-6E-00-22-15-63-BB-6F   
DNS Servers . . . . . . . . . . . : 192.168.1.254   
NetBIOS over Tcpip. . . . . . . . : Enabled   

Ethernet adapter Eth0:   

Connection-specific DNS Suffix  . : home   
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller   
Physical Address. . . . . . . . . : 00-FF-15-63-FF-43   
DHCP Enabled. . . . . . . . . . . : Yes   
Autoconfiguration Enabled . . . . : Yes   
Link-local IPv6 Address . . . . . : fe80::f878:79e9:1495:b402%11(Preferred)   
IPv4 Address. . . . . . . . . . . : 192.168.1.69(Preferred)   
Subnet Mask . . . . . . . . . . . : 255.255.255.0   
Lease Obtained. . . . . . . . . . : 09 September 2011 16:11:21   
Lease Expires . . . . . . . . . . : 10 September 2011 16:11:21   
Default Gateway . . . . . . . . . : 192.168.1.254   
DHCP Server . . . . . . . . . . . : 192.168.1.254   
DHCPv6 IAID . . . . . . . . . . . : 301998613   
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-AF-2E-6E-00-22-15-63-BB-6F   
DNS Servers . . . . . . . . . . . : 192.168.1.254   
NetBIOS over Tcpip. . . . . . . . : Enabled   

Tunnel adapter isatap.home:   

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

Tunnel adapter Local Area Connection* 9:   

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   
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:28ef:b2d:a97f:6159(Preferred)   
Link-local IPv6 Address . . . . . : fe80::28ef:b2d:a97f:6159%12(Preferred)   
Default Gateway . . . . . . . . . : ::   
NetBIOS over Tcpip. . . . . . . . : Disabled

ipconfig /all (wired connection and BTFon showing under one connection) 

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

C:\Windows\system32>ipconfig /all   

Windows IP Configuration   

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

Wireless LAN adapter Wireless Network Connection:   

Connection-specific DNS Suffix  . : home   
Description . . . . . . . . . . . : 802.11n Wireless LAN Card   
Physical Address. . . . . . . . . : 00-FF-4F-9A-FF-FE   
DHCP Enabled. . . . . . . . . . . : Yes   
Autoconfiguration Enabled . . . . : Yes   
Link-local IPv6 Address . . . . . : fe80::7d21:d660:9f2b:b507%19(Preferred)   
IPv4 Address. . . . . . . . . . . : 11.246.159.104(Preferred)   
Subnet Mask . . . . . . . . . . . : 255.255.255.248   
Lease Obtained. . . . . . . . . . : 09 September 2011 16:24:03   
Lease Expires . . . . . . . . . . : 09 September 2011 16:40:43   
Default Gateway . . . . . . . . . : 10.246.159.113   
DHCP Server . . . . . . . . . . . : 10.246.159.113   
DHCPv6 IAID . . . . . . . . . . . : 520095311   
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-AF-2E-6E-00-22-15-63-BB-6F   
DNS Servers . . . . . . . . . . . : 192.168.22.22   
                                    192.168.22.23   
NetBIOS over Tcpip. . . . . . . . : Enabled   

Ethernet adapter Eth0:   

Connection-specific DNS Suffix  . : home   
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller   
Physical Address. . . . . . . . . : 00-FF-15-63-FF-43   
DHCP Enabled. . . . . . . . . . . : Yes   
Autoconfiguration Enabled . . . . : Yes   
Link-local IPv6 Address . . . . . : fe80::f878:79e9:1495:b402%11(Preferred)   
IPv4 Address. . . . . . . . . . . : 192.168.1.69(Preferred)   
Subnet Mask . . . . . . . . . . . : 255.255.255.0   
Lease Obtained. . . . . . . . . . : 09 September 2011 16:11:21   
Lease Expires . . . . . . . . . . : 10 September 2011 16:11:21   
Default Gateway . . . . . . . . . : 192.168.1.254   
DHCP Server . . . . . . . . . . . : 192.168.1.254   
DHCPv6 IAID . . . . . . . . . . . : 301998613   
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-AF-2E-6E-00-22-15-63-BB-6F   
DNS Servers . . . . . . . . . . . : 192.168.1.254   
NetBIOS over Tcpip. . . . . . . . : Enabled   

Tunnel adapter isatap.home:   

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

Tunnel adapter Local Area Connection* 9:   

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   
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:20d5:99e:a97f:6159(Preferred)   
Link-local IPv6 Address . . . . . : fe80::20d5:99e:a97f:6159%12(Preferred)   
Default Gateway . . . . . . . . . : ::   
NetBIOS over Tcpip. . . . . . . . : Disabled
link|improve this question
@Gareth, was that just a layout change? I cannot see a difference in the content. – Tog Sep 3 '11 at 14:25
Hi @Tog - it was primarily minor formatting changes, such as adding the bullet points for the approaches you had already tried. – Gareth Sep 3 '11 at 14:42
2  
Would be a good idea to also post the result of "ipconfig /all". – harrymc Sep 5 '11 at 11:06
1  
@Tog - I would be happy to give it a try... Would it be possible to come on to chat at some point and @ me - if you want to do remote support, I will be happy to try and directly help you! – William Hilsum Sep 5 '11 at 13:15
@harrymc here's the ipconfigs The first is wired and wireless working as two separate connections, one location is home the other one is work. The second is for wired and BTFON, which show as one connection so the location has to be manually changed every time I connect. – Tog Sep 9 '11 at 15:43
show 1 more comment
feedback

4 Answers

up vote 3 down vote

The wired and wireless interface shouldn't be on the same gateway. it looks like they do. what follow should reset everything and you will have to setup your network again.

use netsh to reset both Winsocks entries and the TCP/IP stack

netsh winsock reset
netsh interface ip reset

Then clear the routing table to make sure you don't are having a conflicting one, using:

route /f

this will let you perform a clean setup assuming the network location are already cleared.

reboot and reconfigure your IP settings and networks locations

Updates:

You can manage Network Profiles from here

Control Panel > Classic View > Network and Sharing Center > Customize > Merge or delete network location

Highlight the network then click Delete.

But what I think you clicked on by mistake is this check-box :

enter image description here

To reset this option goto : HKLM\System\CurrentControlSet\Control\Network\NetworkLocationWizard and delete the key HideWizard

link|improve this answer
This made no difference. – Tog Sep 5 '11 at 17:07
"But what I think you clicked on by mistake is this check-box :" No, I did the correct one. – Tog Sep 9 '11 at 18:23
1  
This window should popup when you connect to different networks (assuming you have cleared all the previous configs) it make sense to see all the location set to public when this setting is checked. can you please check if that key is present the registry ? – Revolter Sep 10 '11 at 11:42
The key is not present in the registry. – Tog Sep 10 '11 at 13:48
@Tog: It's only present afterwards. – Tom Wijsman Sep 10 '11 at 15:34
show 3 more comments
feedback
up vote 0 down vote

What you may need to do is delete the connection that you don't want counted as a Public Network.

To do that, click the icon for the public networks (the park bench.)

Network and Sharing Center

Click Merge or delete network location. Select and delete the network that needs to be re-classified.

Merge or delete network location

The next time you connect to that network you'll be asked to re-classify it.

Re-classify

n.b. the network needs to be disconnected (not in use on the merge or delete screen) in order to delete it.

link|improve this answer
Please see the third bullet point in my original post. I have already tried that, when I reconnect to the WAP it rejoins to the wired connection. – Tog Sep 5 '11 at 8:20
@Tog, try deleting all of the listed locations. Should get rid of any possible ties between them. – Windos Sep 5 '11 at 8:26
Sorry, that's what I did originally, I've edited the question. – Tog Sep 5 '11 at 8:42
feedback
up vote 0 down vote

The safest method would be to do system restore to a date before this happened.

If you cannot restore the system, try first the answer of @Revolter.

If this does not help, you could :

  • run a chkdsk /f /r to make sure you don’t have any disk errors
  • run sfc /scannow to validate your system files
  • install latest network drivers
  • Do a Repair Install

Create another system recovery point before starting, and make sure you have backups.

(I hesitate to remark that I have seen cases where Windows required total reinstallation to recover from network errors.)

link|improve this answer
I'm not happy about deleting registry keys without more information on what they contain and what they will affect, care to expand? System restore made no difference. Repair Install will lose too many tweaks and settings to be a viable option. – Tog Sep 5 '11 at 13:03
(1) It is quite incredible that a prior restore point has not restored the network state. You might need to go still more backwards in time. (2) The above registry entries contain all winsock data, and if you want to be sure, you can export them before deleting and compare after the boot the new and old. – harrymc Sep 5 '11 at 13:12
I went back to a Microsoft update prior to the first time I connected to the BTFON WAP. – Tog Sep 5 '11 at 13:21
I still have a logical problem with this, since Windows keeps all network info in the registry, and system restore rewrites the registry. – harrymc Sep 5 '11 at 13:27
Thank God for reg backup. After deleting the keys, nothing worked at all. Even Revolter's stuff had no effect. Weirdly, I couldn't change the network location or name until after I imported the backup. – Tog Sep 5 '11 at 14:12
show 11 more comments
feedback
up vote 0 down vote
+250

Did some further research, your profiles are listed in:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

Set Category of your profile to 1 to have Home/Work and to 0 to have Public.

In

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures

it might be interesting to search your profile and look at the DnsSuffix and FirstNetwork values.

This should be enough to split them; if not, check the other values in these keys.

Or search the XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX or the signature through the registry...

link|improve this answer
There are only 2 profiles present, one is the wired connection which doesn't make any mention of the wireless adapter and the other is the good wireless connection. Those other keys don't give any results using ctrl+f find. I deleted the profiles, rebooted and set up the networks from scratch, same old problem. – Tog Sep 12 '11 at 21:56
OK, the bounty goes here, I'm not happy with any of the answers given to date but this one is, at least, heading me off in a new direction. – Tog Sep 12 '11 at 22:05
@Tog: You don't need to build them from scratch. You need to make them have a separate home/work/public in the registry. I used Process Monitor to localize these keys, filtering by write actions... – Tom Wijsman Sep 13 '11 at 2:50
I'll give that a go – Tog Sep 13 '11 at 6:51
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.