I have been having a similar problem. I have a Dell Truemobile 1184 router and I ordered a network card from Dell and they sent me the lynksys g card. My connection goes in and out. When I check the IP address on my connection it says 0000000. I repair it - it reconnects only to disconnect again. The repair fix says to contact my IP provider. Can someone help??
I hope that someone has already answered this for you, but if not, here goes:
1) Click Start/Control Panel/Network Connections
2) Right click on Wireless Network Connection
3) Select (left click) on View Available Wireless Networks
4) If checked, uncheck the box "Enable IEEE 802.1x authentication for this network"
5) Click Advanced
6) In the Available networks area, select the network you want to configure (probably named wireless) and hit Configure
7) If you have Data encryption set to WEP and the Network authentication type set to Open, change the authentication type to shared (if you have it set to disabled, just exit this screen)
8) Hit okay
These steps helped stabalize my clients Inspirion 8600 with a dell true mobile 1400 dual band internal (mini-PCI) WLAN adapter that was connecting to a Dell true mobile 2300 broadband router. The Dell technician I spoke to said that the true mobile 2300 broadband router has problems with firewalls on the PC, so he feels that removing the "Enable IEEE 802.1x authentication for this network" was the primary thing that helped. We also removed our firewall software ZoneLABs free edition, but that didn't seem to help the situation. However, if you continue to have connectivity issues after you do the steps above, you might consider testing the connection with the firewall disabled. You will then have to balance your need for a firewall against your need for connectivity. As a note, I have worked with Linksys, Netgear, Belkin, et.al. wireless access points, and none of them have problems with a ZoneLABS (free edition) firewall or XP firewall on the PC, so if you want to have a PC firewall and good connectivity, you might consider another Wireless access point. I prefer Linksys as they have a bunch of add-on devices like a signal booster, device bridges, etc. that give you good extended networking options. As a last note, the technician recommended that I remove MS hotfix Q815485 if it was installed on my system as it was known to cause connectivity issues with the true mobile 2300. My system did not have this hotfix.
Why should we have to compromise our security just to get a stable connection. If the router was made to support WEP and WPA , then it should work! NEVER leave your network OPEN, thats like leaving your door open for everyone to come in and out as they please. That workaround is absolutely unacceptable! The consumer should not settle for such lame workarounds...
I don't know if you were responding to my post or not. It looks like you were. I'm 99% sure that removing the checkbox next to the "Enable IEEE 802.1x authentication" does not disable or comprimise WEP in any way. My WEP configuration stayed the same, and without a WEP key, my laptop could not connect to the router. I believe the IEEE 802.1x has more to do with an extension to the WEP protocol. Since configuring the WEP protocol is well beyond most end-users without an automated key generation utility, I think that disabling this feature on the NIC is a fair price to pay especially since the TrueMobile 2300 router doesn't seem to support the 802.1x extension anyway. I could be wrong on this, but I don't remember seeing any place to enable 802.1x features on the router configuration menus. Nor would it be reasonable to ask a normal end-user to setup a Kerberos or RADIUS server to provide the additional authentication mechanism. I don't know if the 802.1x feature affects WPA at all, and I don't have the time to research it right now. However, I hope this information is helpful. Best Wishes.
Below is some relevant informat I found:
802.1X in action
The use of IEEE 802.1X offers an effective framework for authenticating and controlling user traffic to a protected network, as well as dynamically varying encryption keys. 802.1X ties a protocol called EAP (Extensible Authentication Protocol) to both the wired and wireless LAN media and supports multiple authentication methods, such as token cards, Kerberos, one-time passwords, certificates, and public key authentication. For details on EAP specifically, refer to IETF's RFC 2284.
Initial 802.1X communications begins with an unauthenticated supplicant (i.e., client device) attempting to connect with an authenticator (i.e., 802.11 access point). The access point responds by enabling a port for passing only EAP packets from the client to an authentication server located on the wired side of the access point. The access point blocks all other traffic, such as HTTP, DHCP, and POP3 packets, until the access point can verify the client's identity using an authentication server (e.g., RADIUS). Once authenticated, the access point opens the client's port for other types of traffic.
To get a better idea of how 802.1X operates, the following are specific interactions that take place among the various 802.1X elements:
1. The client sends an EAP-start message. This begins a series of message exchanges to authenticate the client; think of this as a group of visitors entering the front gate of a theme park and the group's leader (i.e., client) asking the gatekeeper (i.e., access point) whether they can enter.
2. The access point replies with an EAP-request identity message. In the case of the theme park, the gatekeeper will ask the leader for their name and drivers license.
3. The client sends an EAP-response packet containing the identity to the authentication server. The leader in our example will provide their name and drivers license, and the gatekeeper forwards this information to the group tour manager (i.e., authentication server) who determines whether the group has rights to enter the park.
4. The authentication server uses a specific authentication algorithm to verify the client's identity. This could be through the use of digital certificates or other EAP authentication type. In the case of our example, this process simply involves verifying the validity of the leader's drivers' license and ensuring that the picture on the license matches the leader. In our example, we'll assume the leader is authorized.
5. The authentication server will either send an accept or reject message to the access point. So the group tour manager at the theme park tells the gatekeeper to let the group enter.
6. The access point sends an EAP-success packet (or reject packet) to the client. The gatekeeper informs the leader that the group can enter the park. Of course the gatekeeper would not let the group in if the group tour manager had rejected the group's admittance.
7. If the authentication server accepts the client, then the access point will transition the client's port to an authorized state and forward additional traffic. This is similar to the gatekeeper automatically opening the gate to let in only people belonging to the group cleared for entry.
The basic 802.1X protocol provides effective authentication regardless of whether you implement 802.11 WEP keys or no encryption at all. Most of major wireless LAN vendors, however, are offering proprietary versions of dynamic key management using 802.1X as a delivery mechanism. If configured to implement dynamic key exchange, the 802.1X authentication server can return session keys to the access point along with the accept message. The access point uses the session keys to build, sign and encrypt an EAP key message that is sent to the client immediately after sending the success message. The client can then use contents of the key message to define applicable encryption keys. In typical 802.1X implementations, the client can automatically change encryption keys as often as necessary to minimize the possibility of eavesdroppers having enough time to crack the key in current use.
802.1X not the whole solution
It's important to note that 802.1X doesn't provide the actual authentication mechanisms. When utilizing 802.1X, you need to choose an EAP type, such as Transport Layer Security (EAP-TLS) or EAP Tunneled Transport Layer Security (EAP-TTLS), which defines how the authentication takes place. There are many EAP types, so we'll leave details on EAP types to a future tutorial.
The important part to know at this point is that the software supporting the specific EAP type resides on the authentication server and within the operating system or application software on the client devices. The access point acts as a "pass through" for 802.1X messages, which means that you can specify any EAP type without needing to upgrade an 802.1X-compliant access point. As a result, you can update the EAP authentication type as newer types become available and your requirements for security change.
802.1X is the way to go
The use of 802.1X is well on its way to becoming an industry standard, and you would be wise to include it as the basis for your wireless LAN security solution. Windows XP implements 802.1X natively, and some vendors support 802.1X in their 802.11 access points. Wireless LAN implementations of 802.1X fall outside the scope of the 802.11 standard; however, the 802.11i committee is specifying the use of 802.1X to eventually become part of the 802.11 standard.
lc214
1 Message
0
September 24th, 2003 21:00
jeffesmi
2 Posts
0
November 4th, 2003 14:00
I hope that someone has already answered this for you, but if not, here goes:
1) Click Start/Control Panel/Network Connections
2) Right click on Wireless Network Connection
3) Select (left click) on View Available Wireless Networks
4) If checked, uncheck the box "Enable IEEE 802.1x authentication for this network"
5) Click Advanced
6) In the Available networks area, select the network you want to configure (probably named wireless) and hit Configure
7) If you have Data encryption set to WEP and the Network authentication type set to Open, change the authentication type to shared (if you have it set to disabled, just exit this screen)
8) Hit okay
These steps helped stabalize my clients Inspirion 8600 with a dell true mobile 1400 dual band internal (mini-PCI) WLAN adapter that was connecting to a Dell true mobile 2300 broadband router. The Dell technician I spoke to said that the true mobile 2300 broadband router has problems with firewalls on the PC, so he feels that removing the "Enable IEEE 802.1x authentication for this network" was the primary thing that helped. We also removed our firewall software ZoneLABs free edition, but that didn't seem to help the situation. However, if you continue to have connectivity issues after you do the steps above, you might consider testing the connection with the firewall disabled. You will then have to balance your need for a firewall against your need for connectivity. As a note, I have worked with Linksys, Netgear, Belkin, et.al. wireless access points, and none of them have problems with a ZoneLABS (free edition) firewall or XP firewall on the PC, so if you want to have a PC firewall and good connectivity, you might consider another Wireless access point. I prefer Linksys as they have a bunch of add-on devices like a signal booster, device bridges, etc. that give you good extended networking options. As a last note, the technician recommended that I remove MS hotfix Q815485 if it was installed on my system as it was known to cause connectivity issues with the true mobile 2300. My system did not have this hotfix.
Best Wishes,
Jeffery Smith
Thymadman
3 Posts
0
November 5th, 2003 23:00
jeffesmi
2 Posts
0
November 21st, 2003 16:00
I don't know if you were responding to my post or not. It looks like you were. I'm 99% sure that removing the checkbox next to the "Enable IEEE 802.1x authentication" does not disable or comprimise WEP in any way. My WEP configuration stayed the same, and without a WEP key, my laptop could not connect to the router. I believe the IEEE 802.1x has more to do with an extension to the WEP protocol. Since configuring the WEP protocol is well beyond most end-users without an automated key generation utility, I think that disabling this feature on the NIC is a fair price to pay especially since the TrueMobile 2300 router doesn't seem to support the 802.1x extension anyway. I could be wrong on this, but I don't remember seeing any place to enable 802.1x features on the router configuration menus. Nor would it be reasonable to ask a normal end-user to setup a Kerberos or RADIUS server to provide the additional authentication mechanism. I don't know if the 802.1x feature affects WPA at all, and I don't have the time to research it right now. However, I hope this information is helpful. Best Wishes.
Below is some relevant informat I found:
802.1X in action
The use of IEEE 802.1X offers an effective framework for authenticating and controlling user traffic to a protected network, as well as dynamically varying encryption keys. 802.1X ties a protocol called EAP (Extensible Authentication Protocol) to both the wired and wireless LAN media and supports multiple authentication methods, such as token cards, Kerberos, one-time passwords, certificates, and public key authentication. For details on EAP specifically, refer to IETF's RFC 2284.
Initial 802.1X communications begins with an unauthenticated supplicant (i.e., client device) attempting to connect with an authenticator (i.e., 802.11 access point). The access point responds by enabling a port for passing only EAP packets from the client to an authentication server located on the wired side of the access point. The access point blocks all other traffic, such as HTTP, DHCP, and POP3 packets, until the access point can verify the client's identity using an authentication server (e.g., RADIUS). Once authenticated, the access point opens the client's port for other types of traffic.
To get a better idea of how 802.1X operates, the following are specific interactions that take place among the various 802.1X elements:
1. The client sends an EAP-start message. This begins a series of message exchanges to authenticate the client; think of this as a group of visitors entering the front gate of a theme park and the group's leader (i.e., client) asking the gatekeeper (i.e., access point) whether they can enter.
2. The access point replies with an EAP-request identity message. In the case of the theme park, the gatekeeper will ask the leader for their name and drivers license.
3. The client sends an EAP-response packet containing the identity to the authentication server. The leader in our example will provide their name and drivers license, and the gatekeeper forwards this information to the group tour manager (i.e., authentication server) who determines whether the group has rights to enter the park.
4. The authentication server uses a specific authentication algorithm to verify the client's identity. This could be through the use of digital certificates or other EAP authentication type. In the case of our example, this process simply involves verifying the validity of the leader's drivers' license and ensuring that the picture on the license matches the leader. In our example, we'll assume the leader is authorized.
5. The authentication server will either send an accept or reject message to the access point. So the group tour manager at the theme park tells the gatekeeper to let the group enter.
6. The access point sends an EAP-success packet (or reject packet) to the client. The gatekeeper informs the leader that the group can enter the park. Of course the gatekeeper would not let the group in if the group tour manager had rejected the group's admittance.
7. If the authentication server accepts the client, then the access point will transition the client's port to an authorized state and forward additional traffic. This is similar to the gatekeeper automatically opening the gate to let in only people belonging to the group cleared for entry.
The basic 802.1X protocol provides effective authentication regardless of whether you implement 802.11 WEP keys or no encryption at all. Most of major wireless LAN vendors, however, are offering proprietary versions of dynamic key management using 802.1X as a delivery mechanism. If configured to implement dynamic key exchange, the 802.1X authentication server can return session keys to the access point along with the accept message. The access point uses the session keys to build, sign and encrypt an EAP key message that is sent to the client immediately after sending the success message. The client can then use contents of the key message to define applicable encryption keys. In typical 802.1X implementations, the client can automatically change encryption keys as often as necessary to minimize the possibility of eavesdroppers having enough time to crack the key in current use.
802.1X not the whole solution
It's important to note that 802.1X doesn't provide the actual authentication mechanisms. When utilizing 802.1X, you need to choose an EAP type, such as Transport Layer Security (EAP-TLS) or EAP Tunneled Transport Layer Security (EAP-TTLS), which defines how the authentication takes place. There are many EAP types, so we'll leave details on EAP types to a future tutorial.
The important part to know at this point is that the software supporting the specific EAP type resides on the authentication server and within the operating system or application software on the client devices. The access point acts as a "pass through" for 802.1X messages, which means that you can specify any EAP type without needing to upgrade an 802.1X-compliant access point. As a result, you can update the EAP authentication type as newer types become available and your requirements for security change.
802.1X is the way to go
The use of 802.1X is well on its way to becoming an industry standard, and you would be wise to include it as the basis for your wireless LAN security solution. Windows XP implements 802.1X natively, and some vendors support 802.1X in their 802.11 access points. Wireless LAN implementations of 802.1X fall outside the scope of the 802.11 standard; however, the 802.11i committee is specifying the use of 802.1X to eventually become part of the 802.11 standard.
To download the 802.1X standard, go to http://www.ieee802.org/1/pages/802.1x.html.