Can connect via ethernet but not wireless
Closed
dibbler
-
Apr 28, 2010 at 11:12 AM
gadow21 Posts 13 Registration date Wednesday April 28, 2010 Status Member Last seen April 29, 2010 - Apr 28, 2010 at 11:30 AM
gadow21 Posts 13 Registration date Wednesday April 28, 2010 Status Member Last seen April 29, 2010 - Apr 28, 2010 at 11:30 AM
Related:
- Can connect via ethernet but not wireless
- Wireless keyboard won't type - Guide
- Railway wi-fi connect - Guide
- How to connect ps4 to pc - Guide
- Turn off usb connect sound - Guide
- What type of cable should be used to connect a laptop directly to another laptop to form an ethernet network? ✓ - Network Forum
1 response
gadow21
Posts
13
Registration date
Wednesday April 28, 2010
Status
Member
Last seen
April 29, 2010
3
Apr 28, 2010 at 11:30 AM
Apr 28, 2010 at 11:30 AM
The reason why your wireless network retains the old IP address after doing a release and renew is because you have DHCP disabled. Which means your configuration is using a static IP address.
Your IP address for your wireless connection is really not a real IP address. Its a windows autoconfiguration address, which means that your wireless NIC cant find a valid IP address in your pool (192.168.x.x), so Windows gives it one (169.x.x.x), which wont work. You need to disable or unplug your network cable so that your wireless NIC can take that address.
Also, Im not sure why you have both wireless and a wired connection hooked up to your computer. I would disconnect the LAN wire from the back or side of your computer, enable DHCP on your wireless NIC, reboot the machine and maybe your router, and then connect up to the wireless network again. You should be fine from there.
To enable DHCP in Windows XP go to the Control Panel, and go into Network Connections. Then from there, right click on your wireless NIC, and go to properties. Highlight your IPv4 TCP/IP, and click on properties again. Then click on the button for "Optain and IP address automatically". Do the same for IPv6, and now DHCP is enabled on your wireless NIC, and you should be able to get a new IP address (internal) when doing a release and renew, but it might stay the same. The only way to make sure you get a new one, is to go into your router and change it, or have another device take it. See DHCP, is a "pool" of IP addresses, and when a device talks to your router and says I want a IP address, the first one in the pool is taken.
If you have anymore questions, please feel free to ask.
Your IP address for your wireless connection is really not a real IP address. Its a windows autoconfiguration address, which means that your wireless NIC cant find a valid IP address in your pool (192.168.x.x), so Windows gives it one (169.x.x.x), which wont work. You need to disable or unplug your network cable so that your wireless NIC can take that address.
Also, Im not sure why you have both wireless and a wired connection hooked up to your computer. I would disconnect the LAN wire from the back or side of your computer, enable DHCP on your wireless NIC, reboot the machine and maybe your router, and then connect up to the wireless network again. You should be fine from there.
To enable DHCP in Windows XP go to the Control Panel, and go into Network Connections. Then from there, right click on your wireless NIC, and go to properties. Highlight your IPv4 TCP/IP, and click on properties again. Then click on the button for "Optain and IP address automatically". Do the same for IPv6, and now DHCP is enabled on your wireless NIC, and you should be able to get a new IP address (internal) when doing a release and renew, but it might stay the same. The only way to make sure you get a new one, is to go into your router and change it, or have another device take it. See DHCP, is a "pool" of IP addresses, and when a device talks to your router and says I want a IP address, the first one in the pool is taken.
If you have anymore questions, please feel free to ask.
