From: Robert on
We are running MOSS 2007 Ent. Edition, and recently upgraded all client PCs to Vista Enterprise with Office 2007 installed. All patches up to current.

In any case, Office Products all had issues saving directly to SharePoint, Explorer View fails, and "Open in Windows Explorer" prompts repeatedly for credentials and ultimately fails.

The workaround is simple to implement.

Open 'My Computer'
Right-click and select 'Add a network location'
Click Next Next Next then in the textbox requiring the location to add enter the root of your portal.
Example https://portalname
Click Next Next Next then Finish
You are done. This resolves MANY Office issue and allows IE to open lists in Explorer View.

(yes I AM aware there are not that many Nexts to click)



datawire wrote:

I too access through an internal/netbios name but have found that John's
18-Jul-07

I too access through an internal/netbios name but have found that John's
suggestion works. I use a .local dns configuration and under proxy
server>>advanced, I add *.x.local to exeptions. Now I can access via
http://x or http://x.x.local. If you turn off the auto detect settings, it
appears to be 10x as fast when accessing DavWWWRoot folders. Without doing
this I always have to log in...through either access point.

During my attempts to eliminate logging in, I have set Sharepoint's
alternate access mapping to https and set mysite and all sp sites to require
ssl and require certificates. All the sites log in fine through ie, but when
I try to open a share doc folder I get the error "Your client does not
support opening this list with windows explorer". If I access the shortcut
\\x.x.local(a)SSL\DavWWWRoot, it asks me for a certificate and I have to select
my cert (I only have one, so it should not be asking). Once I access the
folder this way, then I can access any of the folders through the website.
Actions>>Open with Windows Explorer. Has anyone found a way around this?

"Brent" wrote:

Previous Posts In This Thread:

On Wednesday, July 11, 2007 2:04 PM
Bren wrote:

WSS 3.0 prompting for authentication on Vista clients
I have a problem that is only occurring on Vista clients running office 2007:
I am using WSS 3.0 with NTLM authentication on an Intranet. When a Vista
client attempts to open an office document (word, excel), they are prompted
to login to the sharepoint server. If you type the correct user name and
password, it will prompt you two more times before the document is finally
displayed in office. If you press cancel at the login prompt, the document
is displayed in office. I do not have this problem on Windows XP machines
running office 2003 or 2007 (on the same network). I can duplicate the issue
if the site is in the intranet or trusted sites zone in IE and don't think
this is an issue passing domain credentials since the client is not prompted
to login to the server in the first place (just when opening office
documents). PDF documents open fine without prompting for authentication.
Any ideas? I've seen similar posts in other newsgroups but haven't found a
solution.
Thanks

On Thursday, July 12, 2007 6:35 AM
Daniel Bugday wrote:

Hi,which edition of office are you using?
Hi,
which edition of office are you using?

/Daniel Bugday

On Thursday, July 12, 2007 8:04 AM
Bren wrote:

Re: WSS 3.0 prompting for authentication on Vista clients
Office 2007.

"Daniel Bugday" wrote:

On Thursday, July 12, 2007 8:31 AM
Daniel Bugday wrote:

What i wonder is which edition of 2007.. business, standard, enterprise.
What i wonder is which edition of 2007.. business, standard, enterprise.

/Daniel Bugday

On Thursday, July 12, 2007 8:50 AM
Bren wrote:

It shows up as "Office 2007 Professional".
It shows up as "Office 2007 Professional". I assume this is the same as
business?

"Daniel Bugday" wrote:

On Thursday, July 12, 2007 9:33 AM
Daniel Bugday wrote:

The reason i am asking you this is because in earlier versions of office there
The reason i am asking you this is because in earlier versions of office
there was an issue regarding the edition of office users had..

Is it possible for you to try another edition of office just to make sure
thats not the problem?

/Daniel Bugday

"Brent" <Brent(a)discussions.microsoft.com> wrote in message
news:A630A063-4FED-4C70-8A46-D3E9CC033227(a)microsoft.com...

