ACS WQ

Remember the bulldogs...
 
HomeHome  CalendarCalendar  GalleryGallery  FAQFAQ  SearchSearch  RegisterRegister  MemberlistMemberlist  UsergroupsUsergroups  Log inLog in  

Share | 
 

 Technical Meeting Update # 2

Go down 
AuthorMessage
Edmats
HOKAGE
HOKAGE
avatar

Number of posts : 12
Age : 68
Registration date : 2006-08-17

PostSubject: Technical Meeting Update # 2   Thu 17 Aug - 17:49

1. Configuration on the Advanced Tab of the wireless cards properties to improve wireless performance.
=> For Intel Wireless Cards:
Double-click the Intel Wireless Connection on the Device Manager.
Click the Advanced Tab on the Properties window.
On the Property ""Intel Enhanced Throughput"", uncheck Use Default Value and select Enable from the drop-down menu.
On the Property ""Power Management"", uncheck Use Default Value and move the arrow to the far right over Highest.
On the Property ""Transmit Mode"", uncheck Use Default Value and select Long Preamble from the drop-down menu.
On the Property ""Preamble Mode"", uncheck Use Default Value and move the arrow to the far right over Highest.
Close the Properties window.
Press the <FN>+<F2> keys to disable the wireless radio.
Press the <FN>+<F2> keys to enable the wireless radio. The adapter settings are now configured for optimal performance.
Note: To access the updated DSN Tree for this one, just type in Intel Wireless and choose the first option “Intel® 2100a / 2200 / 2915 / 3945 Wireless Network Adapter cannot associate. [ All Portables ]”"
=> For Dell Wireless Cards:
Double-click the Dell Wireless WLAN Card on the Device Manager.
Click the Advanced Tab.
Select Broader Compatibility under Value for the Property ""AP Compatibility Mode"".
Select Disabled under Value for the Properties ""Power Save Mode"" and ""Minimum Power Consumption"". "

2. Fixing IP address FE80::5445:5245:444F%5.
=>For this type of issue, it’s possible that the IP address has been stored or has not been released. It could also be caused by a spyware or it doesn’t know how to connect or associate to the network.
Do the following: delete ARP cache and then reboot. If it doesn’t work – Do a pc restore. If still no go, replace the card.
from Joel Malinao (05.14.06): use the command ipv6 uninstall in the dos prompt.

3. When will be the release of WWAN express cards?
=> There’s still no definite date on when will be the release of WWAN Express Cards since it has been moved to several months. Most likely, sometime September or October.

4. Any specific router out of the market that has incompatibilities or known issues with dell wireless systems?
=> There are no known router issues with the Dell wireless systems
If in case you would encounter issues, just check for possible changes that the customer did to the router and revert it.
Basic connectivity is what’s important. Check the IP address – if valid or invalid.
Also check if security is enabled. Remember that passphrase doesn’t work well with the Dell cards so you’ll have to use hexadecimal keys."

5. More DSN trees for wireless troubleshooting and improve the existing trees. (e.g. intermittent wireless connection tree)
=> John, the client knowledge analyst, has recently updated 14 KB articles in configuring third party routers.
Dell 1400 to 1490 cannot associate has been pre-empted and re-built already.
“Wireless does not function” tree has been updated and will be the main entry point for all the wireless issues.
John is also currently working with the development engineers in improving the DSN trees for wireless devices.
For intermittent issues, you can just use the “Cannot Associate” DSN tree for the meantime. John is still in the process of creating a DSN tree for “dropping connection”."

6. This is about the Truemobile 1300 Mini-PCI driver – Release Date 4/15/2006. The queue got a call from a customer who stated that right after he installed the updated driver for the wireless card the system lost the NetBEUI function. Everything works fine except for the said protocol. The customer reinstalled the old driver and everything went back to normal. Just to verify if it’s really a driver problem the new driver was reinstalled for the second time and the issue is seen again. Basically, that customer just called in to check whether this is a known issue about the driver and if there’s any resolution about it.
Case # 131591249

=> According to James Vance after he referred this case to the engineering dept:
When the newer driver is installed, you have to reload the NETBEUI Protocol. Since that Protocol is not default installed, it’s not designed to carry it over from the older driver to the newer one. The reason that it shows back up on the older version of the driver, is because that protocol is bound to the driver (the older one). So all the customer has to do is add the protocol to the newer driver. Most likely they won’t even need the XP cd, because it’s on the system, it just needs to be added to the newer driver.

7. During an installation of the Dell Wireless 3300 Printer Adapter (Carafe), it was detected as a USB modem before the installation pushed thru. I have verified that the only devices connected thru USB was the mouse and the carafe. The issue was solved but is it normal for the device to be detected as a USB modem?
=> According to James Vance, this is normal. A KB Article will be created about this.

8. DSN for Call Profiling Policies which is normally used for Wrong Queue (Document ID 158341) won't show up when launching DSN inside Dellserv.
=> Check your Dellserv and DSN profiles. Ensure it is set only to ACS Technical Support.

9. Some technicians received calls wherein other routers like US Robotics and SMC have similar issues with Westell 327W. Updating the firmare of the routers also fixed the issues.
=> John requested for the case numbers of the said calls. The technicians are also requested to include the brand of routers and the t/s done in the case notes.
Back to top Go down
View user profile
moxspill
Chunin
Chunin
avatar

Number of posts : 5
Age : 36
Registration date : 2006-08-18

PostSubject: Re: Technical Meeting Update # 2   Fri 18 Aug - 16:21

2. Fixing IP address FE80::5445:5245:444F%5.
=>For this type of issue, it’s possible that the IP address has been stored or has not been released. It could also be caused by a spyware or it doesn’t know how to connect or associate to the network.
Do the following: delete ARP cache and then reboot. If it doesn’t work – Do a pc restore. If still no go, replace the card.
from Joel Malinao (05.14.06): use the command ipv6 uninstall in the dos prompt.

sorry its been a while since i did networking but i believe it is IPv6
Back to top Go down
View user profile
Edmats
HOKAGE
HOKAGE
avatar

Number of posts : 12
Age : 68
Registration date : 2006-08-17

PostSubject: Re: Technical Meeting Update # 2   Fri 1 Sep - 13:09

Thanks Mox! I hope you'll have time to review the other items in this forum.
Back to top Go down
View user profile
Sponsored content




PostSubject: Re: Technical Meeting Update # 2   

Back to top Go down
 
Technical Meeting Update # 2
Back to top 
Page 1 of 1
 Similar topics
-
» How to update any field(text area) in selenium RC using C#
» First Meeting with PFO Trial Neurologist
» Disrupt Update might Brick your Wii U
» [ANSWERED] Windows 8.1 with Update (Retail,Professional VL,Enterprise) (x86/x64) - DVD (English) Out
» [ANSWERED] Cannot Apply Windows Update

Permissions in this forum:You cannot reply to topics in this forum
ACS WQ :: Technical Issues Explained :: Technical Meetings by Edmats-
Jump to: