Netsh cannot connect to unsecured network
Hi all, I have a question about the netsh command. I looked everywhere but nobody seems to have my problem. For the moment if i do "netsh wlan show profiles" i see my current network under the section user profiles. It's there because i connected through the UI. But I can, if not already connected, also connect to it through "netsh wlan connect name=MyNetwork" Now i have a second wireless network at home, not secured. but if i want to connect by "netsh wlan connect name=MyNetwork2" then it returns an error: There is no profile "MyNetwork2" assigned to the specified interface . It's true, there is no profile. But this is a unsecured network and through the UI, I just can connect to it. What am I doing wrong? How can i connect through command to that network? Thanks in advance!! FireWall
May 3rd, 2009 4:07pm

Hi, Thank you for your post. Based on my research, I suspect that the error message means that the profile MyNetwork2 doesnt exist. Therefore, you may create the profile first. To do this, please refer to the section add profile in the following document: Netsh Commands for Wireless Local Area Network (WLAN) Preliminary] http://technet.microsoft.com/en-us/library/cc755301.aspx#bkmk_wlanConn Hope this helps. Thanks.Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2009 1:40pm

First of all thanks for your reply! Adding the profile would maybe indeed solve my problem. But I came across the next problem. Like in your document: add profile filename=C:\Users\WirelessUser\Documents\profile1.xml interface="Wireless Network Connection" add profile filename="C:\Wireless Profiles\WiFi Profile.xml" interface=w but where do I get the .xml file from, because without it wont create the profile? it is a required parameter. and the next thing i was thinking about, why does vista via the ui not create a profile if i connect to the unsecured network? Pieter
May 5th, 2009 5:37pm

Hi, Thank you for your update. Based on my research, I found that the Wireless Network Profile should be shown in Manage Wireless Networks. To open Manage Wireless Networks, please go to "Network and Sharing Center and click the link Manage wireless networks on the left side of the window. Please check if the unsecured network exists. For more information, please refer to the following document: Connecting to Wireless Networks with Windows Vista http://technet.microsoft.com/en-us/library/bb878035.aspx Hope this helps. Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2009 12:36pm

This is a way to do it through the UI, but i'm searching to do it through a command line like for instance with netsh. I'm starting to think that it is just not possible :( I shall have to find an another way to connect to it. My final purpose for this all, was to use it through C# code. But I guess i have to keep looking for an other utility to connect :)
May 6th, 2009 12:45pm

Hi, After researching based on the document: Netsh Commands for Wireless Local Area Network (WLAN) in Windows Server 2008 http://technet.microsoft.com/en-us/library/cc755301.aspx#bkmk_wlanConn I get the following information: If only one SSID is specified in the profile, then the specified SSID is used to connect, and the ssid parameter is not required. If the profile specifies multiple SSIDs, the ssid parameter is required. Therefore, I think the SSID of the unsecured wireless network exists as one of the items included in your Wireless Network Profile and we may have no need to create another new profile for the unsecured wireless network. Therefore, to connect the unsecured wireless network, we may use the command netsh as netsh wlan conncet ssid=[Your SSID of the unsecured wireless network] name=[Your current profile name]. Please refer to the section connect [[ssid=]WirelessNetworkName] name=ProfileNameinterface=InterfaceName. Hope this can be helpful. Thanks.Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2009 10:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics