Re: Intel Pro Wireless 3945 ABG no probs connecting, but dead line
- From: "Shaun Newton" <homespot1@xxxxxxxxxx>
- Date: Sat, 1 Jul 2006 22:45:38 +1000
Sorry to jump in on this one, but you described exactly the same problem i'm
having. I've got a cheapy Dell with the intel proset wireless, and it seems
to be a DHCP not assigning an IP address (getting "automatic private
address" of 169.xxx). I'm using a netcomm adsl router/wireless, my other
laptop can login fine, i can connect using ethernet, but not wireless. I'll
try turning encryption off but thanks for a different line of thought.
Shaun
"Jeff Liebermann" <jeffl@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:r8d6a2lubgdl98q4cv2s70ci4trr6768no@xxxxxxxxxx
"Carsten" <carsten.deppermann@xxxxxxxxx> hath wroth:
If the Tekram AP is ancient, it probably only supports WEP. If you're
using WEP, pleae use the Hex encryption key, not the ASCII. There are
problems converting from ASCII to Hex. Otherwise, try the Tekram with
with encryption temporarily turned off. That should work.
Incidentally, Microsoft displays "connected" when your client radio
associates with an SSID. There's no status indication for encryption
key exchange failure. Proset 10.x has some built in diagnostics that
will show at what point of the negotiation the connection is failing.
WEP is already turned off and it's Intel's Proset that says, that the
connection is established.
OK let's play Q&A.
1. Did DHCP deliver an IP address to your laptop from the Tekram?
Use:
Start -> Run -> cmd <enter>
ipconfig
Is the IP address 169.254.xxx.xxx ??? If so, then DHCP failed. If
it's something like 192.168.xxx.xxx, then it worked. If you set the
IP address on the laptop manually, you cheated. You may need to kick
start the DHCP client with:
ipconfig /release
wait a few seconds
ipconfig /renew
Then run:
ipconfig
to check what was delivered by DHCP.
2. If you have a valid IP address such as 192.168.xxx.xxx, use
IPCONFIG to determine the gateway address. That should be the IP
address of the Tekram. Try to ping it with:
ping 192.168.1.1 (or whatever you have for a gateway IP).
3. If that works, then keep going. Ping the ISP's gateway IP
address. You can get that IP address from the status page in the
Tekram. If it's blank or all zeros, the Tekram router didn't
correctly connect to your ISP.
4. If you can ping the ISP's gateway by IP address, then try to ping
something by the domain name. Something like:
ping www.google.com
If that does NOT work, you have a DNS problem somewhere. Lots of
possibilities but check your DNS servers with:
ipconfig /all | more
Look for the lines starting with DNS.
--
Jeff Liebermann jeffl@xxxxxxxxxxxxxxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.
- Prev by Date: Re: Repeater? Gateway? Access point?
- Next by Date: Re: WAP54G firmware upgrade goes awry
- Previous by thread: Remote admin on Siemens 6520 router
- Next by thread: Re: Intel Pro Wireless 3945 ABG no probs connecting, but dead line
- Index(es):
Relevant Pages
|
