Re: (Partially SOLVED) Re: Wireless still not working
Marc Shapiro wrote: > > > Marc Shapiro wrote: >> >> Now, my problem is with connecting and that is probably a >> configuration problem, but... > >> My wireless network shows up in wicd and I >> select it and click on "Connect." Wicd connects and authenticates, >> then it >> tries to retrieve an IP address through DHCP. After a few minutes of >> this, >> it gives up. I don't know that much about wireless connections, so I >> still >> need help. I am using WEP security and have entered my hex passcode. >> Wicd has already passed the authentication phase, so that should not >> be an >> issue. Why would it not be able to retrieve an IP address? This >> sounds like a DHCP configuration issue, but I don't know where to >> look for that, >> either. Is there a config file that I could compare between the >> Debian and Eeebuntu installations? > > Now, I'm thinking that it is a security/authentication problem. At > work, where I am connecting via an unsecured network, I can connect > just fine. I am posting this from the eeePC after installing > Iceweasel over the wireless connection. > > If the problem is authenticating over WEP, how do I track down that > error? > I had similar problems a few months ago with DHCP authentication on an Eeepc 901 which turned out to be an incompatibility between the installed AW-NE766 (Ralink 2700E) WiFi card and the linux drivers. My solution was to replace the original WiFi card with a compatible Intel WM3945AG and wireless and DHCP now works without problems. Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ho0t3g$rq...@tuscan2.grantura.co.uk
Re: (Partially SOLVED) Re: Wireless still not working
On Fri, 19 Mar 2010 15:10:22 -0400 (EDT), Marc Shapiro wrote: > > Now, I'm thinking that it is a security/authentication problem. > At work, where I am connecting via an unsecured network, > I can connect just fine. I am posting this from the eeePC > after installing Iceweasel over the wireless connection. Isn't success great! (Well, partial success anyway.) > If the problem is authenticating over WEP, > how do I track down that error? I'll be the first to admit I know nothing about WEP. But did you try looking in the logs, such as /var/log/syslog? -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/217628097.20353091269028072026.javamail.r...@md01.wow.synacor.com
Re: (Partially SOLVED) Re: Wireless still not working
Marc Shapiro wrote: > > Now, my problem is with connecting and that is probably a > configuration problem, but... > My wireless network shows up in wicd and I > select it and click on "Connect." Wicd connects and authenticates, then it > tries to retrieve an IP address through DHCP. After a few minutes of this, > it gives up. I don't know that much about wireless connections, so I still > need help. I am using WEP security and have entered my hex passcode. > Wicd has already passed the authentication phase, so that should not be an > issue. Why would it not be able to retrieve an IP address? This > sounds like a DHCP configuration issue, but I don't know where to look for > that, > either. Is there a config file that I could compare between the Debian and > Eeebuntu installations? Now, I'm thinking that it is a security/authentication problem. At work, where I am connecting via an unsecured network, I can connect just fine. I am posting this from the eeePC after installing Iceweasel over the wireless connection. If the problem is authenticating over WEP, how do I track down that error? Marc Shapiro mshapiro...@yahoo.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/582554.40623...@web55507.mail.re4.yahoo.com
(Partially SOLVED) Re: Wireless still not working
And do I feel silly! Because I was out of ideas of what to do, I decided to look through my BIOS settings. The wireless was turned OFF in the BIOS. Could this be why nothing was showing up in syslog, Andrei? I had not checked this, before, since it was working if I booted into Eeebuntu, or the OS that must not be named, so of course the hardware and BIOS must be OK. But it wasn't. Once I turned the WLAN on in the BIOS the modules loaded, my radio turned on and I was able to find my wireless network. Now, my problem is with connecting and that is probably a configuration problem, but... My wireless network shows up in wicd and I select it and click on "Connect." Wicd connects and authenticates, then it tries to retrieve an IP address through DHCP. After a few minutes of this, it gives up. I don't know that much about wireless connections, so I still need help. I am using WEP security and have entered my hex passcode. Wicd has already passed the authentication phase, so that should not be an issue. Why would it not be able to retrieve an IP address? This sounds like a DHCP configuration issue, but I don't know where to look for that, either. Is there a config file that I could compare between the Debian and Eeebuntu installations? Marc Shapiro mshapiro...@yahoo.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/753408.19122...@web55501.mail.re4.yahoo.com