I am looking into a weird problem for some of the users (including me!) on my network.
Symptoms: When connected to wireless internet browsing fails. Trying to visit, for example, google.com via IE or Chrome will timeout and fail.
During this time, other services remain active. The connection never actually drops out. I'm able to ping external domains while browsing isn't working.
Weirdly, I have found an odd workaround.
Either, I wait a few minutes and eventually browsing begins to work again OR I launch a command prompt and ping an internal hostname. The second I start the ping command, I can hit refresh in any browser and my web pages begin to load.
I'm at a loss as to what would stop browsing, but let me to continue resolving names externally via ping or some such.
Any ideas about a starting point for investigation would be great.
This is in a Windows Domain environment with a 2003 DC (which is also DHCP and DNS).