Poštni seznam arhiviranih sporo?il

Od:	"Carl Gehr" <os2-wireless_users@2rosenthals.com>	Glava Izvorno E-sporo?ilo
Pošiljalec:	os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Zadeva:	OS/2 Wireless Users List: MPTS and wireless NIC
Datum:	Sat, 12 Apr 2003 14:12:56 est5edt
Za:	"os2-wireless_users@2rosenthals.com" <os2-wireless_users@2rosenthals.com>

On Sat, 12 Apr 2003 10:55:48 est5edt, Neil Waldhauer wrote: >Now that I have the wireless NIC working, I'm going to have to get both the >built-in NIC and the wireless NIC to work together. > >For my first test, I just changed the built-in Intel NIC driver to the AmbiCom >Prism driver, and all went well. Should I configure the wireless NIC as a >second NIC? > >I want to use DHCP on whichever NIC gets a network. How can I configure that? > >Neil Great comments and questions, Neil. I have experienced similar items. But, let me provide some specific details that may encourage more detailed responses from those who are *know* what is correct. First, the specific configuration that I am trying to make operational: * TPad A30p built-in: - LAN0: Intel PRO PCI [E100BEO2 driver] - LAN1: 802.11b [PRISM driver] * MPTS Configuration specs Both LAN0 and LAN1: - TCPIP - NETBIOS LAN0: - Interface Enabled - DHCP [n/a on any other LANn...] - DDNS is not selected. LAN1: - Interface *not* enabled, because it insists on having a MANUAL IP Address and Subnet Mask. I have no idea what to specify here. Maybe if I could resolve this issue the rest would fall into place. * TCP/IP Configuration Issues: - For some reason, I cannot change the DHCP to anything other than LAN0. Therefore, in order to activate the WLAN, I have had to go into MPTS and change the Adapter Numbers on the two adapters. Just to anticipate the question: Even if I remove the selection of DHCP on LAN0, I cannot select it on LAN1. - I have not been able to make both NICs active at one time. [See LAN1 comments above.] i.e., I would like to be able to just turn the system on and have the adapter that finds a signal take over with DHCP using the connection that becomes active. - When I did switch the two adapter numbers around so that LAN0 was the Wireless, the only time I have ever been able to actually make a connection is when I was able to specifically identify a Network ID (SSID) that matched the known ID of a predefined WLAN. AND, I also had to specify the KNOWN DNS for that network in the MPTS "Host Names" section. - Only if I had the Wireless Adapter 'active' when the system was booted, did the DHCP actually find/assign an IP address. In all other cases, the DHCP Monitor always shows the IP Address as "Not Registered." Killing the DHCP and restarting it followed by Action->Request-Lease does not seem to work with the wireless as it does with the Ethernet. I think I have covered all of the conditions and configuration issues that I have seen. Hopefully, this will allow someone who really understands how to set this up to provide a "Wireless for Dummies" response for those of us who can follow detailed directions, but are not network savvy enough to figure things out for ourselves. [Now, maybe that does not apply to Neil, but it does to me.] Thanks in advance, Carl =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To unsubscribe from this list, send a message to steward@2rosenthals.com with the command "unsubscribe os2-wireless_users" in the body (omit the quotes). For help with other commands, send a message to steward@2rosenthals.com with the command "help" in the body (omit the quotes). =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Naro?iti: Poro?ilo (Feed), Izvle?ek (Digest), Indeks.
Odjava
E-pošta za mojstra za sezname