On Friday, July 13, 2007 9:00 AM
Bren wrote:

I just tried it with the Enterprise version and got the same behavior.
I just tried it with the Enterprise version and got the same behavior.

"Daniel Bugday" wrote:

On Friday, July 13, 2007 10:02 AM
markm75 wrote:

Re: WSS 3.0 prompting for authentication on Vista clients
On Jul 13, 9:00 am, Brent <Br...(a)discussions.microsoft.com> wrote:

We've had this issue with prompting for credentials under Vista with
Sharepoint 2007... in particular.. it prompts if you try to access a
document library.. but only the first time its accessed (after a
reboot etc).

On Monday, July 16, 2007 1:34 AM
eddiets wrote:

Have the same problem, but no solution yet.
Have the same problem, but no solution yet. Works fine under XP with
Office 2007, only under Vista with Office 2007.

On Monday, July 16, 2007 11:20 AM
John Belkevich wrote:

I can replicate this problem in my environment...
I can replicate this problem in my environment... I have Vista Ultimate
with Office 2007 Enterprise, IE 7 and ISA 2006 for web proxy. I am using
a FQDN to access my site (site.domain.com). The only way I can open
files from my site without the prompt is to have an exception in my
proxy settings of IE for my domain (*.domain.com) or explicitly for the
site (site.domain.com). If I remove that exception, I get prompted for
credentials, but can hit cancel to open the document anyway. I read
somewhere that when you use ISA and an externally addressable domain
name for an internal site, IE will still try to access it through ISA,
which I think is what causes the problem...

(Tools->Internet Options->Connections->LAN Settings-> Advanced (under
proxy server))

HTH,
John

eddietse(a)gmail.com wrote:

On Monday, July 16, 2007 12:14 PM
Bren wrote:

Our users do not access the Sharepoint site through a proxy server or reverse
Our users do not access the Sharepoint site through a proxy server or reverse
proxy server. Clients access the site going directly to the server using the
internal NetBIOS server name. As an example:
http://sharepointserver/sitename.

I'm not sure if this makes a difference, but this site was upgraded from WSS
2.0.

"John Belkevich" wrote:

On Wednesday, July 18, 2007 5:26 PM
datawire wrote:

I too access through an internal/netbios name but have found that John's
I too access through an internal/netbios name but have found that John's
suggestion works. I use a .local dns configuration and under proxy
server>>advanced, I add *.x.local to exeptions. Now I can access via
http://x or http://x.x.local. If you turn off the auto detect settings, it
appears to be 10x as fast when accessing DavWWWRoot folders. Without doing
this I always have to log in...through either access point.

During my attempts to eliminate logging in, I have set Sharepoint's
alternate access mapping to https and set mysite and all sp sites to require
ssl and require certificates. All the sites log in fine through ie, but when
I try to open a share doc folder I get the error "Your client does not
support opening this list with windows explorer". If I access the shortcut
\\x.x.local(a)SSL\DavWWWRoot, it asks me for a certificate and I have to select
my cert (I only have one, so it should not be asking). Once I access the
folder this way, then I can access any of the folders through the website.
Actions>>Open with Windows Explorer. Has anyone found a way around this?

"Brent" wrote:

On Friday, July 27, 2007 8:26 AM
Nor wrote:

Brent,I have the exact same issue with is how I stumbled upon this thread.
Brent,

I have the exact same issue with is how I stumbled upon this thread. Its
been driving me crazy!

We have a pure vanilla fresh install of WSS 3.0. No proxy, no ISA, no
nothing other than the front end and backend SQL server. Users are all on
the same internal network. The front end server is added as a trusted site
in IE as well using the users logged in credentials for authentication.

Windows XP users get no authentication boxes to open docs but Vista gets
THREE logon prompts just to open a doc. This is just with WSS 3.0...on WSS
2.0 I do not see this behavior.

