One small thing puzzles me in the "\Network and Internet\Network Connections" screen. Windows 7 shows me the same network name for both the wired and the wireless network but it doesn't really make sense.I have a wireless network with an SSID like 'DNETW1'. I also have a windows workgroup called something like 'DNET1'. The computer happens to be connected with an ethernet cable at the moment (as it has been since boot). The screen mentioned above shows the 'Local Area Connection' and also the 'Wireless Network Connection' both with the wireless network name (DNETW1) in the status field. Is this expected behaviour on that screen?ThanksDavid

Hi David, Is the Ethernet connection disconnected when you connect the wireless connection? Also please capture a screenshot of the status and submit it in the SkyDrive of your Live Space. Arthur Xie - MSFT

Thanks for the reply. Ethernet has been connected all the time. The window has been captured, the status message highlighted and uploaded to my skydrive public folder here.

Hi, The JNETW1 here is the workgroup name. The entry "status" indicates the network it connects. Currently the computer connects to the workgroup JNETW1.Arthur Xie - MSFT

hi friend, If like this situation try to disable WLAN in u r computer, n try it..maybe sometimes it work becz if u want to findout problem have to check one after other. so try it .

Hi Arthur,That's just the problem, as I mentioned inmy first post,the workgoup is JNET1 not JNETW1. As I said, not a big issue, just that I think the screen is showing incorrect information against the ethernet adapter (Local Area Connection). I uploaded the screenshot showing the workgroup definition here.

hi friend, If like this situation try to disable WLAN in u r computer, n try it..maybe sometimes it work becz if u want to findout problem have to check one after other. so try it . I disabled the wireless network adapter, restarted the machineand in network properties it still shows JNETW1 as the status for the Local Network Connection - the workgroup is definitely set to JNET1 so something else is setting that status message. I think that the team now has enough info to replicate the issue if they want to see it and understand/fix it.

May be some of the related Registry key values are incorrect. There are several related keys. Is the workgroup name correct in Network and Sharing Center? You may open the following branch. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles\ There should be several profiles. One of them is the current profile. After changing the key "ProfileName", you could change the network name.Arthur Xie - MSFT

Arthur,Thanks for the info again. I checked the registry keys and can now see 3 profiles - there is a new one and it is called 'JNETW1 2'. I'm really not sure how that got created and this new oneis nowshown as the 'Active Network' in Network and Sharing Center (image here). These registry keysdo seem to be related to what is shown as the 'Active Network'. Its just that the active Network is NOT the Workgroup - maybe it is something new under Windows 7? I guess that the active network is also what is shown under the status that I originally spotted.So, maybe it is working as MS intended but not as I expected intuitively. Is the Workgroup now expected to become deprecated compared to Active Networks and Homegroups?ThanksDavid

Hi, Since only Windows 7 has HomeGroup function, in a non-domain environment with other systems, we still need Workgroup to share resources between computers. This part is not deprecated.Arthur Xie - MSFT

I think if you disconnect the Ethernet connect and then connect the wireless one, this issue will not occur. This name actually means "the second JNETW1". Now we found that it is actually the name of your Network Gateway. Is "JNETW1" the name of your wireless connection? Maybe when you connect both connections, the Ethernet connection considers the wireless connection as your gateway. Connecting two single adapters to one network device will cause network loopback. That can be the reason of this issue.Arthur Xie - MSFT