From: "Will Honea" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.16) with ESMTP id 2363833 for os2-wireless_users@2rosenthals.com; Tue, 17 Mar 2009 00:36:11 -0400 Received-SPF: pass (secmgr-ny.randr: domain of eigbox.net designates 66.96.190.14 as permitted sender) client-ip=66.96.190.14; envelope-from=SRS0=hayFUP=7Q=whonea.net=whonea@eigbox.net; helo=bosmailout14.eigbox.net; Received: from bosmailout14.eigbox.net ([66.96.190.14]) by secmgr-ny.randr with esmtp (Exim 4.43) id 1LjR23-00062g-Vv for os2-wireless_users@2rosenthals.com; Tue, 17 Mar 2009 00:36:07 -0400 Received: from bosmailscan02.eigbox.net ([10.20.15.2]) by bosmailout14.eigbox.net with esmtp (Exim) id 1LjR1i-0001tw-E5 for os2-wireless_users@2rosenthals.com; Tue, 17 Mar 2009 00:35:42 -0400 Received: from bosimpout01.eigbox.net ([10.20.55.1]) by bosmailscan02.eigbox.net with esmtp (Exim) id 1LjR1i-0000aQ-3i for os2-wireless_users@2rosenthals.com; Tue, 17 Mar 2009 00:35:42 -0400 Received: from bosauthsmtp12.eigbox.net ([10.20.18.12]) by bosimpout01.eigbox.net with NO UCE id U0BL1b0020FdZ9W0000000; Mon, 16 Mar 2009 20:11:20 -0400 X-EN-OrigOutIP: 10.20.18.12 X-EN-IMPSID: U0BL1b0020FdZ9W0000000 Received: from 168-103-251-129.clsp.qwest.net ([168.103.251.129] helo=main) by bosauthsmtp12.eigbox.net with esmtpa (Exim) id 1LjR1W-0000ez-15 for os2-wireless_users@2rosenthals.com; Tue, 17 Mar 2009 00:35:30 -0400 Date: Mon, 16 Mar 2009 22:35:28 -0600 To: "OS/2 Wireless Users Mailing List" Reply-To: "Will Honea" In-Reply-To: References: Subject: Re: [OS2Wireless] WIFI LOGON PROBLEM MIME-Version: 1.0 X-Mailer: The Polarbar Mailer; version=1.25d; build=2006 X-Mailer-Platform: Linux; architecture=amd64; version=2.6.27.19-3.2-default X-Mailer-Java-VM: Sun Microsystems Inc.; version=1.6.0_0; compiler=null X-EN-UserInfo: b0192109012588bf2b05ebe482b26736:f259605ce5aa1fb891467026511a1cfb X-EN-AuthUser: whonea@whonea.net Sender: "Will Honea" X-EN-OrigIP: 168.103.251.129 X-EN-OrigHost: 168-103-251-129.clsp.qwest.net X-Spam-Score: 0.0 (/) X-Spam-Report: _SUMMARY_ Message-ID: ** Reply to message from "Jeffrey Race" on Mon, 16 Mar 2009 21:15:37 -0500 > Sometimes I find I have to reboot my computer before I can connect to > a wireless network, after changing out my LAN card. (Running W2K.) > Why would this be so? (I see sometimes my Tinywatcher program > says the domain changes e.g. I was at a hotel it was e-centre.net and > at home it is cable.rcn.com). Is there a command or option I can > use so I don't have to reboot? What can I read to educate myself > about this problem? Your message was not exactly clear about who was connecting to what. If you change a LAN card (wired ethernet) you have to reboot after you set up the card for the system - the system has to load and bind the correct info or the card. If you are talking about the wireless not connecting, you usually have to tell the system to re-scan the available networks before it picks up a new one then select the one you want to connect to. Most machines I work with are configured to re-connect to the last AP used if available and require some manual intervention most of the time to get the one you really want. The comment about the LAN card is confusing - I would assume you are talking about a notebook which makes swapping LAN cards a bit problematic (to say the least) unless the LAN card is a USB or PCMCIA device. If you swap PCMCIA cards in mid-session then getting things to work is also a crap shoot - same reasoning as with ethernet cards as most systems have issues with changing network hardware after bootup. Many wireless devices, for example, don't properly initialize after bootup. -- Will Honea