UNSOLVED

wyricke

updated

23 years ago

W

wyricke

3 Posts

0

11646

February 20th, 2004 12:00

Problems connecting to an un-encrypted network.

I am having a strange problem.  I have a insp 8600 with a TM1300, and XP sp1.  At home I have a WRT54G, and am using WEP 128-bit.  At the office, we have BEFW11S4 that is using no security what so ever.  No WEP,WPA, and even has the default linksys SSID.

When I booted up today at the office, the TM connected to the linksys network, but I could not even ping the router.  I pulled up "properties" under my network places, and when I highlighted the connection, it showed that I was connected, but that encryption was enabled.  I checked the properties for this network, and I have them set to "OPEN".  I even removed the network from my preferred network list, and allowed the TM to rediscover the "linksys" network.  After it rediscovered the network, it gave the warning about connecting to an un-encrypted network.  I told it to connect anyway, and it did.  However it still says that encryption is enabled.  I removed it from my preferred network list again, and this time rebooted.  The same thing occured.

I've searched through the message boards, but I don't see where anyone else has had problems connecting to an open network, but somehow I am.

 

Kevin

  • jmwills

    2 Intern

    •

    11984 Posts

    651

    0

    Posted February 20th, 2004 12:00

    Sounds like someone changed a setting at work.
  • wyricke

    3 Posts

    651

    0

    Posted February 20th, 2004 12:00

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

     

    Kevin

  • jmwills

    2 Intern

    •

    11984 Posts

    651

    0

    Posted February 20th, 2004 13:00

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

    Work:

    SSID:

  • jmwills

    2 Intern

    •

    11984 Posts

    651

    0

    Posted 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

  • wyricke

    3 Posts

    651

    0

    Posted 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.

  • jmwills

    2 Intern

    •

    11984 Posts

    651

    0

    Posted 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?

  • Akashra

    17 Posts

    651

    0

    Posted 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.

  • xmlspice

    4 Posts

    651

    0

    Posted 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...)