http://blogs.technet.com/b/keithcombs/archive/2005/07/30/408433.aspxHeart attack time. There’s nothing worse than reviewing a Windows Server 2003 event log and seeing row after row of red X application event log entries. This is especially true for something like a bunch of nastygrams indicating group policy is failingen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/keithcombs/archive/2005/07/30/408433.aspx#445743Thu, 10 Aug 2006 00:42:23 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:445743Bobwhat do you mean on the wan interface. &nbsp;There is only the option under the general tab for file and print sharing.<div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=445743" width="1" height="1">http://blogs.technet.com/b/keithcombs/archive/2005/07/30/408433.aspx#410013Wed, 31 Aug 2005 05:04:31 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:410013ArielKeith - I have the same problem, but for security reasons decided not to enable File and Print sharing on Wan interface. Then digging on MS website I found this event: <br><a rel="nofollow" target="_new" href="http://support.microsoft.com/kb/290647/en-us">http://support.microsoft.com/kb/290647/en-us</a> <br> <br>At the end you can find a seccion that state &quot;If this procedure does not resolve the issue&quot; then the problem is in the bindings, you should go to advance network settings and set the internal interface to the top. <br> <br>I hope that this helps someone. <br> <br>Ariel<div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=410013" width="1" height="1">