Recurring wireless connection problems...

every few days I see a thread about someone not being able to connect to wireless, and I believe half the time it's caused by a hangup in retrieving the network profile..

the computer will connect to the router, the router assigns an IP address, but all connections to the internet are blocked, as if windows can't remember whether it's connected to a home, work, or public network. My question is, which service is this attached to? How is it disabled?

And when is microsoft going to fix this? It seems this problem has remained unanswered by microsoft for the better part of a year now. There's no doubt in my mind that it's a flaw in windows 7 because it never happens in linux or any other non window OS I've used. I don't care what microsoft recommends, because almost nothing gets past the DMZ firewall in my router unless I decide to allow it anyway, and I have the best possible firewall there is for my critical files.. a computer that will never be connected to the internet.

There have been considerable changes to the network stack with Windows 7. For this reason router firmware updates and new drivers are often required in order for the network connection to function properly. There is absolutely nothing wrong with Windows 7 in this respect.

If it appears the connection is working but you can't access any sites the problem is sometimes caused by winsock needing a reset. The two commands below can sometimes fix this type of problem.

netsh winsock reset catalog (reset winsock entries)

netsh int ip reset reset.log hit (reset TCP/IP stack)

That seems to work.. any chance you would know how to turn that into a script to run at startup?

madtownidiot said:

That seems to work.. any chance you would know how to turn that into a script to run at startup?

I'm glad that helped but those commands usually stay put and fix the problem for good.

If you need to run this at each start up then there is an underlying problem somewhere in this network.

Maybe if you can post a screen shot of the ipconfig /all we can figure out what might be causing this problem to occur.

chev65 said:

madtownidiot said:

That seems to work.. any chance you would know how to turn that into a script to run at startup?

I'm glad that helped but those commands usually stay put and fix the problem for good.

If you need to run this at each start up then there is an underlying problem somewhere in this network.

Maybe if you can post a screen shot of the ipconfig /all we can figure out what might be causing this problem to occur.

typical.. soon as I try to recreate a glitch.. it stops happening. Thanks for the help

This is one glitch you don't want to re-occur. Usually the winsock TCP/IP reset will perminatly fix this sort of problem so it's no wonder that you can't recreate it.

I think the problem repeated only itself because my firewall blocked it the first time. I had to disable the AV and firewall to get it to work, but since then, no problems.. thx

Don't get me started on the networking problems that A/V's create , it is just insane. Glad you got the problem sorted out.

chev65 said:

Don't get me started on the networking problems that A/V's create , it is just insane. Glad you got the problem sorted out.

That's why I stick with fixing used computers in my own shop.. I wouldn't do very well in a corporate environment.. mainly because I tend to tell people what I really think..