|
windows
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Cannot aquire IP from DHCPIn my network I used to have a DLink wireless router (DI-624) and a DLINK
(DWL-2100AP). Because I had difficulties in switching between the 2 networks I sent the AP back for replacement as I thought it was deffective (it might as well have been indeed). Anyway, after that I was only using the wireless router which was working flawlessly until I have installed all latest drivers fro HP as well as the wireless configuration utility (all latest versions). The effect now is that I connect to the network but it stays on status: (aquiring IP address) which never ends. This is what I had with the Access point and even if I roll-back to the old drivers, it is still the same. Now I'm wondering if it was really the AP or the DHCP at the router. If I assign a static IP it connects but nothing works though. What firewall are you using?
-- Show quoteHide quoteKerry MS-MVP Windows - Shell/User "Andreas Yiangoullis" <andr***@trustnet.com.cy> wrote in message news:es0Vl5RnGHA.4784@TK2MSFTNGP04.phx.gbl... > In my network I used to have a DLink wireless router (DI-624) and a DLINK > (DWL-2100AP). Because I had difficulties in switching between the 2 > networks I sent the AP back for replacement as I thought it was deffective > (it might as well have been indeed). > Anyway, after that I was only using the wireless router which was working > flawlessly until I have installed all latest drivers fro HP as well as the > wireless configuration utility (all latest versions). The effect now is > that I connect to the network but it stays on status: (aquiring IP > address) which never ends. This is what I had with the Access point and > even if I roll-back to the old drivers, it is still the same. Now I'm > wondering if it was really the AP or the DHCP at the router. If I assign a > static IP it connects but nothing works though. > WinXP SP2 + DLINK integrated FW
Show quoteHide quote "Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message news:OyuwYPSnGHA.3580@TK2MSFTNGP03.phx.gbl... > What firewall are you using? > > -- > Kerry > MS-MVP Windows - Shell/User > > "Andreas Yiangoullis" <andr***@trustnet.com.cy> wrote in message > news:es0Vl5RnGHA.4784@TK2MSFTNGP04.phx.gbl... >> In my network I used to have a DLink wireless router (DI-624) and a DLINK >> (DWL-2100AP). Because I had difficulties in switching between the 2 >> networks I sent the AP back for replacement as I thought it was >> deffective (it might as well have been indeed). >> Anyway, after that I was only using the wireless router which was working >> flawlessly until I have installed all latest drivers fro HP as well as >> the wireless configuration utility (all latest versions). The effect now >> is that I connect to the network but it stays on status: (aquiring IP >> address) which never ends. This is what I had with the Access point and >> even if I roll-back to the old drivers, it is still the same. Now I'm >> wondering if it was really the AP or the DHCP at the router. If I assign >> a static IP it connects but nothing works though. >> > > You could try disabling the Windows firewall but that's unlikely to be the
cause. Some 3rd party firewalls you need to configure to trust the subnet. I would suspect some problem with encryption. What type of encryption are you using? WEP? WPA? Make sure the settings are the same on both the computer and the AP. You may want to re-enter the keys on both ends to make sure they are right. If either one is using an ascii phrase to generate the key then disable that and enter the keys manually. -- Show quoteHide quoteKerry MS-MVP Windows - Shell/User Andreas Yiangoullis wrote: > WinXP SP2 + DLINK integrated FW > > "Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message > news:OyuwYPSnGHA.3580@TK2MSFTNGP03.phx.gbl... >> What firewall are you using? >> >> -- >> Kerry >> MS-MVP Windows - Shell/User >> >> "Andreas Yiangoullis" <andr***@trustnet.com.cy> wrote in message >> news:es0Vl5RnGHA.4784@TK2MSFTNGP04.phx.gbl... >>> In my network I used to have a DLink wireless router (DI-624) and a >>> DLINK (DWL-2100AP). Because I had difficulties in switching between >>> the 2 networks I sent the AP back for replacement as I thought it >>> was deffective (it might as well have been indeed). >>> Anyway, after that I was only using the wireless router which was >>> working flawlessly until I have installed all latest drivers fro HP >>> as well as the wireless configuration utility (all latest >>> versions). The effect now is that I connect to the network but it >>> stays on status: (aquiring IP address) which never ends. This is >>> what I had with the Access point and even if I roll-back to the old >>> drivers, it is still the same. Now I'm wondering if it was really >>> the AP or the DHCP at the router. If I assign a static IP it >>> connects but nothing works though. On 1-Jul-2006, "Andreas Yiangoullis" <andr***@trustnet.com.cy> wrote: Static addressing is the way to go. Router address is both> If I assign > >> a static IP it connects but nothing works though. the DNS server, and the Default Gateway, well in my case anyway. Have tried DLink kit, and like the magazine reviewers found that it's flaky, but I might just have been unlucky. I suspect DLink source from more than one vendor, but supply the same drivers for all versions of the product. Also make sure that you use the same address range like 10.0.0.nnn It may work if you are XP's Administrator, I had major problems with setting up internet connectivity for a User account. It too showed a connection, and the adapter counted packets, but no actual useable connection.
Show quote
Hide quote
"Andreas Yiangoullis" <andr***@trustnet.com.cy> wrote in message It has been known to take 10 minutes for DHCP to assign an IP before. To be news:es0Vl5RnGHA.4784@TK2MSFTNGP04.phx.gbl... > In my network I used to have a DLink wireless router (DI-624) and a DLINK > (DWL-2100AP). Because I had difficulties in switching between the 2 > networks I sent the AP back for replacement as I thought it was deffective > (it might as well have been indeed). > Anyway, after that I was only using the wireless router which was working > flawlessly until I have installed all latest drivers fro HP as well as the > wireless configuration utility (all latest versions). The effect now is > that I connect to the network but it stays on status: (aquiring IP > address) which never ends. This is what I had with the Access point and > even if I roll-back to the old drivers, it is still the same. Now I'm > wondering if it was really the AP or the DHCP at the router. If I assign a > static IP it connects but nothing works though. > honest with you, in a home or small office situation, I find it more efficient to assign IP numbers to machines and fill in the DNS servers as well (assigning the DLink router's IP address in DNS will suffice). You don't have to worry about DHCP and your number is available to you even if the router is, for some reason, turned off thus meaning when the router is on again, it connects quickly. In your case it would connect MORE quickly assuming it can get a signal. One other thing to consider in your setup is that you don't have WEP or whatever turned on in the router when setting up or if it is already done, that you have the RIGHT encryption method and encryption key or passphrase installed at the computer. Also, if you are using MAC filtering, you wont get on or get assigned an IP address at all.
External Hard Drive for backing up simple home network - recommendations
Controlling home PC from networked laptop wireless and wired Change between wireless networks Networking only works one way Connected but can't ping router or surf! network connection with xp on 2 computers Connectivity problems Location of wireless config data wireless network not found on new laptop |
|||||||||||||||||||||||