HELP!!!
joke
though i need some wireless guru's help.
We have a lot of wireless accesspoints (artem Onair) and client radio cards (artem - chipset XG901 & prism- chipset XG902) in Windows XP, Windows 2000 and Windows 98 PCs.
XG901 are present in all 98+2K machines, and a few XP machines.
XG902 is present in XP machines only.
We dont use DHCP, each PC has a static IP.
Both cards are recognised under wXP as being a FEC wireless card, I have found the PnP ID to check which is which.
The problem we have is that since the manufacturer has stopped making XG901 chipset based cards and have 'imposed' upon us the XG902 chipset, we have random wireless crashes.
The symptoms are:
Wireless AP working, but a PC can not connect. Restarting the AP is the only way to allow the card to connect.
Card connecting and disconnecting.... we have to disable and re-enable the card in networks connections to make the card connect.
We have a lot of APs, and there are other APs that have been deployed of Cisco brand to handle other wireless connections, and their broadcast zones obviously interfere with our APs.
Since these bases have been deployed, we have has an increase of disconnection problems, but the problem existed before the deployment.
I will check and comapre functionality (nitro, rts etc) that exists and is enabled on each type of card and Onair AP. The
APs have mostly the same firmware... a recent update stopped all the XG901 cards from being able to connect to the AP that had been updated......
This is in a Factory environment, and so wireless is not recommended, but it is not really an option to change this... and the data we are losing when the base/card crashes is a risk to production.
I am MCSE 2K3, so if anyone has any Windows-based ideas too, I am more than open to them.
Please help if you have any suggestions.
David
Aftertaf
Sometimes it just needs a good kicking.
joke
though i need some wireless guru's help.
We have a lot of wireless accesspoints (artem Onair) and client radio cards (artem - chipset XG901 & prism- chipset XG902) in Windows XP, Windows 2000 and Windows 98 PCs.
XG901 are present in all 98+2K machines, and a few XP machines.
XG902 is present in XP machines only.
We dont use DHCP, each PC has a static IP.
Both cards are recognised under wXP as being a FEC wireless card, I have found the PnP ID to check which is which.
The problem we have is that since the manufacturer has stopped making XG901 chipset based cards and have 'imposed' upon us the XG902 chipset, we have random wireless crashes.
The symptoms are:
Wireless AP working, but a PC can not connect. Restarting the AP is the only way to allow the card to connect.
Card connecting and disconnecting.... we have to disable and re-enable the card in networks connections to make the card connect.
We have a lot of APs, and there are other APs that have been deployed of Cisco brand to handle other wireless connections, and their broadcast zones obviously interfere with our APs.
Since these bases have been deployed, we have has an increase of disconnection problems, but the problem existed before the deployment.
I will check and comapre functionality (nitro, rts etc) that exists and is enabled on each type of card and Onair AP. The
APs have mostly the same firmware... a recent update stopped all the XG901 cards from being able to connect to the AP that had been updated......
This is in a Factory environment, and so wireless is not recommended, but it is not really an option to change this... and the data we are losing when the base/card crashes is a risk to production.
I am MCSE 2K3, so if anyone has any Windows-based ideas too, I am more than open to them.
Please help if you have any suggestions.
David
Aftertaf
Sometimes it just needs a good kicking.