We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


After connecting to access point away from home, laptop no longer will connect to home access point

jasimon9 asked
Medium Priority
Last Modified: 2013-11-09
This problem seems to occur once in a while, and I have never known what has caused it or what the solution is.

After taking my laptop to connect at some access point away from home, it will no longer connect to my access point at home when I return. What might cause this and what might the solution be?
Watch Question


Additional info: it seems to get stuck on "acquiring network address." This is strange because the system usually will connect immediately upon bootup.
Its seems that the wireless card is not refreshing its settings

when this happens you can run the following command from the cmdp prompt

ipconfig /flushdns
ipconfig /release
ipconfig /renew

and see you are able to connect.

Also thats it happens with the same wireless router or they are different example
if you use the hotel router then you come home then your laptop does not connect to your home wireless
or connecting to any router then connecting to your home wireless connection does not work.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Steve KnightIT Consultancy
Agreed.  When you connect to a network and get a DHCP address you are given a lease which lasts a certain length of time.  It could be these foregin networks are giving quite a long lease period and therefore you still have an IP address from their network.  It will initially try and connect to the original DHCP server address (and fail) until the end of the lease time at which point it will broadcast for a new one and end up talking to your router again and getting an address on your network.

If there is a period of time between connections and the lease time is qutie short you don't normally notice these things because the lease it already ran out or due to run out so it acquires a new on one anyway.

Only thing strange here is normally with XP and 2000 it releases the address at shutdown, are you by any chance hibernating or putting your machine into standby?  If so it will retain the address.

either way releasing and renewing as above and/or shutting down and restarting instead of hibernating will most likely fix it.
Here is another potential answer:

Did the other network and your home network have the same network name (SSID)?  Does one or the other have some sort of encryption on it (WEP or WPA)?

To make the whole issue easy to solve:
1) Double click on your wireless network icon in the bottom right, next to the clock
2) Click on Change Order of Preferred Networks on the left
3) Find your wireless network and delete it
4) Refresh the list of wireless networks and reconnect to it.

After that you should be able to automatically connect to your network again.

Here is what can happen:  Sometimes when you are out and about you connect to a network that has the same name but different configuration settings as another network.  Windows remembers those settings and tries to automatically reconnect using them.  Then when you try to connect to another of a similar name the connection cannot be successfully made because of the differences.

Good Luck,



Lot's of good ideas. I will try the flushdns, release, renew (things I have done in the past, but forgot about).

I have tried rebooting several times, and that made no difference.

My home network has a unqiue name that is not duplicated on other routers.

The "delete-recreate" is also a good idea.

I'll let you know my results.
sometimes, esp if you move through numerous wireless routers before coming back to the "home" router, the new router settings supercede the home settings. you can see these in the windows wireless networking setup window... try moving your home router "up" in the settings. Also, when you switch to other routers, do you manually config your ip address for these or are you on dhcp?


Immediately after posting my last comment on 10/24, my laptop back light went out and I had to take it in for repair. So I have not yet been able to try the above suggestions. Will post again when I get the machine back.
Steve KnightIT Consultancy

Four way split would be fair...

dido with dragon-it
Steve KnightIT Consultancy

Don't let my wife see that comment... just 'cos I had one Dido CD she thinks I fancy her


We did get the laptop back and have not had the situation recur since then.

I have many times moved my own network to the top, and it does not help. However, the flushdns is probably the correct approach. After sometime the dns would usually time out and take care of itself, but moving between many connections in a short time would seem to solved by the flushdns and I believe in the past that is what worked for me.

Therefore I believe that that is the correct solution. However, deleting the network and letting it be found again would also seem to be a likely solution. So I am going to split points on this basis.

Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.