said by pn :
It is certainly a WB problem.
Its not a "problem," its an "issue" created by those clueless programmers in Redmond, who think they are so "smart." They have had since Windows 3.1x days to figure it out, but what did you expect from Redmond?
Change default DNS timeout value in your OS to a longer time value, and the "issue" disappears.
XP - »drewthaler.blogspot.com/2005/09/···ows.html
Vista/7 - »blogs.technet.com/b/stdqry/archi···t-2.aspx