10-06-2005 04:55 AM - edited 03-13-2019 10:46 AM
Hi friend,
Please let me know if the above mentioned subject can work out?
Thank you and regards
Charles
10-06-2005 05:28 AM
I'm not familiar with this particular card, but Communicator will definitely work with wireless.
Brandon
10-06-2005 11:46 AM
I have been chasing this issue for awhile.
There is another post IP Communicator with XP SP2 that discusses the same issue.
There was a post several weeks ago that stated that Atheros was working on it. I wiill try to find that post again.
10-06-2005 11:53 AM
Replied by: dom@mowd.co.uk - Senior Network Consultant, DHL Information Services - Sep 9, 2005, 12:02am PST
I have observed exactly this problem, and currently have a TAC Case open for this, so far the status is:
1) Atheros and Cisco agree that this points strongly to a problem in the atheros device-driver
2) Atheros's FAE and Dev Manager visited Cisco 08/23/05 and debugged the problem.
3) They took back with them a working Communicator setup to reproduce this issue inhouse.
4) They will come back with a final analysis in a couple of days.
5) At that point they will also provide Cisco guidance on telling customers what they can do, especially if they are running non-Cisco 'Atheros' based NICs such as the one found HP Laptops.
So it is in 3rd party hands as it looks like device drive bug.
10-06-2005 04:56 PM
hi dom, thank you for reply..., mind to tell me your tac case number or any references? so that i can know more detail..
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide