|
|||||||
| Motherboards, Networking and Misc Forum Need the newest 4-in-1s? Some nForce drivers? some other driver you need? |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
DriverHeaven Newbie
Join Date: Apr 2006
Posts: 5
Rep Power: 0 ![]() |
Intel PRO/Wireless 3945ABG and Belkin F5D7230-4 Router issue
I have a Toshiba Satellite A100 Laptop with the OEM Intel PRO/Wireless 3945ABG built-in.
I've just upgraded my home network (moved house) with a Belkin Wireless Router running the 802.11G standard (but comes up as Belkin54g as the network name). I bought the router in a package with a USB adaptor for my main computer, and eventually got the network running with WPA2-PSK/AES running. In short, I could get the main computer to hook up in unsecured mode, but had problems in secured mode until I reinstalled the USB adaptor. Problem with the laptop is that I can connect to the server to get an IP address, (192.168.1.100, subnet mask 255.255.255.0) - but I cannot browse etc. The toolbar icon indicates connection at 54mbps (sitting right next to the router). I could not get the connection to work in the clear, and obviously still can't when the system is locked down. I've tried pinging the router, turning off firewalls etc but nothing comes back/times out. Does anyone know of compatability issues etc between the Intel component and the Belkin router? I know I can run 'G" wireless on the laptop but is this router running the 54g protocol and is that a possible issue? How can I find out? FWIW - everything works fine if I cable in to the router....duh Cliffo |
|
|
|
|
|
#2 |
|
HardwareHeaven Extreme Member
|
I'm not a wireless network wiz by any means, but looks like you might have to get into the properties settings for your particular WPA2 connection (Wireless Networks tab...) - a problem like this likely has to do with selecting the proper "Association" and "Authentication". There are several settings under those tabs that need to be selected to provide for proper communications - and are particular to your hardware and driver...
At least we know your router is good - so the problem is very likely in the setup of the WPA2 wireless connection properties...
__________________
It's not so much getting your way that matters or not - what matters is how you go about getting it. |
|
|
|
![]() |
| Thread Tools | |
|
|