Wifi can't get a ip

kadooosh's picture
Submitted by kadooosh on Sat, 05/05/2007 - 09:09. Networking

Hi I just got a wizard and its works great except I cant get wifi working, I keeps connecting but never gets a ip, I tried it on 2 diferent routers, I tried it with Socket Wi-Fi Companion but didnt work either :(

anyone got a idea what could be wrong, thanks

--




kadooosh's picture
Submitted by kadooosh on Sat, 05/05/2007 - 09:27.

I just noticed it registered my dns and dhcp server on 192.168.2.1 but this is wrong... they are both one 192.168.1.1 but I have no idea how to correct it
oh btw
im using a linksys wrt54gl with dd-wrt firmware I tried with wpa-psk and without any security, mac filter is on but I added the mac of my ppc(didnt work disabled too

--


FireDoc's picture
Submitted by FireDoc on Sat, 05/05/2007 - 20:14.

I have a WRT54GS w/HyperWRT as an wireless AP router. Some folks have DHCP connection issues with PPC's. The factory DHCP client list on the LinkSys, I believe, is 50 clients starting at IP 192.168.1.100, giving you a range of 100-149. Have you tried locking down an IP address in the PPC? With all other PC/PPC's powered off, set the PPC to 192.168.1.100. You can also input the SubNet Mask 255.255.255.0, Gateway 192.168.1.1 and Pri/Sec DNS (your ISP). Soft-boot. The router should connect the PPC because it is the first device on network. For simplicity, start off with all security features disabled, this should get you up and running. If not try/check the following settings on the router for starters:

Setup > Basic >
Connection Type > Automatic DHCP
Local IP Address > 192.168.1.1 (Router/Gateway Address)
SubNet Mask > 255.255.255.0
DHCP Server > Enabled - starting? 192.168.1.100 - clients? 50
Client Lease Time > 0 (one day)

Wireless > Basic Wireless Settings
Wireless Network Mode > Mixed - for now (b and g (PPC compatability?))
SSID Broadcast > Enabled

Wireless > Security > None - for now

Wireless > Security > MAC Filtering > Disabled - for now (check that the PPC MAC is correct with Enabled, Permit Acsess Only - capital letters with collin separaters - disabling this feature will not remove the MAC addresses entered)

Wireless > Advanced Wireless Settings
Shared Key > Auto - for now
Basic Rate > All
Transmission Rate > Auto
CTS > Disabled
FrameBurst > Enabled (your choice)

Security > Firewall / VPN - shouldn't be causing connection issues

DMZ and NAT Redirection should not be an issue either. Disable DMZ if it is not necessary. I believe it defaults to x.x.x.100.

After establishing LAN/WAN connections... re-instate and test the security settings one at a time.

LinkSys factory default LAN IP is 192.168.1.1... nothing else should share this address. 192.168.2.1 is not valid with the x.x.1.x and will not connect.

Depending on your PPC, you may have to edit the registry to enable "g" wireless.

Hope this helps you out.

I use static IP's on all wired/wireless PC/PPC's using a gateway router, AP router (wireless access) and VoIP phone service. Also, I have found this method to have more reliable/stable connections, easier to "find" and control PC's on the network. You may want to try this out.

--


kadooosh's picture
Submitted by kadooosh on Sun, 06/05/2007 - 12:16.

ooi it works :D but now I dont have any security hehe lets see if I can enable wpa

--


kadooosh's picture
Submitted by kadooosh on Sun, 06/05/2007 - 12:28.

kadooosh wrote:
ooi it works :D but now I dont have any security hehe lets see if I can enable wpa

nope with wpa it cant connect... I enabled the mac filter now so I guess that should be good enough security for a while

--


FireDoc's picture
Submitted by FireDoc on Sun, 06/05/2007 - 20:09.

FYI... if you used the static IP of 100 on the PPC, within the DHCP server client list, you can't leave it there. It was only for testing. Why? If your PC is DHCP and turned on first, the PC will take over 100 and PPC will not connect. The good part is that PPC connection was accomplished which tells you "things" are working.

Because other issues remain, encryption security, it may be best to "lock down" your system via static IP. Doing this will establish and hold connections so they will not be an issue again. You can retain a smaller DHCP client list for your buds that come over with their laptops - or - turn DHCP off all together. Enabling wireless MAC filtering is excellent.

Some PPC's only work with certain types of WPA encryption... have you tested the different types available from the router? Can't help you much about WPA. My system, with static IP and wireless MAC on WEePing, has 9 PC's, two PPC's, Xbox and PS2 connected all the time and 4 other PC/PPC's come and go. Of the 9 PC's, four run Win98 on wireless WEP, which of course, WPA is not supported. I'm not familiar with WPA options.

I have read on a forum somewhere (HTC or xda) that an individual had a similar WPA issue as yourself. Do a google search for PPC, WPA, etc.

--


kadooosh's picture
Submitted by kadooosh on Mon, 07/05/2007 - 07:00.

FireDoc wrote:
FYI... if you used the static IP of 100 on the PPC, within the DHCP server client list, you can't leave it there. It was only for testing. Why? If your PC is DHCP and turned on first, the PC will take over 100 and PPC will not connect. The good part is that PPC connection was accomplished which tells you "things" are working.

Because other issues remain, encryption security, it may be best to "lock down" your system via static IP. Doing this will establish and hold connections so they will not be an issue again. You can retain a smaller DHCP client list for your buds that come over with their laptops - or - turn DHCP off all together. Enabling wireless MAC filtering is excellent.

Some PPC's only work with certain types of WPA encryption... have you tested the different types available from the router? Can't help you much about WPA. My system, with static IP and wireless MAC on WEePing, has 9 PC's, two PPC's, Xbox and PS2 connected all the time and 4 other PC/PPC's come and go. Of the 9 PC's, four run Win98 on wireless WEP, which of course, WPA is not supported. I'm not familiar with WPA options.

I have read on a forum somewhere (HTC or xda) that an individual had a similar WPA issue as yourself. Do a google search for PPC, WPA, etc.


its working with dhcp now im not even sure if my wizard suports wep, all it gives me for verification options are open, shared, wpa and wpa-psk oh wait wep is at datadecoding (im running dutch os so im translation this hehe ... :p )
im search a bit to enable wpa cause wep is kinda easy to crack I heard, thanks alot :)
I just tested and wep does work, im suprised I entered that 26 digits key correct at once :o

--


ybbmadysu's picture
Submitted by ybbmadysu on Thu, 02/08/2007 - 17:54.

I share my connection with another wrt54gs. both have ddwrt std in wds w/tkip & aes. no mac filter, dhcp disabled.

What do I fix/change to make this work?

--