2 Intern

 • 

12K Posts

February 20th, 2004 12:00

Sounds like someone changed a setting at work.

3 Posts

February 20th, 2004 12:00

I also have a Latitude running W2K using a linksys WPG54G which still connects.

 

Kevin

2 Intern

 • 

12K Posts

February 20th, 2004 13:00

If I were you I would setup two wireless profiles, one named work and the other home.

Work:

SSID:

2 Intern

 • 

12K Posts

February 20th, 2004 13:00

If I were you I would setup two wireless profiles, one named work and the other home.

Work:

SSID:  linksys

encyrption: none

 

Home:

SSID:  chnage it to something unique and stop the broadcast

Encryption:  use 128 bit with a passphrase to generate the key

Message Edited by jmwills on 02-20-2004 10:32 AM

3 Posts

February 20th, 2004 14:00

I have three wireless networks setup in my preferred list.  One for my secure network at home, one for the secure network that I setup  at my parents house, and one for the unsecure network here at the office.  I have them setup in the preferred network list in that order, and all three have different SSIDs.

This makes not sense at all.  The card will recognize the network as being unsecured.  It warns me about the network being unsecured, but I can not disable encryption.  I have data encryption set for disabled for this network connection.  I've deleted the network from my preferred network list, and let the adapter re-discover it.

2 Intern

 • 

12K Posts

February 20th, 2004 16:00

The profile for each location determines the encryption for each network so as long as you set the the necessary parameters correctly, I fail to see where you are going wrong.

Do you have the update applied from KB Article 815485?

17 Posts

February 21st, 2004 01:00

Netgear and DLink support their own enhanced transfer modes for b and g - In my case we have DLink APs around the house, and I'm using an Intel Pro/Wireless 2100.  Took me ages to figure out that it wasn't WEP causing the problems, but these enhanched PBCC modes.

Check just to make sure you have these enhanched transfer modes disabled on the router, and then try to connect.  That COULD be the cause of the problem, though I can't say for certain as you're dealing with slightly different hardware.

4 Posts

March 2nd, 2004 12:00

I had the identical problem.  A month of phone support, a new OS, a new machine, sending it back to dell for testing on their own time, a new card - nothing fixed it.  But, I made partial progress last night.

Try dropping the transfer rate on the router and let me know, I am testing a theory.  There seems to be a pattern: Trumobile and XP may only work at lower transfer rates, in which case there is a bug that needs to be fixed.

Anyone have ideas for a workaround that does not involve tweaking the router?  (no good for work locations...)

No Events found!

Top