Wireless Internet....help!

Hi all, sort of a newbie to linux, I am using suse 10.0 have got a wired ethernet connection which is working fine, and have a belkin wireless card in the back of the tower but can't seem to get it to work with linux (is fine with XP). I have installed ndiswrapper and installed the driver, which was rt61.inf. i have checked on konsole by ndiswrapper -l and it said driver present, hardware present, ndiswrapper is starting at boot as i typed modprobe ndiswrapper and then ndiswrapper -m. i went into yast and the network card was not there, so i added one myself, entered WEP key etc, tried iwconfig in konsole and it said it was there, but i can't connect. also, sometimes when configuring the wireless network card when it reaches 63% on the configuring screen linux freezes and i have to hold in the off button. can anyone help.......please!

also, getting a laptop soon with suse 10.3, can anyone help me set wireless connection with this, its a HP6720.

Thanks in advance! please be simple with me, im not that clever...

cheers, ross.

im not that clever... [/b]

neither am i, but i found this http://www.andrewd18.com/ndiswrapper/ndisw...nfo10-32bit.php give it a read, might help

Andy

A few "generic" considerations:

If you have an active ethernet interface which is set to use DHCP, then usually the wireless interface will not be able to use DHCP. This is because, by default, only the first active network interface is eligible access DHCP to get an IP address. In most instances, the first active interface will be an ethernet device.

So, some options: 1 set the wireless with a fixed IP; 2 set ethernet to be activated manually rather than at boot; 3 set ethernet with a fixed IP and wireless with DHCP, or; 4 just delete the ethernet configuration if you won't be using it. (You can do any of this in YAST)

The default behaviour of DHCP can be changed, I think, if you need both interfaces active and using DHCP.

I just mention the above scenario, because it can complicate complicate troubleshooting.

Other reasons for a hanging wireless connection can centre around encryption/security set-ups. For this reason, it is helpful to see if you can establish an open (unprotected) connection, just to verify that you have drivers and basic parameters correctly set up. Also ensure that you have entered your encryption key correctly and using the same method for your access point/router and wireless adapter.

Paul