I built a new WFE to add to my Farm and when I added it it keeps asking for my credentials.I built it to match exactly what the other two WFEs have but it keeps prompting. I have added the url of the sites as a trusted site in IE. any ideas?

Just to get some more information... Is this a load balanced WFE? Are you being prompted when you are accessing the site remotely as well as on the server itself? Is it the same site collection that is working on another server?

yes it is load balanced. yes, it prompts from both sides. its every site, every page and only on this server, the other two WFEs do not prompt. Do you think i need to update the farm credentials?

It wouldn't be your farm credentials. If that was the case, you wouldn't be able to log in at all. It sounds like something got hosed in the installation process. I would uninstall SharePoint on that WFE and reinstall it. Shannon Bray - MCT, MCPD, MCTS, MCITP Blog http://shannonbray.wordpress.com User Group Site: http://www.cospug.com

I'm assuming that you can log in fine when you get the prompt? I would agree with Shannon that a reinstall is a good step, if only to eliminate that before spending more time on the issue. I would also verify that your domain is setup the same on this server. Same DNS servers, AD resolution is working ok, app pool identities are the same, etc. Its likely not going to be anything within Central Admin (farm creds) as those settings are drawn from the same location as the other servers in your farm.

it prompts for each image on every site. even i cancel out of the prompt the page shows up normally. as far as i know, DNS, AD res are the same. app pool accts are the same.

you don't happen to have https enabled on the other WFE's with a redirect in place from http? Sounds like you are authenticating to the main page but the images are linked to a url that it thinks you need to re-authenticate to.

nope, no https on this environment.

I believe if it was an actual authentication issue of some sort, then you would be able to duplicate it on all of the WFEs. The issue is isolated to one box, so something has been messed up with the actual web application itself. If you feel it will be a waist of your time to re-install, double check the application pools, services on the WFE and verify they are using the same accounts, and check to see if that particular WFE is throwing errors in the application log. Shannon Bray - MCT, MCPD, MCTS, MCITP Blog http://shannonbray.wordpress.com User Group Site: http://www.cospug.com

Is the site using Kerberos or NTLM?

Some more questions:What is the operation system for the WFE? How about others?If you cancel the prompting window, can you access the web site?Sincerely,Lambert QinPosting is provided "AS IS" with no warranties, and confers no rights.

The farm is using kerberos and all servers are running windows 2003 sp2 32-bit. Canceling the prompts still gets me to the page but the images are X'ed out. When I was running the config wizard these events got entered into the log, not sure if it is normal or not. This first event got entered for each web app several times before it finally got though. Event Type: Warning Event Source: ASP.NET 2.0.50727.0 Event Category: None Event ID: 1064 Date: 4/16/2010 Time: 11:36:07 AM User: N/A Computer: SPAPP2 Description: Failed while creating files and directories in C:\Inetpub\wwwroot\wss\VirtualDirectories\services.com80\aspnet_client. Error code: 80070003 For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: W3SVC-WP Event Category: None Event ID: 2269 Date: 4/16/2010 Time: 11:37:27 AM User: N/A Computer: SPAPP2 Description: The worker process failed to initialize the http.sys communication or the w3svc communication layer and therefore could not be started. The data field contains the error number. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 05 00 07 80

I'm even seeing this event pop up now, somethings gotta be wrong the permissions on this box. Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Unified Logging Service Event ID: 5401 Date: 4/18/2010 Time: 6:56:33 PM User: N/A Computer: SPAPP2 Description: Tracing Service failed to create the trace log file at 'D:\MOSS-Trace-Logs'. Error 5: Access is denied. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

anyone?

Looks like the server file system permissions are messed up. Was this server ever working? If so, what's changed since? If it's never worked then it might be easier to rebuild the server.

Hello Danny, Did you rebuild it? You probably will find that this will fix your issue in a lot less time than you have spent on it. You can keep chasing this tail for quite some time. Shannon Bray - MCT, MCPD, MCTS, MCITP Blog http://shannonbray.wordpress.com User Group Site: http://www.cospug.com

SharePoint was working before the server was rebuilt, but since then I can't get it back to where it was. So you're suggesting rebuilding the whole server or just reinstalling MOSS? I have already tried reinstalling MOSS with no luck. THanks in advance.

reading through i see that you are facing the authentication prompt only on the images and rest of the page comes up as expected, so if I am not wrong you would get broken images sign (a little red cross) on the places with images This looks like an IIS sync issue or IIS permissions issue You can expand the effected site in IIS manager and go to images folder and compare permissions on that folder with some other WFE, that should help

I checked IIS and the settings are the same. There is one difference I have noticed but I don't think this would be the issue. The IUSER_<servername> account has a "-R" at the end of it, that wouldn't cause any issues would it?

bump

SharePoint was working before the server was rebuilt, but since then I can't get it back to where it was. So you're suggesting rebuilding the whole server or just reinstalling MOSS? I have already tried reinstalling MOSS with no luck. THanks in advance. Yes. Rebuilding the server from scratch might be your best bet.

so i finally got this fixed. rebuilding the server did not help. what was causing the issue was that IIS was running at a different version than the rest of the WFEs. I had to reinstall sp2 on the server and that solved the issue. thanks all for the suggestions