Password prompt at companyweb on client computer 1

[princetonderm]

We have been starting to set up SBS STD 2003 at our workplace and have encountered an issue with companyweb. We are new to SBS 2003, with little to no experience with it, but have been able to do everything we need, as in add users and set up accounts for these users with email. Although another thread seems to have addressed this issue of a username and password prompt when

http://companyweb

is accessed from a client computer, the "solutions" have not worked. We have tried adding companyweb to safe intranet sites, the main resolution that has been posted. The prompt screen lasts for one cancel click, in that after clicking cancel once, the prompt goes away, at least for the homepage. Does anyone have any possible fixes for this problem?

Thanks for the support.

 

[Danny28]

The problem is because the userid you have logged on with on the client PC does not have access to the companyweb site. You need to either log on as another user or give the current user rights to at least read the companyweb site. If you go on the server and access the sharepoint administration site, you will find a place to do this.

I also recommend contacting a consultant to have them complete setting up your server. SBS is easier to administer than the 2003 Server, but you aren't going to know how to set anything up. There are many tricks to computer server operating systems, and people with experience and specialized training are your best bet, at least for the initial installation.

 

[princetonderm]

In response to giving the user's rights, we have given them contributing and reading rights in sharepoint admin.

 

[Danny28]

That would suggest that your SBS was not set up correctly using the wizards. I would try rerunning the CEICW.

You can also go into your IIS.MSC, right click COMPANYWEB, select properties, and select the directory security tab. Make sure that the IUSR_xxxxxxxxx account has been entered with the appropriate password and that "anonymous access" is enabled. Also make sure "integrated windows authentication" is enabled. Go back out to a command prompt and run IISRESET /FORCE.

 

[princetonderm]

The IIS.MSC is set up in that way. When using iisreset /force, am i only using that, or am i using iisreset {comp name} and then command? And in regards to the CEICW wizard, we believe it has been set up correctly.

 

[Danny28]

If you are running the IISRESET command on the server itself, then the computername is implied and therefore not necessary.

Does this client have an IP address on the same LAN segment as your server? What are the local ip addresses of your server and the client?

 

[princetonderm]

The ip addresses of the client and server are 172.16.26.46 and 172.16.26.44 respectably.

 

[princetonderm]

To add, this issue with username and password prompt occurs on any client computer, not just this one.

 

[Danny28]

Can you access COMPANYWEB from the server?

Can you access COMPANYWEB from a client computer that is logged in with the domain administrator id?

 

[princetonderm]

Yes and Yes.

 

[princetonderm]

To add, If a domain admin username is entered, access to companyweb is granted, however, complete access is granted, we don't want the users to have full modification rights.

 

[Danny28]

Ok. I was checking to see if your companyweb site was functioning properly.

Go into IIS.MSC and rt click companyweb to get the permissions for the site. Is USERS one of the groups with READ & EXECUTE, READ, and LIST rights?

 

[princetonderm]

Yes, and they have special permissions as well, most likely default, with create files and folders.

 

[Danny28]

Do you have SUS 3.0 or Sharepoint Services 3.0 installed on this server?

I recommend removing and reinstalling companyweb on this server using the following procedure posted by Microsoft. I also recommend rebooting the server after performing the removal portion.
1) Using ADD/REMOVE programs, CHANGE/REMOVE Windows 2003 SBS, follow the wizard to Remove Intranet Component.
2) Remove Windows Sharepoint Services 2.0
3) Delete Registry Keys:
a) Delete
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Intranet
b) Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\SHAREPOINT
c) Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
Extensions\Ports\Port /LM/W3SVC/4:
(Do not delete "Port /LM/W3SVC/1:" because it is FronPage Server Extension
2002
which is installed on the Default WebSite. If you see additional "Port
/LM/W3SVC/X:", backup and then remove them)


4) Delete IIS Virtual Directory
a) Open IIS, expand servername, Web Sites
b) Delete SharePoint Central Administration (Do Not Delete Microsoft
SharePoint
Administration. It belongs to FronPage Server Extension)


5) Delete Application Pool
a) Open IIS, expand servername, Application Pools.
b) There should be only 4 application pools (DefaultAppPool,
ExchangeApplicationPool, ExchangeMobileBrowseApplicationPool, and
MSSharePointAppPool).
Besides those 4, delete all the extra.


6) Rename Folders
a) Rename C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT to
MSSQL$SHAREPOINT.OLD
b) Rename C:\Inetpub\companyweb to companyweb.old
Note: Location of the MSSQL$SHAREPOINT folder is determined by
HKLM\Software\Microsoft\SmallBusinessServer\Monitoring\MSDE_Location. Check
out
this registry key and determine the real location of the folder.


7) Install the intranet component
a) In Add or Remove Programs, select Windows Small Business Server 2003
and then
click Change/Remove. The Setup Wizard appears.
b) Click Next.
c) On the Windows Configuration page, click Next.
d) On the Component Selection page, in the Action column, change Server
Tools to
Maintenance, change Intranet component to Install, and then click Next.
e) On the Logon Information page, click Next.
f) On the Component Summary page, click Next.
g) Click Finish.

 

[princetonderm]

This seems to have made it work, thank you very much for your time and your knowledge on SBS 2003.

 

[Danny28]

No problem.

 

[princetonderm]

The problem turned out to be a picture that we added to companyweb,in place of windows sbs 2003, and it was causing the site to force username and pass onto the client computers.