We encountered the same issue and we corrected this by adding the following into the "Local Intranet" in Internet Options and Security:
*.networkdomain.com
*.networkdomain.local (if you have a '.local')
I suggest the 'Local Intranet' rather than the 'Trusted Sites' because it corrected our issue.
Main Topics
Browse All Topics





by: mccarthybriPosted on 2009-11-20 at 05:48:44ID: 25870157
I would go ahead and make the internal site (url) a trusted site and see if that helps any thing