Looking for the fix as well...



"Brent" wrote:

On Friday, August 03, 2007 11:16 PM
thebearn wrote:

Glan I am not the only one going crazy.
Glan I am not the only one going crazy.

Office 2007 Enterprise Edition on Windows Vista Business - get logon
prompts continuously when opening and saving documents.

Office 2007 EE on Windows XP works perfectly

I do not have any Proxy Server etc.

Single Domain, and MOSS 2007 Site has been added to the trusted sites
list.

I have also tried disabling protected mode on all the IE security
options and setting Trusted sites to the lowest security possible

HELP !!!

On Saturday, August 04, 2007 3:11 AM
Mike Walsh wrote:

This isn't the newsgroup for people who have installed MOSS 2007.
This isn't the newsgroup for people who have installed MOSS 2007.

Your Subject and Text of message don't match. Do you have WSS 3.0 (here)
or MOSS 2007 (microsoft.public.sharepoint.portalserver) ?

Add a WSS 3.0 site to the Intranet security zones when using Vista/IE7;
Trusted is what is correct for XPPro but this doesn't work with
Vista/IE7 you need Intranet (yes, it is odd, but it's a proven fact).


Mike Walsh
WSS FAQ http://www.wssfaq.com
no questions by e-mail please



thebearnz(a)gmail.com wrote:

On Tuesday, August 07, 2007 6:11 PM
J. Greg Mackinnon wrote:

The thing that fixed this for me was to add our Sharepoint Server to the
The thing that fixed this for me was to add our Sharepoint Server to the
"Local intranet" Zone (not "Trusted sites", AND to disable Protected
Mode on this zone.

(You can see how protected mode would create trouble, since it forces IE
to run in a low-privilege mode that cannot share information with other
running applications.)

This was really starting to get on my nerves! I am happy to finally
have a solution, even if it does "put my computer at risk" according to
the pop-ups in IE7.

-Greg Mackinnon
University of Vermont

thebearnz(a)gmail.com wrote:

On Wednesday, August 08, 2007 12:02 AM
Mike Walsh wrote:

Many thanks for the AND section.
Many thanks for the AND section.

I've often suggested Intra for Vista/IE7 and have been frustrated when
that didn't help as it should.

so next time it's "disable Protected Mode" as well....

Mike Walsh
WSS FAQ http://www.wssfaq.com
no questions by e-mail please



J. Greg Mackinnon wrote:

On Wednesday, August 08, 2007 12:21 AM
Mike Walsh wrote:

Prompted by the above, I've also finally got round to putting this in the WSS
Prompted by the above, I've also finally got round to putting this in
the WSS v3 FAQ. It's here

http://www.asaris.de/sites/walsh/Lists/WSSv3%20FAQ/DispForm.aspx?ID=1191

Mike Walsh


Mike Walsh wrote:

On Thursday, August 09, 2007 3:10 PM
J. Greg Mackinnon wrote:

The problems don't end, though.
The problems don't end, though. Now we get a "Protected mode is
currently turned off for the Local intranet zone" warning in the IE
Information Bar. Very annoying, since this setting was applied via GPO.
Sadly, there does not appear to be a corresponding GPO setting to
suppress this warning, either.

This bar appears to be controlled by the DWORD value
"NoProtectedModeBanner" in:
"HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main"
but the Vista Group Policy Settings reference does not contain this
setting at all.

Off to trawl the Group Policy groups for help...

On the plus side, I have been credited on the Internet by Mike Walsh.
What a hoot! I should have a credit to Mike added to my email signature
file, and he is thanking me...

-Greg Mackinnon
University of Vermont

Mike Walsh wrote:

On Friday, August 10, 2007 2:22 AM
Mike Walsh wrote:

come back and let s know the results of your Group Policy search !
come back and let s know the results of your Group Policy search ! (and
if possible send me mail).

Do you think this warning is so annoying that I should amend the FAQ
item ? It doesn't require any extra clicks I hope (?)


Mike Walsh


J. Greg Mackinnon wrote:

On Monday, August 13, 2007 5:35 PM
J. Greg Mackinnon wrote:

Sadly, my previously posted solution (configure your Sharepoint server in the
Sadly, my previously posted solution (configure your Sharepoint server
in the "Local intranet" Zone, AND disable protected mode) ceased working
after a day in production, so I guess my pride at being placed in the
WSS FAQ was premature. The solution does not work for me anymore. I
intend to burn a support incident on this in coming week.

Even if the previously posted solution did work, I think that a
permanent Information Bar pop-up in IE which advises users on managed
computers that their IE settings are making their computer vulnerable is
a bad thing. I was able to suppress the Information Bar, although not
without difficulty.

Since is no existing GP setting to suppress this particular IE
Information Bar warning, I had to generate a custom ADMX template file
to control the setting.

I used the "Full Armor ADMX Migrator" tool (licensed by Microsoft and
avaiable at www.microsoft.com/downloads) to generate the ADMX, which I
can post back to this group if there is interest. I don't recommend
taking this route until we have some real answers to the question of how
to kill off those Office authentication prompts.

-Greg Mackinnon
University of Vermont

Mike Walsh wrote:

On Tuesday, August 14, 2007 12:45 AM
Mike Walsh wrote:

Thanks. I'll make it a maybe in the FAQ ...Mike WalshWSS FAQ www.wssfaq.
Thanks. I will make it a maybe in the FAQ ...

Mike Walsh
WSS FAQ www.wssfaq.com / wss.collutions.com
no private e-mail questions please

J. Greg Mackinnon wrote:

On Friday, September 07, 2007 6:30 AM
C(a)discussions.microsoft.com wrote:

It appears that this is not just related to Office and SharePoint, its how
It appears that this is not just related to Office and SharePoint, its how
WebDav redirector works in Vista http://support.microsoft.com/kb/940172

Whenever I connect to a local intranet WebDav (for example explorer view of
a sharepoint document library or the Save/publish pages in Office) I am
prompted for this additional username/password.

The best work around I have found so far which doesn't require setting up a
proxy is to add the site to the local intranet, set a proxy with a fake
proxyname and port, bypass local and then in the advanced exceptions list,
place just the value * in to this text box to get access to both the internet
and intranet where a proxy is not being used. If you use a proxy then place
the real proxy name and port into the proxyname box. If you use automatic
connect then find out what your proxy address is then remove automatic and
place the proxyname into the proxy box.

This is by far not an ideal work around I would be happy to hear a better
method, but as far as I can tell from the KB article listed above is that we
have to wait for an update to the Vista WebDav redirector, or this is
actually the intended WebDav behaviour.

What do the Microsoft guys do during demos with Vista and SharePoint?

"Mike Walsh" wrote:

On Friday, September 07, 2007 9:09 AM
J. Greg Mackinnon wrote:

The CSS SharePoint tech I was working with forwarded this "fake proxy"
The CSS SharePoint tech I was working with forwarded this "fake proxy"
workaround to us earlier this week. It seems to work. As it turns out,
the "disable protected mode" suggestion above was not necessary
(although the "local intranet" setting is, as it was under XP).

There is a great blog post detailing the required steps here:
http://www.portalsolutions.net/Blog/Lists/Posts/Post.aspx?ID=27

Apparently the problem will not affect you if you are using a proxy, so
MS guys probably don't have this problem most of the time.

Our SE tells me that there should be a bug fix for this problem in Vista
SP1. I hope so... I'll test it out as soon as the public beta is released.

-Greg Mackinnon
University of Vermont

C wrote:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Entity Framework 4.0 and the AJAX Autocomplete Extender.
http://www.eggheadcafe.com/tutorials/aspnet/77429274-e89f-49c2-a93a-b290f013f649/entity-framework-40-and.aspx