Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Same sorta problem as before... here it is... I'm using windows to manage my wireless networks and i started using Window's wireless zero configuration... i'm using a smc router and a smc wireless card. When i start up the computer the network card seems to autoconfigure itself and assigns an outrageous ip address not even close to the private ip address the router assigns... i have the router setup as my DHCP server but for some reason the wireless card won't detect the DHCP server at startup... i have to repair the connection in order for it to work after every boot... i even tried assigning a static ip, subnet mask, and default gateway, but once again at startup it won't work and assigns a completely bogus ip address... if anyone knows how to stop itself from autoconfiguring or why it's doing this, your help will be much appreciated...
Thanks,
ToPoAsus A7V133
AMD Athlon 1.2Ghz
512Mb SDRAM
ATI Radeon 9600XT
SoundBlaster Live! Value

I had that same problem. Manually assign the ip address under the tcp/ip settings in your connection properties. Use an ip address in the range that the router/DHCP server assigns. For example its set to 50 ip address 192.168.1.100-192.168.1.149. Use an IP address in that range.

finally after trying everything i decided to remove WPA authentication from the network and use WEP encryption without any network authentication and everything seems to work fine now... it detects the DHCP server and assigns a proper ip address... plus the network is 128bit encrypted... everything seems to work...
Asus A7V133
AMD Athlon 1.2Ghz
512Mb SDRAM
ATI Radeon 9600XT
SoundBlaster Live! Value

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |