« Can't Enable Wireless Fedora 16 + Gnome 3 | Main | Well Documented - Linux vs Windows »



Feed You can follow this conversation by subscribing to the comment feed for this post.

Microsoft tries to chalk this issue up to the computer booting faster than the network, DNS issues, or netlogon using udp instead of tcp. The fact is, this is a problem with Windows and they refuse to acknowledge it. This workaround absolutely works, and the fact that it does illustrates the problem exists.
The only concern I have is that after the maximum number of cached logins are exhausted, will it renegotiate or will I have to do this again to refresh the cache? Only time will tell.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name is required. Email address will not be displayed with the comment.)


  • meowkins

Windward Reports


  • Quantcast