Problem with Windows 98 logging onto wireless network

Question

I have a unique issue that I am having some issues trying to fix. I have a
PC that is running Windows 98SE that connects to the network via a Cisco
Aironet 350 wireless card. I removed this card from another PC and it was
working fine a week and a half ago. I place this card in the other PC and
install the drivers and Novell Client 3.40 and I can't log onto the
network. The PC can associate to the AP though. I can also put in a regular
10/100 ethernet card and get on the network. We use 128-bit WEP encryption.
I have checked my WEP key and it's correct. I have set the client
properties based on another PC that is connected so that shouldn't be the
issue. I have 15 other PC's with the same card and client version that are
getting on the network just fine. Also when we look at our AP through the
web interface, in a column where it usually lists the authenticated
machine's IP addresses, it only says Unassigned for this machine. I am at a
loss of where to go next with this issue. I have been looking around not
only Novell's site but Cisco's as well and no dice there.I would truly
appreciate any help anyone could give me.
Thank You
Jami Benson

Answer 1

On Thu, 25 Jan 2007 14:43:12 GMT, [email protected] wrote:
>> On Wed, 24 Jan 2007 22:10:10 GMT, [email protected] wrote:
>>
>> >I have a unique issue that I am having some issues trying to fix. I have a
>> >PC that is running Windows 98SE that connects to the network via a Cisco
>> >Aironet 350 wireless card. I removed this card from another PC and it was
>> >working fine a week and a half ago. I place this card in the other PC and
>> >install the drivers and Novell Client 3.40 and I can't log onto the
>> >network. The PC can associate to the AP though. I can also put in a regular
>> >10/100 ethernet card and get on the network. We use 128-bit WEP encryption.
>> >I have checked my WEP key and it's correct. I have set the client
>> >properties based on another PC that is connected so that shouldn't be the
>> >issue. I have 15 other PC's with the same card and client version that are
>> >getting on the network just fine. Also when we look at our AP through the
>> >web interface, in a column where it usually lists the authenticated
>> >machine's IP addresses, it only says Unassigned for this machine. I am at a
>> >loss of where to go next with this issue. I have been looking around not
>> >only Novell's site but Cisco's as well and no dice there.I would truly
>> >appreciate any help anyone could give me.
>> >Thank You
>> >Jami Benson
>> By any chance does your Netware network use IPX? (You did say this
>> card was working, but was it for Netware and TCP/IP)
>> Does your system get a IP address? Is it in the same range as other
>> systems?
>> Is the NW client BOUND to the aeronet card?
>>
>Steve,
> We don't use DHCP. We manually assign IP addresses. We do use IPX on the
>network, but it is really only used for printing with the print queues we
>have set up. As to the NW client being bound to the Aironet card, I'm not
>100% sure what you mean. I apologize about that. I am fairly new to
>Netware.
Bound applies to Protocols in general. (W9x versions, Not XP)
Open "Network". (You can right click "Network Neighborhood", select
Properties or use the control panel)
Inspect the "Properties" for each adapter listed on the Configuration
Tab.
Do Not change anything at this time, and ALWAYS choose CANCEL for
safety . Once you have it figured, you will make and save changes :)
There are 3 groups of entries. Clients,Services,Protocols.
You choose to "Bind" a particular protocol(s) to a adapter(part of the
Adapters properties).
Not all protocols need be bound to the SAME adapter (nor is it
desired). Example: Bind PPOE to dial-up, TCP/IP to the Wireless
adapter, IPX to the 10-100T WIRED adapter. << Example, do NOT really
do this.
802.11 wireless DOES NOT support the IPX protocol. If your printers
use IPX (only), then you will need a Print Queue on the server for
that printer and PRINT to that PRINT Q from the wireless (or IP only)
devices.
Ah!
> Also just as a point of interest, if I remove the Novell client
>and use strictly IP with the wireless card in, I still can't get the PC
>connected to either the network nor the internet. I guess I'm saying I'm
>saying I'm not 100% that this is a Novell issue.
Start with getting a Internet connection to work.
That will also indicate that TCP/IP is working.
When you don't use DHCP, you have to do everything (settings)
yourself, CORRECTLY :^)
IP (no clash with existing stations)
Subnet mask, same as every one else on the network.
Gateway the A/P
DNS as needed, one should be your ISP's suggested.
Is the A/P correctly configured for your Non-DHCP network?
*AND* are you sure you have the proper adapter drivers for W98(se)????
>Let me know what you
>think. Thanks for the help so far.
>
>Jami Benson